I am the upstream author of whatsapp-desktop, an independent GPL-3.0-or-later desktop client for WhatsApp Web with tray integration, notifications, themes, configurable fonts and privacy controls. It requires an existing WhatsApp account and Internet access and is not affiliated with Meta or WhatsApp.
I have prepared a source-only application packaging proposal. It installs JavaScript and data and depends on a separately packaged Electron >= 40, < 41; the application build neither downloads Electron nor runs npm. The application tests and package builds pass in clean Ubuntu 24.04 and Fedora 44 environments. Fedora rpmlint reports zero errors and warnings.
Public source review artifacts (Fedora SPEC/SRPM and Debian .dsc/orig/quilt sources, with checksums): https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
Merged packaging changes and validation: https://github.com/abdallah-shehawey/whatsapp-desktop/pull/6
Debian ITP, acknowledged by the BTS: https://bugs.debian.org/1150415
The key prerequisite is Electron: it is not currently packaged in the target official archives, and Debian's runtime request https://bugs.debian.org/842420 remains open. The ITP is explicitly blocked on that runtime work. I have not completed Electron source packaging, and these application artifacts are not an accepted or currently installable official archive package.
I would like to pursue inclusion in Fedora's official repositories. Could a Fedora packager advise on the Electron prerequisite, review eligibility for this independent web-service client, and sponsorship for a new contributor? The directly downloadable SPEC and SRPM are linked above. I understand that a formal Fedora Package Review must be filed through a Bugzilla account tied to my Fedora Account System email; this email is a request for packaging guidance, not a claim that a formal review has already been filed.
Regards, Abdallah Shehawey
On Fri, Oct 9, 2026 at 8:03 AM Abdallah Shehawey shehawey9@gmail.com wrote:
I am the upstream author of whatsapp-desktop, an independent GPL-3.0-or-later desktop client for WhatsApp Web with tray integration, notifications, themes, configurable fonts and privacy controls. It requires an existing WhatsApp account and Internet access and is not affiliated with Meta or WhatsApp.
I have prepared a source-only application packaging proposal. It installs JavaScript and data and depends on a separately packaged Electron >= 40, < 41; the application build neither downloads Electron nor runs npm. The application tests and package builds pass in clean Ubuntu 24.04 and Fedora 44 environments. Fedora rpmlint reports zero errors and warnings.
Public source review artifacts (Fedora SPEC/SRPM and Debian .dsc/orig/quilt sources, with checksums): https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
Merged packaging changes and validation: https://github.com/abdallah-shehawey/whatsapp-desktop/pull/6
Debian ITP, acknowledged by the BTS: https://bugs.debian.org/1150415
The key prerequisite is Electron: it is not currently packaged in the target official archives, and Debian's runtime request https://bugs.debian.org/842420 remains open. The ITP is explicitly blocked on that runtime work. I have not completed Electron source packaging, and these application artifacts are not an accepted or currently installable official archive package.
Electron is present in Fedora. It is currently in Rawhide (which will eventually branch to become Fedora 46), but it is present. However, we will only maintain one version of Electron, Right now, nodejs-electron is on v43, and it will likely move to v44 soon.
I would like to pursue inclusion in Fedora's official repositories. Could a Fedora packager advise on the Electron prerequisite, review eligibility for this independent web-service client, and sponsorship for a new contributor? The directly downloadable SPEC and SRPM are linked above. I understand that a formal Fedora Package Review must be filed through a Bugzilla account tied to my Fedora Account System email; this email is a request for packaging guidance, not a claim that a formal review has already been filed.
You'll need to update your software to work with newer versions of Electron. I don't know much about your application beyond that, since I haven't looked. Perhaps someone else familiar with Nodejs applications may be willing to look at this once you've updated your code.
-- 真実はいつも一つ!/ Always, there's only one truth!
Le ven. 9 oct. 2026 à 14:36, Neal Gompa ngompa13@gmail.com a écrit :
On Fri, Oct 9, 2026 at 8:03 AM Abdallah Shehawey shehawey9@gmail.com wrote:
I am the upstream author of whatsapp-desktop, an independent GPL-3.0-or-later desktop client for WhatsApp Web with tray integration, notifications, themes, configurable fonts and privacy controls. It requires an existing WhatsApp account and Internet access and is not affiliated with Meta or WhatsApp.
I have prepared a source-only application packaging proposal. It installs JavaScript and data and depends on a separately packaged Electron >= 40, < 41; the application build neither downloads Electron nor runs npm. The application tests and package builds pass in clean Ubuntu 24.04 and Fedora 44 environments. Fedora rpmlint reports zero errors and warnings.
Public source review artifacts (Fedora SPEC/SRPM and Debian .dsc/orig/quilt sources, with checksums): https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
Merged packaging changes and validation: https://github.com/abdallah-shehawey/whatsapp-desktop/pull/6
Debian ITP, acknowledged by the BTS: https://bugs.debian.org/1150415
The key prerequisite is Electron: it is not currently packaged in the target official archives, and Debian's runtime request https://bugs.debian.org/842420 remains open. The ITP is explicitly blocked on that runtime work. I have not completed Electron source packaging, and these application artifacts are not an accepted or currently installable official archive package.
Electron is present in Fedora. It is currently in Rawhide (which will eventually branch to become Fedora 46), but it is present. However, we will only maintain one version of Electron, Right now, nodejs-electron is on v43, and it will likely move to v44 soon.
I would like to pursue inclusion in Fedora's official repositories. Could a Fedora packager advise on the Electron prerequisite, review eligibility for this independent web-service client, and sponsorship for a new contributor? The directly downloadable SPEC and SRPM are linked above. I understand that a formal Fedora Package Review must be filed through a Bugzilla account tied to my Fedora Account System email; this email is a request for packaging guidance, not a claim that a formal review has already been filed.
You'll need to update your software to work with newer versions of Electron. I don't know much about your application beyond that, since I haven't looked. Perhaps someone else familiar with Nodejs applications may be willing to look at this once you've updated your code.
Out of curiosity, which package uses this packaged electron in rawhide ?
Having every electron based application to rely on the same pace update of the base electron package looks unreliable. That's because not every package maintainer can rise up at the same time (not even talking about having upstream rebased at the same time, dealing with various difficulties or even real life issues). It's not more reliable to have a slow pace electron package because it's just moving the same problem.
I would prefer to amend the alternate version policy (that allows a "per-version" namespace of a given package). That way we can have a "per-consumer" based namespace. So having electron-whatsapp-desktop and others (signal, elementary, etc).
That's the only way forward to this long standing issue.
On Fri, Oct 9, 2026 at 9:59 AM Nicolas Chauvet kwizart@gmail.com wrote:
Le ven. 9 oct. 2026 à 14:36, Neal Gompa ngompa13@gmail.com a écrit :
On Fri, Oct 9, 2026 at 8:03 AM Abdallah Shehawey shehawey9@gmail.com wrote:
I am the upstream author of whatsapp-desktop, an independent GPL-3.0-or-later desktop client for WhatsApp Web with tray integration, notifications, themes, configurable fonts and privacy controls. It requires an existing WhatsApp account and Internet access and is not affiliated with Meta or WhatsApp.
I have prepared a source-only application packaging proposal. It installs JavaScript and data and depends on a separately packaged Electron >= 40, < 41; the application build neither downloads Electron nor runs npm. The application tests and package builds pass in clean Ubuntu 24.04 and Fedora 44 environments. Fedora rpmlint reports zero errors and warnings.
Public source review artifacts (Fedora SPEC/SRPM and Debian .dsc/orig/quilt sources, with checksums): https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
Merged packaging changes and validation: https://github.com/abdallah-shehawey/whatsapp-desktop/pull/6
Debian ITP, acknowledged by the BTS: https://bugs.debian.org/1150415
The key prerequisite is Electron: it is not currently packaged in the target official archives, and Debian's runtime request https://bugs.debian.org/842420 remains open. The ITP is explicitly blocked on that runtime work. I have not completed Electron source packaging, and these application artifacts are not an accepted or currently installable official archive package.
Electron is present in Fedora. It is currently in Rawhide (which will eventually branch to become Fedora 46), but it is present. However, we will only maintain one version of Electron, Right now, nodejs-electron is on v43, and it will likely move to v44 soon.
I would like to pursue inclusion in Fedora's official repositories. Could a Fedora packager advise on the Electron prerequisite, review eligibility for this independent web-service client, and sponsorship for a new contributor? The directly downloadable SPEC and SRPM are linked above. I understand that a formal Fedora Package Review must be filed through a Bugzilla account tied to my Fedora Account System email; this email is a request for packaging guidance, not a claim that a formal review has already been filed.
You'll need to update your software to work with newer versions of Electron. I don't know much about your application beyond that, since I haven't looked. Perhaps someone else familiar with Nodejs applications may be willing to look at this once you've updated your code.
Out of curiosity, which package uses this packaged electron in rawhide ?
Having every electron based application to rely on the same pace update of the base electron package looks unreliable. That's because not every package maintainer can rise up at the same time (not even talking about having upstream rebased at the same time, dealing with various difficulties or even real life issues). It's not more reliable to have a slow pace electron package because it's just moving the same problem.
I would prefer to amend the alternate version policy (that allows a "per-version" namespace of a given package). That way we can have a "per-consumer" based namespace. So having electron-whatsapp-desktop and others (signal, elementary, etc).
That's the only way forward to this long standing issue.
Unless you want to maintain all the different chromium codestreams in parallel, that's probably not happening.
It was introduced in order to package podman-desktop, which has a review request: https://bugzilla.redhat.com/2527713
Le ven. 9 oct. 2026 à 16:04, Neal Gompa ngompa13@gmail.com a écrit :
On Fri, Oct 9, 2026 at 9:59 AM Nicolas Chauvet kwizart@gmail.com wrote:
Le ven. 9 oct. 2026 à 14:36, Neal Gompa ngompa13@gmail.com a écrit :
On Fri, Oct 9, 2026 at 8:03 AM Abdallah Shehawey shehawey9@gmail.com wrote:
I am the upstream author of whatsapp-desktop, an independent GPL-3.0-or-later desktop client for WhatsApp Web with tray integration, notifications, themes, configurable fonts and privacy controls. It requires an existing WhatsApp account and Internet access and is not affiliated with Meta or WhatsApp.
I have prepared a source-only application packaging proposal. It installs JavaScript and data and depends on a separately packaged Electron >= 40, < 41; the application build neither downloads Electron nor runs npm. The application tests and package builds pass in clean Ubuntu 24.04 and Fedora 44 environments. Fedora rpmlint reports zero errors and warnings.
Public source review artifacts (Fedora SPEC/SRPM and Debian .dsc/orig/quilt sources, with checksums): https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
Merged packaging changes and validation: https://github.com/abdallah-shehawey/whatsapp-desktop/pull/6
Debian ITP, acknowledged by the BTS: https://bugs.debian.org/1150415
The key prerequisite is Electron: it is not currently packaged in the target official archives, and Debian's runtime request https://bugs.debian.org/842420 remains open. The ITP is explicitly blocked on that runtime work. I have not completed Electron source packaging, and these application artifacts are not an accepted or currently installable official archive package.
Electron is present in Fedora. It is currently in Rawhide (which will eventually branch to become Fedora 46), but it is present. However, we will only maintain one version of Electron, Right now, nodejs-electron is on v43, and it will likely move to v44 soon.
I would like to pursue inclusion in Fedora's official repositories. Could a Fedora packager advise on the Electron prerequisite, review eligibility for this independent web-service client, and sponsorship for a new contributor? The directly downloadable SPEC and SRPM are linked above. I understand that a formal Fedora Package Review must be filed through a Bugzilla account tied to my Fedora Account System email; this email is a request for packaging guidance, not a claim that a formal review has already been filed.
You'll need to update your software to work with newer versions of Electron. I don't know much about your application beyond that, since I haven't looked. Perhaps someone else familiar with Nodejs applications may be willing to look at this once you've updated your code.
Out of curiosity, which package uses this packaged electron in rawhide ?
Having every electron based application to rely on the same pace update of the base electron package looks unreliable. That's because not every package maintainer can rise up at the same time (not even talking about having upstream rebased at the same time, dealing with various difficulties or even real life issues). It's not more reliable to have a slow pace electron package because it's just moving the same problem.
I would prefer to amend the alternate version policy (that allows a "per-version" namespace of a given package). That way we can have a "per-consumer" based namespace. So having electron-whatsapp-desktop and others (signal, elementary, etc).
That's the only way forward to this long standing issue.
Unless you want to maintain all the different chromium codestreams in parallel, that's probably not happening.
That would be a given. The alternative is to bundle the electron into the "consumer application" which is what is done with the element
It was introduced in order to package podman-desktop, which has a review request: https://bugzilla.redhat.com/2527713
So it means podman-desktop will control the pace of the nodejs-electron package updates. This is very much "the problem". Another electron enabled package could end-up having a different pace.
In the whatsapp-desktop case , the electron used is >= 40 < 41. So it will likely never be able to use a system(aka podman paced based) nodejs-electron package.
@Abdallah since you've suggested to package whatsapp-desktop, you will likely need to experiment that in a copr repository with a nodejs-electron-whatsapp-desktop (or any other name).
Hope this helps.
On Fri, Oct 9, 2026 at 10:43 AM Nicolas Chauvet kwizart@gmail.com wrote:
Le ven. 9 oct. 2026 à 16:04, Neal Gompa ngompa13@gmail.com a écrit :
On Fri, Oct 9, 2026 at 9:59 AM Nicolas Chauvet kwizart@gmail.com wrote:
Le ven. 9 oct. 2026 à 14:36, Neal Gompa ngompa13@gmail.com a écrit :
On Fri, Oct 9, 2026 at 8:03 AM Abdallah Shehawey shehawey9@gmail.com wrote:
I am the upstream author of whatsapp-desktop, an independent GPL-3.0-or-later desktop client for WhatsApp Web with tray integration, notifications, themes, configurable fonts and privacy controls. It requires an existing WhatsApp account and Internet access and is not affiliated with Meta or WhatsApp.
I have prepared a source-only application packaging proposal. It installs JavaScript and data and depends on a separately packaged Electron >= 40, < 41; the application build neither downloads Electron nor runs npm. The application tests and package builds pass in clean Ubuntu 24.04 and Fedora 44 environments. Fedora rpmlint reports zero errors and warnings.
Public source review artifacts (Fedora SPEC/SRPM and Debian .dsc/orig/quilt sources, with checksums): https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
Merged packaging changes and validation: https://github.com/abdallah-shehawey/whatsapp-desktop/pull/6
Debian ITP, acknowledged by the BTS: https://bugs.debian.org/1150415
The key prerequisite is Electron: it is not currently packaged in the target official archives, and Debian's runtime request https://bugs.debian.org/842420 remains open. The ITP is explicitly blocked on that runtime work. I have not completed Electron source packaging, and these application artifacts are not an accepted or currently installable official archive package.
Electron is present in Fedora. It is currently in Rawhide (which will eventually branch to become Fedora 46), but it is present. However, we will only maintain one version of Electron, Right now, nodejs-electron is on v43, and it will likely move to v44 soon.
I would like to pursue inclusion in Fedora's official repositories. Could a Fedora packager advise on the Electron prerequisite, review eligibility for this independent web-service client, and sponsorship for a new contributor? The directly downloadable SPEC and SRPM are linked above. I understand that a formal Fedora Package Review must be filed through a Bugzilla account tied to my Fedora Account System email; this email is a request for packaging guidance, not a claim that a formal review has already been filed.
You'll need to update your software to work with newer versions of Electron. I don't know much about your application beyond that, since I haven't looked. Perhaps someone else familiar with Nodejs applications may be willing to look at this once you've updated your code.
Out of curiosity, which package uses this packaged electron in rawhide ?
Having every electron based application to rely on the same pace update of the base electron package looks unreliable. That's because not every package maintainer can rise up at the same time (not even talking about having upstream rebased at the same time, dealing with various difficulties or even real life issues). It's not more reliable to have a slow pace electron package because it's just moving the same problem.
I would prefer to amend the alternate version policy (that allows a "per-version" namespace of a given package). That way we can have a "per-consumer" based namespace. So having electron-whatsapp-desktop and others (signal, elementary, etc).
That's the only way forward to this long standing issue.
Unless you want to maintain all the different chromium codestreams in parallel, that's probably not happening.
That would be a given. The alternative is to bundle the electron into the "consumer application" which is what is done with the element
It was introduced in order to package podman-desktop, which has a review request: https://bugzilla.redhat.com/2527713
So it means podman-desktop will control the pace of the nodejs-electron package updates. This is very much "the problem". Another electron enabled package could end-up having a different pace.
Ideally there's a SIG for Electron applications so that it can be coordinated and multiple people can work together instead. This is not a new problem for us in Fedora and it is generally expected that we work with various upstreams to resolve the issue.
In the whatsapp-desktop case , the electron used is >= 40 < 41. So it will likely never be able to use a system(aka podman paced based) nodejs-electron package.
The packager is the upstream developer. They can fix it.
-- 真実はいつも一つ!/ Always, there's only one truth!
Le ven. 9 oct. 2026 à 16:54, Neal Gompa ngompa13@gmail.com a écrit :
On Fri, Oct 9, 2026 at 10:43 AM Nicolas Chauvet kwizart@gmail.com wrote:
Le ven. 9 oct. 2026 à 16:04, Neal Gompa ngompa13@gmail.com a écrit :
On Fri, Oct 9, 2026 at 9:59 AM Nicolas Chauvet kwizart@gmail.com wrote:
Le ven. 9 oct. 2026 à 14:36, Neal Gompa ngompa13@gmail.com a écrit :
On Fri, Oct 9, 2026 at 8:03 AM Abdallah Shehawey shehawey9@gmail.com wrote:
I am the upstream author of whatsapp-desktop, an independent GPL-3.0-or-later desktop client for WhatsApp Web with tray integration, notifications, themes, configurable fonts and privacy controls. It requires an existing WhatsApp account and Internet access and is not affiliated with Meta or WhatsApp.
I have prepared a source-only application packaging proposal. It installs JavaScript and data and depends on a separately packaged Electron >= 40, < 41; the application build neither downloads Electron nor runs npm. The application tests and package builds pass in clean Ubuntu 24.04 and Fedora 44 environments. Fedora rpmlint reports zero errors and warnings.
Public source review artifacts (Fedora SPEC/SRPM and Debian .dsc/orig/quilt sources, with checksums): https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
Merged packaging changes and validation: https://github.com/abdallah-shehawey/whatsapp-desktop/pull/6
Debian ITP, acknowledged by the BTS: https://bugs.debian.org/1150415
The key prerequisite is Electron: it is not currently packaged in the target official archives, and Debian's runtime request https://bugs.debian.org/842420 remains open. The ITP is explicitly blocked on that runtime work. I have not completed Electron source packaging, and these application artifacts are not an accepted or currently installable official archive package.
Electron is present in Fedora. It is currently in Rawhide (which will eventually branch to become Fedora 46), but it is present. However, we will only maintain one version of Electron, Right now, nodejs-electron is on v43, and it will likely move to v44 soon.
I would like to pursue inclusion in Fedora's official repositories. Could a Fedora packager advise on the Electron prerequisite, review eligibility for this independent web-service client, and sponsorship for a new contributor? The directly downloadable SPEC and SRPM are linked above. I understand that a formal Fedora Package Review must be filed through a Bugzilla account tied to my Fedora Account System email; this email is a request for packaging guidance, not a claim that a formal review has already been filed.
You'll need to update your software to work with newer versions of Electron. I don't know much about your application beyond that, since I haven't looked. Perhaps someone else familiar with Nodejs applications may be willing to look at this once you've updated your code.
Out of curiosity, which package uses this packaged electron in rawhide ?
Having every electron based application to rely on the same pace update of the base electron package looks unreliable. That's because not every package maintainer can rise up at the same time (not even talking about having upstream rebased at the same time, dealing with various difficulties or even real life issues). It's not more reliable to have a slow pace electron package because it's just moving the same problem.
I would prefer to amend the alternate version policy (that allows a "per-version" namespace of a given package). That way we can have a "per-consumer" based namespace. So having electron-whatsapp-desktop and others (signal, elementary, etc).
That's the only way forward to this long standing issue.
Unless you want to maintain all the different chromium codestreams in parallel, that's probably not happening.
That would be a given. The alternative is to bundle the electron into the "consumer application" which is what is done with the element
It was introduced in order to package podman-desktop, which has a review request: https://bugzilla.redhat.com/2527713
So it means podman-desktop will control the pace of the nodejs-electron package updates. This is very much "the problem". Another electron enabled package could end-up having a different pace.
Ideally there's a SIG for Electron applications so that it can be coordinated and multiple people can work together instead. This is not a new problem for us in Fedora and it is generally expected that we work with various upstreams to resolve the issue.
In the whatsapp-desktop case , the electron used is >= 40 < 41. So it will likely never be able to use a system(aka podman paced based) nodejs-electron package.
The packager is the upstream developer. They can fix it.
I would oppose the same to the podman-desktop maintainer. Electron upstream is supposed to be at 44.x version, but the packaged version in rawhide is 43.2 (not even the latest bugfix from 43.7). So it really means "electron" and consumer versions are tightly coupled.
Nicolas Chauvet venit, vidit, dixit 2026-10-09 18:14:20:
Le ven. 9 oct. 2026 à 16:54, Neal Gompa ngompa13@gmail.com a écrit :
On Fri, Oct 9, 2026 at 10:43 AM Nicolas Chauvet kwizart@gmail.com wrote:
Le ven. 9 oct. 2026 à 16:04, Neal Gompa ngompa13@gmail.com a écrit :
On Fri, Oct 9, 2026 at 9:59 AM Nicolas Chauvet kwizart@gmail.com wrote:
Le ven. 9 oct. 2026 à 14:36, Neal Gompa ngompa13@gmail.com a écrit :
On Fri, Oct 9, 2026 at 8:03 AM Abdallah Shehawey shehawey9@gmail.com wrote: > > I am the upstream author of whatsapp-desktop, an independent > GPL-3.0-or-later desktop client for WhatsApp Web with tray > integration, notifications, themes, configurable fonts and privacy > controls. It requires an existing WhatsApp account and Internet access > and is not affiliated with Meta or WhatsApp. > > I have prepared a source-only application packaging proposal. It > installs JavaScript and data and depends on a separately packaged > Electron >= 40, < 41; the application build neither downloads Electron > nor runs npm. The application tests and package builds pass in clean > Ubuntu 24.04 and Fedora 44 environments. Fedora rpmlint reports zero > errors and warnings. > > Public source review artifacts (Fedora SPEC/SRPM and Debian > .dsc/orig/quilt sources, with checksums): > https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging... > > Merged packaging changes and validation: > https://github.com/abdallah-shehawey/whatsapp-desktop/pull/6 > > Debian ITP, acknowledged by the BTS: > https://bugs.debian.org/1150415 > > The key prerequisite is Electron: it is not currently packaged in the > target official archives, and Debian's runtime request > https://bugs.debian.org/842420 remains open. The ITP is explicitly > blocked on that runtime work. I have not completed Electron source > packaging, and these application artifacts are not an accepted or > currently installable official archive package. >
Electron is present in Fedora. It is currently in Rawhide (which will eventually branch to become Fedora 46), but it is present. However, we will only maintain one version of Electron, Right now, nodejs-electron is on v43, and it will likely move to v44 soon.
> I would like to pursue inclusion in Fedora's official repositories. > Could a Fedora packager advise on the Electron prerequisite, review > eligibility for this independent web-service client, and sponsorship > for a new contributor? The directly downloadable SPEC and SRPM are > linked above. I understand that a formal Fedora Package Review must be > filed through a Bugzilla account tied to my Fedora Account System > email; this email is a request for packaging guidance, not a claim > that a formal review has already been filed. >
You'll need to update your software to work with newer versions of Electron. I don't know much about your application beyond that, since I haven't looked. Perhaps someone else familiar with Nodejs applications may be willing to look at this once you've updated your code.
Out of curiosity, which package uses this packaged electron in rawhide ?
Having every electron based application to rely on the same pace update of the base electron package looks unreliable. That's because not every package maintainer can rise up at the same time (not even talking about having upstream rebased at the same time, dealing with various difficulties or even real life issues). It's not more reliable to have a slow pace electron package because it's just moving the same problem.
I would prefer to amend the alternate version policy (that allows a "per-version" namespace of a given package). That way we can have a "per-consumer" based namespace. So having electron-whatsapp-desktop and others (signal, elementary, etc).
That's the only way forward to this long standing issue.
Unless you want to maintain all the different chromium codestreams in parallel, that's probably not happening.
That would be a given. The alternative is to bundle the electron into the "consumer application" which is what is done with the element
It was introduced in order to package podman-desktop, which has a review request: https://bugzilla.redhat.com/2527713
So it means podman-desktop will control the pace of the nodejs-electron package updates. This is very much "the problem". Another electron enabled package could end-up having a different pace.
Ideally there's a SIG for Electron applications so that it can be coordinated and multiple people can work together instead. This is not a new problem for us in Fedora and it is generally expected that we work with various upstreams to resolve the issue.
In the whatsapp-desktop case , the electron used is >= 40 < 41. So it will likely never be able to use a system(aka podman paced based) nodejs-electron package.
The packager is the upstream developer. They can fix it.
I would oppose the same to the podman-desktop maintainer. Electron upstream is supposed to be at 44.x version, but the packaged version in rawhide is 43.2 (not even the latest bugfix from 43.7). So it really means "electron" and consumer versions are tightly coupled.
Exactly. Electron is a prime example for a "runtime" that needs to be available in different versions. Without versioned packages, flatpak is the solution to that. Also, it could help isolate whatever whatsapp is trying to do.
As for podman-desktop: I see no explicit version dependency on electron in the spec file. There might be a practical one. OTOH: I don't know why one wouldn't want to use upstream's flatpak. It can't be for fear of containerisation ;-)
Michael
On 2026-10-09 11:17 AM, Michael J Gruber wrote:
As for podman-desktop: I see no explicit version dependency on electron in the spec file. There might be a practical one. OTOH: I don't know why one wouldn't want to use upstream's flatpak. It can't be for fear of containerisation 😉
Flathub's build system doesn't support shared, reusable build definitions for shared components or recursive resolution of build-time dependencies, so dependencies like Electron typically supplied using a pre-built binary rather than built from source. (For Electron, specifically, I am not aware of any packages that build that dependency from source.)
At least in principle, having a complete pipeline to build everything from source means that we can bring up new architectures, we can demonstrate compliance with license terms that require us to supply the source to binaries we distribute, we know that the software was built on trusted hosts, etc, etc.
On 2026-10-09 7:43 AM, Nicolas Chauvet wrote:
In the whatsapp-desktop case , the electron used is >= 40 < 41. So it will likely never be able to use a system(aka podman paced based) nodejs-electron package.
Electron 40 was initially released in Jan 2026 and discontinued in July 2026:
https://releases.electronjs.org/schedule
That's gonna be a very hard sell.
On 2026-10-09 5:35 AM, Neal Gompa wrote:
However, we will only maintain one version of Electron
That's the most likely outcome, but Fedora is a project that distributes the work of its maintainers, so what will actually happen depends a lot on what work maintainers do.
So, let's talk about what futures are possible:
It's difficult to make very clear statements about Chromium's release schedule for a couple of reasons. First, because releases tagged in their git repo mirror don't appear to agree with the published release schedule. There are releases tagged in the 150 release series after the 152 release series was promoted to stable, which the release documentation suggests would not happen. Second, because in September, Chromium switched from a 4-week release schedule to a 2-week release schedule, and it's possible that undocumented release practices from the past are no longer relevant.
If we ignore tagged releases and use only their documentation as reference, then there are two ways to look at Chromium's release model. One is that Chromium publishes two release channels, labeled "stable" and "extended stable". Both are illustrated as rolling releases, ending the maintenance of a release series once a new release series is promoted to production. One on a two week cadence and the other on an eight week cadence. The other point of view is that Chromium has a staggered release model in which every fourth release is supported for eight weeks while the rest are supported for two weeks.
https://chromiumdash.appspot.com/releases?platform=Linux
https://chromiumdash.appspot.com/schedule
https://chromium.googlesource.com/chromium/src/+/lkgr/docs/process/release_c...
https://github.com/chromium/chromium/tags
Fortunately, Electron aligns with and uses Chromium's "extended stable" release branches. Unfortunately, Electron declares a branch "supported" for 24 weeks, despite the fact that the underlying Chromium release is only maintained for 8 weeks. It's not a great security posture, but it is what it is.
https://www.electronjs.org/docs/latest/tutorial/electron-timelines
https://releases.electronjs.org/schedule
There are a couple of challenges with maintaining release parity with the upstream project (i.e. maintaining all three active branches of Electron in Fedora). One is that the Electron package is based on the Chromium package, and that package is a rolling release stream that follows the "stable" release channel. Even a single release of Electron is going to diverge from Chromium, and we don't know yet how much work it's going to be to update the Electron package's copy of the Chromium source and patches, independent of the Chromium package.
If the Electron package maintains release parity, then every 8 weeks its maintainers need to introduce a new package, deprecate an old package, update three releases of the Electron package, and make sure that all of the packages that rely on Electron have been rebuilt against an actively supported release. We'll also end up with two Electron runtimes that don't have upstream maintenance of the Chromium codebase, which is... not great.
If the Electron package rolls from release to release, then the maintainers still have to deal with diverging from the Chromium package and they still have to make sure that packages that use Electron have been rebuilt against an active release. It's possible that building Electron applications against a rolling-release Electron runtime will be more work than maintaining 3 releases of Electron, but that's not clear yet. The security posture is better here, there's fewer packages to maintain, fewer builds, and less work with new packages / deprecating packages during a release.
Neal and I have talked about creating a Chromium SIG for people who are interested in maintenance of Electron and cef, but I haven't done the initial setup yet. If you are interested, let me know so that I can ping you when it's set up.
On 2026-10-10 9:40 PM, Gordon Messmer wrote:
If the Electron package maintains release parity, then every 8 weeks its maintainers need to introduce a new package, deprecate an old package, update three releases of the Electron package, and make sure that all of the packages that rely on Electron have been rebuilt against an actively supported release. We'll also end up with two Electron runtimes that don't have upstream maintenance of the Chromium codebase, which is... not great.
For what it's worth, I'll retract that statement.
I've (locally) built Electron 43.8.3, and it looks like once Chromium stops publishing releases, the Electron developers start cherry-picking patches including security fixes:
https://github.com/electron/electron/commits/43-x-y/patches
That being the case, I don't think there's any security basis for keeping just one Electron release in Fedora, and the only real limitation we have is available labor.
If anyone wants to learn to maintain an Electron release, let me know.
I suspect they are cherry-picking only a very small subset of the available upstream security fixes. I'm not a Chromium developer, but I would expect a *lot* more than that.
On 2026-10-28 5:38 PM, Michael Catanzaro via devel wrote:
I suspect they are cherry-picking only a very small subset of the available upstream security fixes. I'm not a Chromium developer, but I would expect a *lot* more than that.
I'm seeing one cherry-pick commit a day, roughly, but each of those commits is dozens of cherry-picks from Chromium.
How many do you expect?
Thank you for pointing out the existing Rawhide Electron package. My initial assessment was incomplete: I checked the stable Fedora environment and missed nodejs-electron in Rawhide.
I have now tested application 1.9.12 with Fedora's official nodejs-electron-43.2.0-1.fc46 in a private Rawhide container. The revised Fedora SPEC uses Electron >=43,<44, matches the actual native window class and consolidates duplicate icon files. The source RPM rebuilt and the application package installed successfully; rpmlint reports zero errors and warnings.
The real logged-out WhatsApp QR page, Settings, Fonts and About rendered, the preloads/IPC worked, private settings writes were read back and the native WM_CLASS matched the desktop entry. This is a basic compatibility check using X11 with GPU disabled; signed-in messaging/calls, native Wayland and hardware acceleration remain unvalidated. I will need to validate later Electron major versions as Fedora moves forward.
Revised SPEC: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/download/pack...
Revised SRPM: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/download/pack...
Review artifacts and validation details: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
Package review: https://bugzilla.redhat.com/show_bug.cgi?id=2548541
Sponsorship request: https://forge.fedoraproject.org/packaging/sponsors/issues/802
I would appreciate application review and maintainer sponsorship guidance. Debian's separate runtime prerequisite remains unresolved. I understand that neither the discussion nor these application checks constitute archive acceptance.
Best regards, Abdallah Shehawey FAS: abdallah-shehawey
On Fri, 09 Oct 2026 05:03:09 -0700, Abdallah Shehawey shehawey9@gmail.com wrote:
I am the upstream author of whatsapp-desktop, an independent GPL-3.0-or-later desktop client for WhatsApp Web with tray integration, notifications, themes, configurable fonts and privacy controls. It requires an existing WhatsApp account and Internet access and is not affiliated with Meta or WhatsApp. I have prepared a source-only application packaging proposal. It installs JavaScript and data and depends on a separately packaged Electron >= 40, < 41; the application build neither downloads Electron nor runs npm. The application tests and package builds pass in clean Ubuntu 24.04 and Fedora 44 environments. Fedora rpmlint reports zero errors and warnings. Public source review artifacts (Fedora SPEC/SRPM and Debian .dsc/orig/quilt sources, with checksums): https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging... Merged packaging changes and validation: https://github.com/abdallah-shehawey/whatsapp-desktop/pull/6 Debian ITP, acknowledged by the BTS: https://bugs.debian.org/1150415 The key prerequisite is Electron: it is not currently packaged in the target official archives, and Debian's runtime request https://bugs.debian.org/842420 remains open. The ITP is explicitly blocked on that runtime work. I have not completed Electron source packaging, and these application artifacts are not an accepted or currently installable official archive package. I would like to pursue inclusion in Fedora's official repositories. Could a Fedora packager advise on the Electron prerequisite, review eligibility for this independent web-service client, and sponsorship for a new contributor? The directly downloadable SPEC and SRPM are linked above. I understand that a formal Fedora Package Review must be filed through a Bugzilla account tied to my Fedora Account System email; this email is a request for packaging guidance, not a claim that a formal review has already been filed. Regards, Abdallah Shehawey
Hi Gordon,
Thank you for explaining the runtime maintenance tradeoffs and the value of Fedora's source-built Electron package.
I agree that Electron 40 is no longer a suitable supported target; the upstream schedule lists its end of life as July 1, 2026: https://releases.electronjs.org/schedule
The >= 40, < 41 requirement was in my initial Fedora proposal. I revised the Fedora package to require Electron >= 43, < 44 after testing Fedora Rawhide's official nodejs-electron-43.2.0-1.fc46. The updated proposal and results were posted in this thread and in the review: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/... https://bugzilla.redhat.com/show_bug.cgi?id=2548541#c1
The immutable revision 2 SPEC, source RPM and checksums are here: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
This application package contains no downloaded Electron runtime and uses Fedora's packaged runtime. I rebuilt the source RPM, installed the resulting application RPM in an isolated Rawhide environment, and obtained zero rpmlint errors and warnings. I checked the real logged-out QR page, Settings, Fonts, About, IPC preferences and native window class using private XDG directories and X11 with GPU disabled. Signed-in messaging and calls, native Wayland and hardware acceleration remain unvalidated; I have not expanded the dependency range to later major versions.
These Fedora packaging changes are separate from the existing stable 1.9.12 bundled release, which still uses Electron 40, and the Debian proposal, whose runtime prerequisite remains unresolved. Neither the application review nor sponsorship has been approved.
My immediate contribution is application compatibility testing and source packaging. I would appreciate guidance on how application maintainers could coordinate with the proposed Chromium SIG when it is established, and on the next steps for review and packager mentorship. I cannot yet make a commitment to maintaining the Electron runtime itself.
Thank you, Abdallah Shehawey Fedora account: abdallah-shehawey
On Fri, 09 Oct 2026 05:03:09 -0700, Abdallah Shehawey shehawey9@gmail.com wrote:
I am the upstream author of whatsapp-desktop, an independent GPL-3.0-or-later desktop client for WhatsApp Web with tray integration, notifications, themes, configurable fonts and privacy controls. It requires an existing WhatsApp account and Internet access and is not affiliated with Meta or WhatsApp. I have prepared a source-only application packaging proposal. It installs JavaScript and data and depends on a separately packaged Electron >= 40, < 41; the application build neither downloads Electron nor runs npm. The application tests and package builds pass in clean Ubuntu 24.04 and Fedora 44 environments. Fedora rpmlint reports zero errors and warnings. Public source review artifacts (Fedora SPEC/SRPM and Debian .dsc/orig/quilt sources, with checksums): https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging... Merged packaging changes and validation: https://github.com/abdallah-shehawey/whatsapp-desktop/pull/6 Debian ITP, acknowledged by the BTS: https://bugs.debian.org/1150415 The key prerequisite is Electron: it is not currently packaged in the target official archives, and Debian's runtime request https://bugs.debian.org/842420 remains open. The ITP is explicitly blocked on that runtime work. I have not completed Electron source packaging, and these application artifacts are not an accepted or currently installable official archive package. I would like to pursue inclusion in Fedora's official repositories. Could a Fedora packager advise on the Electron prerequisite, review eligibility for this independent web-service client, and sponsorship for a new contributor? The directly downloadable SPEC and SRPM are linked above. I understand that a formal Fedora Package Review must be filed through a Bugzilla account tied to my Fedora Account System email; this email is a request for packaging guidance, not a claim that a formal review has already been filed. Regards, Abdallah Shehawey
Hi all,
I am following up on Fedora review #2548541 and sponsorship request #802 with a refreshed source-only application snapshot for whatsapp-desktop 1.9.20 (RPM revision 2).
The current SPEC had kept the dated 1.9.12 review Source0 after application version updates. I fixed that in merged PR #14: review sources now use a version-specific tag, and the source-package builder checks the expanded URL/version against committed source and records them in the build manifest.
Review snapshot, checksums and validation: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
SPEC: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/download/pack...
SRPM: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/download/pack...
Fresh validation on 2026-10-25: - 399 application checks pass. Both GitHub CI jobs pass, and a fresh Ubuntu 24.04 build from the .dsc passes with no Lintian package errors. - The SRPM rebuilt and the application RPM installed in a fresh Rawhide container using official nodejs-electron-43.2.0-1.fc46. rpmlint reports zero errors and warnings. - The installed application rendered the real logged-out WhatsApp login page and QR canvas, Settings, Fonts and About with actual preloads/IPC. Private preference write/readback, hide/show and the native WM_CLASS matching the desktop entry passed. - All 10 published review assets were downloaded anonymously and matched their SHA256 checksums.
These are basic compatibility checks using private data, Xvfb X11 and disabled GPU acceleration. Signed-in messaging/calls, native Wayland, hardware acceleration and full desktop portal integration remain unvalidated. The application package still uses Fedora's runtime and does not bundle or download Electron during its build. Debian's separate runtime prerequisite remains unresolved.
I am still seeking an application reviewer and a packager sponsor/mentor: https://bugzilla.redhat.com/show_bug.cgi?id=2548541 https://forge.fedoraproject.org/packaging/sponsors/issues/802
Could someone help with the application review or advise on a suitable sponsorship path? This update does not claim review approval, sponsorship or official archive acceptance.
Thank you, Abdallah Shehawey FAS: abdallah-shehawey
On Sun, 11 Oct 2026 03:47:10 -0500, Abdallah Shehawey shehawey9@gmail.com wrote:
Hi Gordon, Thank you for explaining the runtime maintenance tradeoffs and the value of Fedora's source-built Electron package. I agree that Electron 40 is no longer a suitable supported target; the upstream schedule lists its end of life as July 1, 2026: https://releases.electronjs.org/schedule The >= 40, < 41 requirement was in my initial Fedora proposal. I revised the Fedora package to require Electron >= 43, < 44 after testing Fedora Rawhide's official nodejs-electron-43.2.0-1.fc46. The updated proposal and results were posted in this thread and in the review: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/... https://bugzilla.redhat.com/show_bug.cgi?id=2548541#c1 The immutable revision 2 SPEC, source RPM and checksums are here: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging... This application package contains no downloaded Electron runtime and uses Fedora's packaged runtime. I rebuilt the source RPM, installed the resulting application RPM in an isolated Rawhide environment, and obtained zero rpmlint errors and warnings. I checked the real logged-out QR page, Settings, Fonts, About, IPC preferences and native window class using private XDG directories and X11 with GPU disabled. Signed-in messaging and calls, native Wayland and hardware acceleration remain unvalidated; I have not expanded the dependency range to later major versions. These Fedora packaging changes are separate from the existing stable 1.9.12 bundled release, which still uses Electron 40, and the Debian proposal, whose runtime prerequisite remains unresolved. Neither the application review nor sponsorship has been approved. My immediate contribution is application compatibility testing and source packaging. I would appreciate guidance on how application maintainers could coordinate with the proposed Chromium SIG when it is established, and on the next steps for review and packager mentorship. I cannot yet make a commitment to maintaining the Electron runtime itself. Thank you, Abdallah Shehawey Fedora account: abdallah-shehawey On Fri, 09 Oct 2026 05:03:09 -0700, Abdallah Shehawey < shehawey9@gmail.com> wrote: > I am the upstream author of whatsapp-desktop, an independent GPL-3.0-or-later desktop client for WhatsApp Web with tray integration, notifications, themes, configurable fonts and privacy controls. It requires an existing WhatsApp account and Internet access and is not affiliated with Meta or WhatsApp. > > I have prepared a source-only application packaging proposal. It installs JavaScript and data and depends on a separately packaged Electron >= 40, < 41; the application build neither downloads Electron nor runs npm. The application tests and package builds pass in clean Ubuntu 24.04 and Fedora 44 environments. Fedora rpmlint reports zero errors and warnings. > > Public source review artifacts (Fedora SPEC/SRPM and Debian .dsc/orig/quilt sources, with checksums): > https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
Merged packaging changes and validation: >
https://github.com/abdallah-shehawey/whatsapp-desktop/pull/6 > > Debian ITP, acknowledged by the BTS: > https://bugs.debian.org/1150415 > > The key prerequisite is Electron: it is not currently packaged in the target official archives, and Debian's runtime request https://bugs.debian.org/842420 remains open. The ITP is explicitly blocked on that runtime work. I have not completed Electron source packaging, and these application artifacts are not an accepted or currently installable official archive package. > > I would like to pursue inclusion in Fedora's official repositories. Could a Fedora packager advise on the Electron prerequisite, review eligibility for this independent web-service client, and sponsorship for a new contributor? The directly downloadable SPEC and SRPM are linked above. I understand that a formal Fedora Package Review must be filed through a Bugzilla account tied to my Fedora Account System email; this email is a request for packaging guidance, not a claim that a formal review has already been filed. > > Regards, > Abdallah Shehawey
Dne 25. 10. 26 v 15:33 Abdallah Shehawey napsal(a):
Hi all,
I am following up on Fedora review #2548541 and sponsorship request #802 with a refreshed source-only application snapshot for whatsapp-desktop 1.9.20 (RPM revision 2).
The current SPEC had kept the dated 1.9.12 review Source0 after application version updates. I fixed that in merged PR #14: review sources now use a version-specific tag, and the source-package builder checks the expanded URL/version against committed source and records them in the build manifest.
Review snapshot, checksums and validation: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
SPEC: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/download/pack...
I don't think that:
~~~
Requires: electron >= 43 Requires: electron < 44
~~~
does what you think it does. If I am not mistaken, this essentially allows any `electron` version.
I think that you want to use the following instead:
~~~
Requires: (electron >= 43 with electron < 44)
~~~
But generally, I don't like these restrictions unless they are somehow asserted, e.g. in `%check` section. My opinion is that if electron should be bumped to 44+, this package should become FTBFS. It would allow electron maintainers to know as well as to you.
Vít
SRPM: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/download/pack...
Fresh validation on 2026-10-25:
- 399 application checks pass. Both GitHub CI jobs pass, and a fresh
Ubuntu 24.04 build from the .dsc passes with no Lintian package errors.
- The SRPM rebuilt and the application RPM installed in a fresh
Rawhide container using official nodejs-electron-43.2.0-1.fc46. rpmlint reports zero errors and warnings.
- The installed application rendered the real logged-out WhatsApp
login page and QR canvas, Settings, Fonts and About with actual preloads/IPC. Private preference write/readback, hide/show and the native WM_CLASS matching the desktop entry passed.
- All 10 published review assets were downloaded anonymously and
matched their SHA256 checksums.
These are basic compatibility checks using private data, Xvfb X11 and disabled GPU acceleration. Signed-in messaging/calls, native Wayland, hardware acceleration and full desktop portal integration remain unvalidated. The application package still uses Fedora's runtime and does not bundle or download Electron during its build. Debian's separate runtime prerequisite remains unresolved.
I am still seeking an application reviewer and a packager sponsor/mentor: https://bugzilla.redhat.com/show_bug.cgi?id=2548541 https://forge.fedoraproject.org/packaging/sponsors/issues/802
Could someone help with the application review or advise on a suitable sponsorship path? This update does not claim review approval, sponsorship or official archive acceptance.
Thank you, Abdallah Shehawey FAS: abdallah-shehawey
On Sun, 11 Oct 2026 03:47:10 -0500, Abdallah Shehawey shehawey9@gmail.com wrote:
Hi Gordon, Thank you for explaining the runtime maintenance tradeoffs and the value of Fedora's source-built Electron package. I agree that Electron 40 is no longer a suitable supported target; the upstream schedule lists its end of life as July 1, 2026: https://releases.electronjs.org/schedule The >= 40, < 41 requirement was in my initial Fedora proposal. I revised the Fedora package to require Electron >= 43, < 44 after testing Fedora Rawhide's official nodejs-electron-43.2.0-1.fc46. The updated proposal and results were posted in this thread and in the review: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/FMU2S7YOLQY33XZLSWI5BDIJ3XWGHASQ/ https://bugzilla.redhat.com/show_bug.cgi?id=2548541#c1 The immutable revision 2 SPEC, source RPM and checksums are here: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging-review-2026-10-10-fedora43 This application package contains no downloaded Electron runtime and uses Fedora's packaged runtime. I rebuilt the source RPM, installed the resulting application RPM in an isolated Rawhide environment, and obtained zero rpmlint errors and warnings. I checked the real logged-out QR page, Settings, Fonts, About, IPC preferences and native window class using private XDG directories and X11 with GPU disabled. Signed-in messaging and calls, native Wayland and hardware acceleration remain unvalidated; I have not expanded the dependency range to later major versions. These Fedora packaging changes are separate from the existing stable 1.9.12 bundled release, which still uses Electron 40, and the Debian proposal, whose runtime prerequisite remains unresolved. Neither the application review nor sponsorship has been approved. My immediate contribution is application compatibility testing and source packaging. I would appreciate guidance on how application maintainers could coordinate with the proposed Chromium SIG when it is established, and on the next steps for review and packager mentorship. I cannot yet make a commitment to maintaining the Electron runtime itself. Thank you, Abdallah Shehawey Fedora account: abdallah-shehawey On Fri, 09 Oct 2026 05:03:09 -0700, Abdallah Shehawey <shehawey9@gmail.com> wrote: > I am the upstream author of whatsapp-desktop, an independent GPL-3.0-or-later desktop client for WhatsApp Web with tray integration, notifications, themes, configurable fonts and privacy controls. It requires an existing WhatsApp account and Internet access and is not affiliated with Meta or WhatsApp. > > I have prepared a source-only application packaging proposal. It installs JavaScript and data and depends on a separately packaged Electron >= 40, < 41; the application build neither downloads Electron nor runs npm. The application tests and package builds pass in clean Ubuntu 24.04 and Fedora 44 environments. Fedora rpmlint reports zero errors and warnings. > > Public source review artifacts (Fedora SPEC/SRPM and Debian .dsc/orig/quilt sources, with checksums): > https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging-review-2026-10-09 > > Merged packaging changes and validation: > https://github.com/abdallah-shehawey/whatsapp-desktop/pull/6 > > Debian ITP, acknowledged by the BTS: > https://bugs.debian.org/1150415 > > The key prerequisite is Electron: it is not currently packaged in the target official archives, and Debian's runtime request https://bugs.debian.org/842420 remains open. The ITP is explicitly blocked on that runtime work. I have not completed Electron source packaging, and these application artifacts are not an accepted or currently installable official archive package. > > I would like to pursue inclusion in Fedora's official repositories. Could a Fedora packager advise on the Electron prerequisite, review eligibility for this independent web-service client, and sponsorship for a new contributor? The directly downloadable SPEC and SRPM are linked above. I understand that a formal Fedora Package Review must be filed through a Bugzilla account tied to my Fedora Account System email; this email is a request for packaging guidance, not a claim that a formal review has already been filed. > > Regards, > Abdallah Shehawey
Hi Vít,
Thank you for the SPEC feedback. I have replaced the two separate Requires lines with the single rich dependency you suggested:
Requires: (electron >= 43 with electron < 44)
The same dependency is also a BuildRequires, so one runtime provider must satisfy both bounds before the application builds. Once Fedora's runtime leaves the supported range, the application package becomes FTBFS. In a fresh Rawhide container, the current range resolves to nodejs-electron-43.2.0-1.fc46; changing it to Electron >= 44, < 45 fails dependency resolution as expected. This gate does not need to execute Electron during the build.
The source packages also now declare Node.js >= 20 for their test suite. The X11 check added since the previous snapshot fails with EINVAL on Ubuntu 24.04's archive Node.js 18.19.1. The Debian build now runs on Debian 13, with archive Node.js 20.19.2, instead of implicitly relying on a newer runner-local Node.js.
Refreshed source-only review snapshot for application 1.10.3, built from main commit d0534a7b3c0e92ab252f7a115aea570e7b4cccc8:
SPEC: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/download/pack...
SRPM: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/download/pack...
All review sources, checksums, validation record and evidence: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
Fresh validation on 2026-11-11: - Both PR #16 and post-merge main CI jobs pass. - Rawhide passes all 426 application checks across 25 suites, plus source-only installation and metadata checks. - The Rawhide SRPM rebuilds and its application RPM installs against Fedora's official runtime; rpmlint 2.10.0 reports 0 errors and 0 warnings on both packages. - The installed application loads the real logged-out WhatsApp page and QR canvas; Settings, Fonts and About use their real preloads and IPC. Private preference write/readback, hide/show and WM_CLASS matching pass. - The Debian .dsc rebuilds on Debian 13 with no Lintian errors. It executes 422 checks; four desktop watcher assertions skip because gsettings is absent from that buildroot and pass in Rawhide. - All published review assets were downloaded anonymously and matched SHA256SUMS.
The runtime check uses private user data, an unprivileged user, Xvfb X11 and disabled GPU acceleration. Signed-in messaging/calls, native Wayland, hardware acceleration and full desktop portal integration remain unvalidated. Rawhide availability does not establish stable Fedora availability, and Debian's separate Electron prerequisite remains unresolved.
My work remains application compatibility and source packaging. I am still seeking an application reviewer and a packager sponsor/mentor: https://bugzilla.redhat.com/show_bug.cgi?id=2548541#c3 https://forge.fedoraproject.org/packaging/sponsors/issues/802#issuecomment-1...
Regards, Abdallah Shehawey FAS: abdallah-shehawey
On Sun, 25 Oct 2026 07:33:25 -0700, Abdallah Shehawey shehawey9@gmail.com wrote:
Hi all, I am following up on Fedora review #2548541 and sponsorship request #802 with a refreshed source-only application snapshot for whatsapp-desktop 1.9.20 (RPM revision 2). The current SPEC had kept the dated 1.9.12 review Source0 after application version updates. I fixed that in merged PR #14: review sources now use a version-specific tag, and the source-package builder checks the expanded URL/version against committed source and records them in the build manifest. Review snapshot, checksums and validation: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging... SPEC: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/download/pack... SRPM: https://github.com/abdallah-shehawey/whatsapp-desktop/releases/download/pack... Fresh validation on 2026-10-25: - 399 application checks pass. Both GitHub CI jobs pass, and a fresh Ubuntu 24.04 build from the .dsc passes with no Lintian package errors. - The SRPM rebuilt and the application RPM installed in a fresh Rawhide container using official nodejs-electron-43.2.0-1.fc46. rpmlint reports zero errors and warnings. - The installed application rendered the real logged-out WhatsApp login page and QR canvas, Settings, Fonts and About with actual preloads/IPC. Private preference write/readback, hide/show and the native WM_CLASS matching the desktop entry passed. - All 10 published review assets were downloaded anonymously and matched their SHA256 checksums. These are basic compatibility checks using private data, Xvfb X11 and disabled GPU acceleration. Signed-in messaging/calls, native Wayland, hardware acceleration and full desktop portal integration remain unvalidated. The application package still uses Fedora's runtime and does not bundle or download Electron during its build. Debian's separate runtime prerequisite remains unresolved. I am still seeking an application reviewer and a packager sponsor/mentor: https://bugzilla.redhat.com/show_bug.cgi?id=2548541 https://forge.fedoraproject.org/packaging/sponsors/issues/802 Could someone help with the application review or advise on a suitable sponsorship path? This update does not claim review approval, sponsorship or official archive acceptance. Thank you, Abdallah Shehawey FAS: abdallah-shehawey On Sun, 11 Oct 2026 03:47:10 -0500, Abdallah Shehawey shehawey9@gmail.com wrote: > Hi Gordon, > > Thank you for explaining the runtime maintenance tradeoffs and the value of Fedora's source-built Electron package. > > I agree that Electron 40 is no longer a suitable supported target; the upstream schedule lists its end of life as July 1, 2026: > https://releases.electronjs.org/schedule > > The >= 40, < 41 requirement was in my initial Fedora proposal. I revised the Fedora package to require Electron >= 43, < 44 after testing Fedora Rawhide's official nodejs-electron-43.2.0-1.fc46. The updated proposal and results were posted in this thread and in the review: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
https://bugzilla.redhat.com/show_bug.cgi?id=2548541#c1 > > The immutable
revision 2 SPEC, source RPM and checksums are here: > https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
This application package contains no downloaded Electron runtime and
uses Fedora's packaged runtime. I rebuilt the source RPM, installed the resulting application RPM in an isolated Rawhide environment, and obtained zero rpmlint errors and warnings. I checked the real logged-out QR page, Settings, Fonts, About, IPC preferences and native window class using private XDG directories and X11 with GPU disabled. Signed-in messaging and calls, native Wayland and hardware acceleration remain unvalidated; I have not expanded the dependency range to later major versions. > > These Fedora packaging changes are separate from the existing stable 1.9.12 bundled release, which still uses Electron 40, and the Debian proposal, whose runtime prerequisite remains unresolved. Neither the application review nor sponsorship has been approved. > > My immediate contribution is application compatibility testing and source packaging. I would appreciate guidance on how application maintainers could coordinate with the proposed Chromium SIG when it is established, and on the next steps for review and packager mentorship. I cannot yet make a commitment to maintaining the Electron runtime itself. > > Thank you, > Abdallah Shehawey > Fedora account: abdallah-shehawey > > > On Fri, 09 Oct 2026 05:03:09 -0700, Abdallah Shehawey shehawey9@gmail.com wrote: > > I am the upstream author of whatsapp-desktop, an independent GPL-3.0-or-later desktop client for WhatsApp Web with tray integration, notifications, themes, configurable fonts and privacy controls. It requires an existing WhatsApp account and Internet access and is not affiliated with Meta or WhatsApp. > > > > I have prepared a source-only application packaging proposal. It installs JavaScript and data and depends on a separately packaged Electron >= 40, < 41; the application build neither downloads Electron nor runs npm. The application tests and package builds pass in clean Ubuntu 24.04 and Fedora 44 environments. Fedora rpmlint reports zero errors and warnings. > > > > Public source review artifacts (Fedora SPEC/SRPM and Debian .dsc/orig/quilt sources, with checksums): > > https://github.com/abdallah-shehawey/whatsapp-desktop/releases/tag/packaging...
Merged packaging changes and validation: > >
https://github.com/abdallah-shehawey/whatsapp-desktop/pull/6 > > > > Debian ITP, acknowledged by the BTS: > > https://bugs.debian.org/1150415 > > > > The key prerequisite is Electron: it is not currently packaged in the target official archives, and Debian's runtime request https://bugs.debian.org/842420 remains open. The ITP is explicitly blocked on that runtime work. I have not completed Electron source packaging, and these application artifacts are not an accepted or currently installable official archive package. > > > > I would like to pursue inclusion in Fedora's official repositories. Could a Fedora packager advise on the Electron prerequisite, review eligibility for this independent web-service client, and sponsorship for a new contributor? The directly downloadable SPEC and SRPM are linked above. I understand that a formal Fedora Package Review must be filed through a Bugzilla account tied to my Fedora Account System email; this email is a request for packaging guidance, not a claim that a formal review has already been filed. > > > > Regards, > > Abdallah Shehawey