Embed a build result badge whereever you need it. Select from
the options below and copy the result over to your README or on
your website, and enjoy it refresh automatically whenever the
build result changes.
I would rather not touch anything outside of this package that could affect other packages in this project.
But as I was able to fix something similar for 15.3 using BuildRequires in the spec file, this should be possible for fedora as well.
unresolvable: have choice for pkgconfig(jack): jack-audio-connection-kit-devel pipewire-jack-audio-connection-kit-devel, have choice for nodejs-devel needed by nodejs-packaging: nodejs-devel nodejs16-devel
I tried it like this:
# help decide for dependency
BuildRequires: pipewire-jack-audio-connection-kit-devel
BuildRequires: nodejs16-devel
But that seems to create some conflict with npm16. Maybe we need the "newer" version of nodejs-devel. We could try BuildRequires: nodejs-devel >=17 or something like that for fedora.
@dheidler Odd version numbers of nodejs like 17 are development versions. Even numbers are maintained LTS versions. Most projects use LTS versions and not development versions and if you build them like signal-desktop with nodejs16 it wont work if electron is built with nodejs17!
nodejs-election should be built with nodejs16 on all distributions!
I'm using nodejs16 on all opensuse distros.
I was unable to get resolved build dependencies for fedora otherwise.
Feel free to send a SR to change it on fedora - I myself am happy if it builds at all for fedora as I don't consider it as very important.
I think the system node copy is only used for running the typescript compiler, electron ships its own fork of node (and libuv) inside.
I even tried to unbundle libuv (it is backward compatible; Arch uses system libuv even in ancient node versions) but it did not work — Electron has its own patches not matching any upstream libuv version.
I'm doing a major review of our spec for electron 19 merge, does anyone know why we block building on 32bit platforms? Especially since armv7 is explicitely supported by upstream.
I don't really care about other arches, but right now even arm64 fails to link, which would be a regression. So i'm trying to unbundle some libs (abseil, spirv) to reduce binary size.
Hi, just a user of the repo here on Fedora 37. The package seems to have been rebuilt 6 or 7 times in the past week or so, with no apparent change to the source RPM other than the release number. What's prompted this and what changed?
as of todays update to 33.3.1 on a leap 15.6 with element-web and element-desktop installed from this same repo ( https://build.opensuse.org/project/show/devel:languages:nodejs ) i am only briefly seeing content inside the element-desktop ( 1.11.88 ) and the it vanishes and the whole element-desktop window content is pure white only and only the element-desktop menu such as file, edit, view, window, help ... I only briefly see my last chat with a person and briefly the element-desktop gui as it used to be then its shortly after that replaced by a seemingly white layer or fully white content only. any help? where to bugreport? thanks.
Please try to delete the cache folders .config/Element/GPUCache/ etc. and try to restart. If it does not work, bug reports go here https://bugzilla.opensuse.org/
I did this step but it didnt, help (much) I briefly have seen my chat a bit longer now, I have just posted a single jpeg picture inside the chat a few lines ago (yesterday) which seems to be loading (attempting to load) the little circle as placeholder for the jpeg rotates but it never displays that jpeg image and maybe exactly when it tries to load it or tries to draw it it seems to go white. I even see the cursor at the very bottom to chat write a new line into the chat and all. all seems pretty normal for element-desktop gui and application until it blanks out (white out).
no the element-desktop application continues to be displayed on the KDE desktop of 15.6 leap, the menu and the window in general keeps working, minimize maximize etc, but the content gets covered or disappears by a fully white layer it seems. I briefly see my chat. will try that cache deletion .config/Element/GPUCache/ from above and see what I can find out. thanks.
Ccache worked without me doing anything in spec, until rpmbuild broke it by introducing subbuilddir. To use ccache locally, add --ccache parameter to osc build.
Comments 36
@ithod not sure how to resolve the fedora deps. My latest change didn't really help: https://build.opensuse.org/package/rdiff/devel:languages:nodejs/nodejs-electron?linkrev=base&rev=5
This comment has been deleted
Hm - adding the Prefer: to the spec doesn't seem to have an effect.
This comment has been deleted
I would rather not touch anything outside of this package that could affect other packages in this project. But as I was able to fix something similar for 15.3 using BuildRequires in the spec file, this should be possible for fedora as well.
I tried it like this:
But that seems to create some conflict with npm16. Maybe we need the "newer" version of nodejs-devel. We could try
BuildRequires: nodejs-devel >=17or something like that for fedora.This comment has been deleted
Because we do not have any debug symbols at all.
This comment has been deleted
@dheidler Odd version numbers of nodejs like 17 are development versions. Even numbers are maintained LTS versions. Most projects use LTS versions and not development versions and if you build them like signal-desktop with nodejs16 it wont work if electron is built with nodejs17!
nodejs-election should be built with nodejs16 on all distributions!
I'm using nodejs16 on all opensuse distros. I was unable to get resolved build dependencies for fedora otherwise. Feel free to send a SR to change it on fedora - I myself am happy if it builds at all for fedora as I don't consider it as very important.
Take a look at the tumbleweed build log, it picks nodejs17!
Let's see if my latest change fixes that
I think the system node copy is only used for running the typescript compiler, electron ships its own fork of node (and libuv) inside.
I even tried to unbundle libuv (it is backward compatible; Arch uses system libuv even in ancient node versions) but it did not work — Electron has its own patches not matching any upstream libuv version.
Please branch memory-constraints and build it for Fedora 36 in devel:languages:nodejs
I'm doing a major review of our spec for electron 19 merge, does anyone know why we block building on 32bit platforms? Especially since armv7 is explicitely supported by upstream.
This comment has been deleted
Yes - I think build failed on armv7h and i586 and I'm not sure how to fix that, so it was disabled to save ressources.
I managed to fix all assembling errors, but unfortunately on i586 neither BFD nor GoLD can handle “Google Ultron powered by Download More RAM”.
You could have some entry here: https://build.opensuse.org/package/view_file/devel:languages:nodejs/nodejs-electron/_constraints?expand=1
But I guess you can just have 4GB of RAM in total on i586.
I don't really care about other arches, but right now even arm64 fails to link, which would be a regression. So i'm trying to unbundle some libs (abseil, spirv) to reduce binary size.
Hi, just a user of the repo here on Fedora 37. The package seems to have been rebuilt 6 or 7 times in the past week or so, with no apparent change to the source RPM other than the release number. What's prompted this and what changed?
that usually means that a dependency got rebuilt.
Unfortunately fedora does not have build-compare which would eliminate spurious rebuilds: boo#1206734
Is this a problem specifically for Fedora 36 and later, or has it been for all Fedora versions?
all fedora, it never had reproducible builds on OBS
as of todays update to 33.3.1 on a leap 15.6 with element-web and element-desktop installed from this same repo ( https://build.opensuse.org/project/show/devel:languages:nodejs ) i am only briefly seeing content inside the element-desktop ( 1.11.88 ) and the it vanishes and the whole element-desktop window content is pure white only and only the element-desktop menu such as file, edit, view, window, help ... I only briefly see my last chat with a person and briefly the element-desktop gui as it used to be then its shortly after that replaced by a seemingly white layer or fully white content only. any help? where to bugreport? thanks.
Please try to delete the cache folders
.config/Element/GPUCache/etc. and try to restart. If it does not work, bug reports go here https://bugzilla.opensuse.org/I did this step but it didnt, help (much) I briefly have seen my chat a bit longer now, I have just posted a single jpeg picture inside the chat a few lines ago (yesterday) which seems to be loading (attempting to load) the little circle as placeholder for the jpeg rotates but it never displays that jpeg image and maybe exactly when it tries to load it or tries to draw it it seems to go white. I even see the cursor at the very bottom to chat write a new line into the chat and all. all seems pretty normal for element-desktop gui and application until it blanks out (white out).
Do you get a core dump?
no the element-desktop application continues to be displayed on the KDE desktop of 15.6 leap, the menu and the window in general keeps working, minimize maximize etc, but the content gets covered or disappears by a fully white layer it seems. I briefly see my chat. will try that cache deletion .config/Element/GPUCache/ from above and see what I can find out. thanks.
I am not even sure how to properly bugreport this to what area on the opensuse bugzilla, i created this: https://bugzilla.opensuse.org/show_bug.cgi?id=1235830 thanks for teaching a bit more about this.
todays nodejs-electron update to rpm -qi nodejs-electron Name : nodejs-electron Version : 35.3.0 Release : lp156.1.1 Architecture: x86_64 Install Date: Thu 08 May 2025 03:33:18 PM CEST Group : Development/Languages/NodeJS Size : 285651938
renders the still-current element-desktop (with element-web installed) packages faulty and nonfunctional, core dumped segfault crash upon startup.
rpm -qi element-desktop Name : element-desktop Version : 1.11.99 Release : lp156.1.2 Architecture: x86_64 Install Date: Sun 27 Apr 2025 04:51:24 PM CEST Group : Unspecified Size : 20335527
thanks.
can reproduce. Reverted the package until i can find what's wrong and fix it.
gh#electron/electron#47007
Hey could you add ccache or sccache detection to the spec file? I think to use either you have to add them as cc_wrapper when calling gn.
I managed to add that to spec file by adding these lines to the spec file:
Add this at the top of the spec file, e.g. as in after the build options before 'Name:'
define if ccache should be used or not
%define useccache %{lua: \ if posix.access('/etc/profile.d/build_ccache.sh', 'f') then\ print(1)\ else\ print(0)\ end}
define if sccache should be used or not
Also works with rust
%define usesccache %{lua: \ if posix.access('/etc/profile.d/build_sccache.sh', 'f') then\ print(1)\ else\ print(0)\ end}
Then add this further down in %build before calling gn: %if %{useccache} myconf_gn+=' cc_wrapper="/usr/bin/ccache"' %endif
%if %{usesccache} myconf_gn+=' cc_wrapper="/usr/bin/sccache"' %endif
Ccache worked without me doing anything in spec, until rpmbuild broke it by introducing subbuilddir. To use ccache locally, add --ccache parameter to osc build.