March 2025 - openSUSE Factory - openSUSE Mailing Lists

New zypper media backend and parallel download support
by Benjamin Zeller 14 Apr '25

14 Apr '25

Hello everyone, the new libzypp-17.36.4 / zypper-1.14.87 combination brings some features that hopefully will help to improve the slowness in fetching packages and metadata. They currently need to be enabled manually because they are still in early stages: 1) zypper fetches packages during update/dup/install using parallel connections ( yes finally ). Currently the feature must be manually enabled by setting a environment variable like so: > env ZYPP_PCK_PRELOAD=1 zypper dup The number of concurrent connections is controlled by a setting in zypp.conf: download.max_concurrent_connections Currently the default is 5, but for me setting it higher performs even better. 2) A simpler more efficient media backend, it drops some of the overhead like fetching metalinks or splitting one file over multiple servers and should behave much better on connection reuse, in our internal test this always outperforms the current one. This is seperate from the parallel package downloads but should bring some benefits when fetching metadata from servers on zypper refresh. It's enabled with: > env ZYPP_CURL2=1 zypper ref Since both features do not actively fetch mirrorlink informations from the server it is best to combine them with a existing feature, specifying the metalink/mirror information in each .repo file. Otherwise especially the parallel downloader will only fetch from the baseUrl which might be slower. Example for my Tumbleweed repo file: > [download.opensuse.org-oss] > name=Main Repository (OSS) > enabled=1 > autorefresh=1 > metalink=https://download.opensuse.org/tumbleweed/repo/oss/repodata/repomd.… > path=/ > type=rpm-md > keeppackages=0 It replaces the baseUrl= key with metalink= key and URL. But be aware that this will also download signature keys from the mirrors instead of download.opensuse.org. So for production use better stick to baseUrl= for now. Finally some numbers for those who enjoy it: Downloaded roughly 100Mb, around 250 Packages over my 100Mbit/s MultiCurl ( current default ): ------------------------------------------------------------------------------------------ Executed in 68.68 secs usr time 42.41 millis 0.38 millis 42.03 millis sys time 70.80 millis 1.02 millis 69.77 millis ZYPP_CURL2=1 enabled ( new experimental backend ): ------------------------------------------------------------------------------------------ Executed in 29.55 secs usr time 44.33 millis 0.00 millis 44.33 millis sys time 57.07 millis 1.42 millis 55.65 millis ZYPP_PCK_PRELOAD=1 enabled (parallel downloads): ------------------------------------------------------------------------------------------ Executed in 13.13 secs usr time 142.10 millis 0.38 millis 141.72 millis sys time 232.80 millis 1.02 millis 231.78 millis Download of 407 Packages ~1.02Gb into empty rootfs ( postgresql virtualbox go mariadb ruby ) MultiCurl ( current default ): ________________________________________________________ Executed in 281.15 secs usr time 83.34 millis 0.36 millis 82.99 millis sys time 186.04 millis 1.03 millis 185.01 millis ZYPP_CURL2=1 enabled ( new experimental backend ): ________________________________________________________ Executed in 208.51 secs usr time 76.77 millis 0.00 millis 76.77 millis sys time 168.91 millis 2.02 millis 166.89 millis ZYPP_PCK_PRELOAD=1 enabled (parallel downloads): ________________________________________________________ Executed in 119.60 secs usr time 1.92 secs 0.36 millis 1.92 secs sys time 3.58 secs 1.03 millis 3.58 secs Cheers, Benjamin

16 49

Re: Kernel 5.13.x and IIO devices
by ASSI 13 Apr '25

13 Apr '25

ASSI writes: > After the update to the new kernel my IIO device files can't be read > most of the time: > > cat: '/sys/bus/iio/devices/iio:device0/in_temp_input': Device or resource busy > cat: '/sys/bus/iio/devices/iio:device0/in_humidityrelative_input': Device or resource busy > cat: '/sys/bus/iio/devices/iio:device0/in_pressure_input': Device or resource busy > > Is that a known change somewhere that requires some new settings to recover > from or a bug? That particular IIC bus has a BME280 and DS3231M in > daisy-chain. It seems at least the BME280 is handled differently than before: > > [ 2147.889803] [ T2128] bmp280 1-0076: Measurement cycle didn't complete. > > Oversampling ratio is set to 1, so one read per second should not > produce such errors. Not unexpectedly, no change in behaviour after updating to kernel 13.1. I have tried to find any changes that would explain this in the kernel change log, but I've come up empty… there is some way of skipping interrupts now and going for polling instead, but as I read it this relates to network only, not IIO devices. Have any kernel options changed that would explain what I am seeing and/or what configuration allows me to run this system with a 13.x kernel successfully? For the moment I can keep it at 12.x, but that won't be an option indefinitely of course. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

1 1

libglew change broke openscad
by JA McInnes 12 Apr '25

12 Apr '25

It looks like an update to libGLEW early this month has broken openscad. I'm getting this error now openscad: symbol lookup error: openscad: undefined symbol: __GLXEW_SGIX_fbconfig Is this permanent? I can get openscad from flatpak or other sources. thanks -John M.

6 11

openSUSE:Factory - Build fail notification
by DimStar / Dominique Leuenberger 08 Apr '25

08 Apr '25

Dear Package maintainers and hackers. Below package(s) in openSUSE:Factory have had problems for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted. - deepin-file-manager: Unresolvable - lucene++: Uninstallable: nothing provides libboost_filesystem.so.1.86.0()(64bit) needed by liblucene++0-3.0.8.x86_64 - poedit: Unresolvable - pulseview: Uninstallable: nothing provides libboost_filesystem.so.1.86.0()(64bit) needed by pulseview-0.4.2.x86_64 - python-sigstore: Unresolvable - rstudio: Uninstallable: nothing provides libboost_chrono.so.1.86.0()(64bit) needed by rstudio-2024.04.0+735.x86_64 - wesnoth: Uninstallable: nothing provides libboost_context.so.1.86.0()(64bit) needed by wesnoth-campaign-server-1.18.3.x86_64 Unless somebody is stepping up and submitting fixes, the listed package(s) are going to be removed from openSUSE:Factory. Kind regards, DimStar / Dominique Leuenberger <dimstar(a)opensuse.org>

4 4

pcre deprecation and move to pcre2
by Andreas Stieger 03 Apr '25

03 Apr '25

Hello, while bumping pcre2 I noted that pcre2 has new maintainers: https://build.opensuse.org/request/show/1252897 https://github.com/PCRE2Project/pcre2/releases/tag/pcre2-10.45 (from 2025-02-25) We had pcre2 in the distribution for 9 years now (by yours truly), intended to replace pcre "soon". https://build.opensuse.org/request/show/312616 The old library was in quasi-maintenance mode at the time already, and is "unmaintained since 2018". The old pcre library should not only be considered deprecated - but dead and insecure now. We should get rid of it - CWE-1104, OWASP Top 10:2021 #6, and all. I zipped through some easy ones... https://build.opensuse.org/request/show/1253625 proftpd https://build.opensuse.org/request/show/1253337 sngrep https://build.opensuse.org/request/show/1253141 zabbix https://build.opensuse.org/request/show/1253581 apache2-mod_auth_openidc Olaf picked up ocaml-pcre2 and started to look at coccinelle - thanks. https://build.opensuse.org/request/show/1253797 ocaml-pcre2 https://build.opensuse.org/request/show/1254244 coccinelle Some need processing please: https://build.opensuse.org/request/show/1253263 apache2-mod_security2 https://build.opensuse.org/request/show/1253341 liblognorm https://build.opensuse.org/request/show/1253347 rasqal For zsh boo#1201811 did not get far the time. I took a stab: https://build.opensuse.org/request/show/1254254 I would like to discuss at which point are we happy to just whack pcre from the distribution for security reasons. Only 37 binary packages depend on the lib, probably less than 30 once the above is through and some available patches are added. Should we just kill it now and get it over with? Some previous work including patches: https://archlinux.org/todo/move-to-pcre2/ https://md.archlinux.org/p/LPxw6tavl#/ Good night, Andreas

2 4

no longer setting devel project attribute
by Andreas Stieger 03 Apr '25

03 Apr '25

Hello, We no longer seem to set the devel project attribute on new packages added to openSUSE:Factory. Seen four days ago in SR#1252975 and needing request a changedevelproject request to fix, see osc log -M openSUSE:Factory/pwtool. Now seen in SR#1253607 a second time. I understand that BsRequestActionSubmitexecute_accept is supposed to do this, but I see that OBS:InitializeDevelProject was removed. Was this intentional, maybe in preparation of the migration to the git backend? Andreas

4 7

[opensuse-factory] reproducible builds status 2025-03
by Bernhard M. Wiedemann 31 Mar '25

31 Mar '25

Hi, I made some more patches this month. The rpm issue gets partially resolved the way upstream intended by using a variable in %{_smp_mflags} ... and maybe in %jobs Note: %jobs is SUSE-specific and we want to reduce its use for more portable .spec files. Meanwhile, I'm thinking about how to advance part3 of my RBOS-project. That is the addition of all other bit-reproducible Factory packages to the 3k that were already part of it. One relatively simple solution would be to construct a 'RBOS-conflicts' metapackage that Conflicts with all the known-bad packages and thus prevents their accidental installation. There could be a few edge cases such as ceph, that only starts to differ slightly after the year 2038 or colord, that is fully reproducible as long as build machines all have AVX2 available. Should these be blocked, because they are not fully reproducible or be allowed, because it is somehow possible to verify the correctness of binaries? Here are the autogenerated bits: last month's status: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… Last months' reproducible builds project updates (including my work): https://reproducible-builds.org/reports/2025-02/ I uploaded https://rb.zq1.de/compare.factory-20250331/ today https://rb.zq1.de/spec/glossar.txt explains the meaning of below values: total-packages: 16013 (+20) build-tried: 15955 (+15) build-failed: 55 (+42) build-n-a: 166 (-7) build-succeeded: 15734 (-20) build-official-failed+na: 101 (-1) build-compare-failed: 169 (-4) build-compare-succeeded: 15565 (-16) verify-failed: 216 (-10) verified-semi-reproducible: 15349 (-52) verified-bit-identical: 15092 (-52) bit-by-bit-identical: 15453 (-23) not-bit-by-bit-identical: 281 (+3) not-bit-by-bit-identicalcheck: 281 (+3) https://rb.zq1.de/compare.factory-20250331/graph.png shows the change over time https://rb.zq1.de/compare.factory-20250331/unreproduciblerings.txt lists very unreproducible core packages (bootstrap+DVD) Of the badly unreproducible packages, 2 were in ring0 24 were in ring1 That makes it 26/4043 => 0.64 % which is below the overall average of 169/15734 => 1.07 % 281/15734 => 1.79 % of packages are not perfectly reproducible package notes: ==> ./avr-libc/.rb.notes <== minor .a strange varying hardlinks from fdupes ==> ./bash/.rb.notes <== => SR 1251754 1251745 PGO (date+PID+other) ==> ./bcc/.rb.notes <== => SR 1245394 1245394 https://github.com/iovisor/bcc/pull/5213 https://build.opensuse.org/request/show/1245248 by wfrisch bcc lua ==> ./ck/.rb.notes <== = https://github.com/concurrencykit/ck/issues/243 => https://github.com/concurrencykit/ck/pull/184 FTBFS-j1 ==> ./curl/.rb.notes <== FTBFS-2033 found range good=2087143195 bad=2087145119 ==> ./deepin-daemon/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1238196 FTBFS osc build --noservice --clean --vm-type=kvm standard ==> ./difftastic/.rb.notes <== => SR 1251184 1251169 => https://github.com/Wilfred/difftastic/pull/813 race rust/llvm ==> ./dmd/.rb.notes <== random TMP label - lea offset(%rip),%rbx # <_TMP36993 + ofs> ==> ./firefox-esr/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1239446 FTBFS-race ==> ./font-manager/.rb.notes <== date in 0.9.4 xml ==> ./framework_tool/.rb.notes <== date+time --- old /usr/bin/framework_tool (objdump) ==> ./fritzing/.rb.notes <== https://bugzilla.opensuse.org/show_bug.cgi?id=1239967 fritzing random ==> ./gawk/.rb.notes <== => SR 1256211 1254398 PGO ==> ./ghostty/.rb.notes <== ghc toolchain debuginfo ==> ./glucat/.rb.notes <== pdflatex toolchain pdf /usr/share/doc/packages/glucat-doc/GluCat-API-reference-manual.pdf ==> ./grex/.rb.notes <== [ 568s] failures: ==> ./gstreamer-plugins-rs/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1237097 = https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/issues/599 date ; rust/llvm asm diff [build] jobs = 1 doesn't help ==> ./gzdoom/.rb.notes <== parallelism unreproducible with project=openSUSE:Factory repo=standard debuginfo=--debuginfo multibuildrbkall ==> ./julia/.rb.notes <== stuck in -j1 build => workaround -j3 ==> ./kbd/.rb.notes <== => SR 1265521 1265349 1265750 https://bugzilla.opensuse.org/show_bug.cgi?id=1240348 2024-12 https://github.com/legionus/kbd/commit/eebaa3b69efd9e3d218f3436dc43ff334002… ==> ./libcorrect/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1238370 CPU SSE detection ==> ./linkerd-cli-edge/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1240347 date+time: new//usr/src/debug/linkerd-cli-edge-25.3.4/multicluster/static/generated_multicluster_templates.gogen.go ==> ./lua-language-server/.rb.notes <== FTBFS-2031 --build-opt=--vm-custom-opt=-rtc base=2042-01-25T00:00:00 failed ==> ./m4/.rb.notes <== => SR 1254473 PGO ==> ./mingw32-gcc/.rb.notes <== ?binutils toolchain? ==> ./mpitests/.rb.notes <== FTBFS-CPU? ==> ./octave-forge-geometry/.rb.notes <== random path, octave toolchain? --- old /usr/lib/debug/.dwz/octave-forge-geometry-4.0.0-1.1.x86_64 (objdump) ==> ./octave-forge-strings/.rb.notes <== random: (similar to other octave packages) There is randomness embedded in debuginfo: /tmp/oct-v8Vm5t/strings-1.3.1/src and pcregexp.cc.59dddf9b ==> ./os-autoinst/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1239686 FTBFS osc build --vm-type=kvm -j1 --clean --noservice standard ==> ./pixelorama/.rb.notes <== timestamp + ordering + random ==> ./postgresql17/.rb.notes <== = https://www.postgresql.org/message-id/ba8e1bc0-8a99-45b7-8397-3f2e94415e03%… FTBFS-2024-11-03 - solved by postgresql17-jsonb_jsonpath.patch found range good=1730573413 bad=1730576847 ==> ./pspp/.rb.notes <== = https://savannah.gnu.org/bugs/index.php?65485 parallelism issue = https://bugzilla.opensuse.org/show_bug.cgi?id=1221321 FTBFS-nocheck ==> ./python-HyperKitty/.rb.notes <== => SR 1252100 1252068 => https://gitlab.com/mailman/hyperkitty/-/merge_requests/656 = https://gitlab.com/mailman/hyperkitty/-/issues/527 toolchain issue?, random from ["python3.11", "build_static_files/manage.py", "compress", "--force"] ==> ./python-nanobind/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1239153 FTBFS-j1 osc build --vm-type=kvm --noservice --clean -j1 standard ==> ./python-pandas/.rb.notes <== = https://github.com/pandas-dev/pandas/issues/60078 ASLR+parallelism+other? mesonpy toolchain random; random .pyc - ref counters? ==> ./python-pgmagick/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1239745 FTBFS osc build -j1 --clean --noservice --vm-type=kvm standard ==> ./python-postorius/.rb.notes <== FTBFS-j1 ==> ./python-scipy/.rb.notes <== .a file hashes in RECORD vary ==> ./python3-espressomd/.rb.notes <== => SR 1255106 1255097 date ==> ./python311/.rb.notes <== PGO + :doc parallelism ==> ./python314/.rb.notes <== = https://github.com/python/cpython/issues/130979 = https://github.com/sphinx-doc/sphinx/issues/13419 Sphinx toolchain race ==> ./qgis/.rb.notes <== parallelism ==> ./rpm/.rb.notes <== => https://github.com/rpm-software-management/rpm/pull/2762 = https://github.com/rpm-software-management/rpm/issues/932 Cannot set Build Date from changelog anymore ==> ./sad/.rb.notes <== => SR 1252059 = https://github.com/ms-jpq/sad/issues/359 rust+python random uuid https://github.com/ms-jpq/sad/blob/6c65d52211e79298c0e1b1496a7287e98cb8e813… ==> ./sequoia-sq/.rb.notes <== = https://gitlab.com/sequoia-pgp/sequoia-sq/-/issues/535 FTBFS-2026-10-05 #=> https://gitlab.com/sequoia-pgp/sequoia-sq/-/merge_requests/554 FTBFS-2026-01-31 ==> ./starship/.rb.notes <== rust ; maybe some low-entropy (filesys) issue left => https://github.com/starship/starship/pull/5352 filesys readdir, rust ==> ./warewulf4/.rb.notes <== => SR 1248768 by cgoll ; embedded CPU-core count ==> ./wrk/.rb.notes <== => SR 1251668 = https://github.com/LuaJIT/LuaJIT/issues/1348 toolchain = https://github.com/wg/wrk/issues/507 hash order issue ==> ./xmlgraphics-fop/.rb.notes <== => SR 1250478 = https://bugzilla.opensuse.org/show_bug.cgi?id=1237094 date+random => SR 866261 ==> ./yazi/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1239491 = https://github.com/lukaslueg/built/issues/80 parallelism/core-count with debuginfo => https://github.com/xiph/rav1e/pull/3412

1 0

gamescope is broken: "_scmsync.obsinfo file must not be part of the git repository. "
by Rein Fernhout (Levitating) 31 Mar '25

31 Mar '25

I just received a notification from the OBS that a package (gamescope[1]) I intended to help maintain has broken. It refuses to build with the following message: broken: ERROR:root:ERROR: The _scmsync.obsinfo file must not be part of the git repository. I am not really sure what changed here, because the last revision was over a month ago and build without issue. This package is developed at /pool using git even long before we started the whole migration. I am maintainer on the OBS but I don't actually have write access to the /pool repository because absolutely nobody maintaining this can figure out how the SCM link works. [1]: https://build.opensuse.org/package/show/games:tools/gamescope

3 2

openSUSE:Factory - Build fail notification
by DimStar / Dominique Leuenberger 30 Mar '25

30 Mar '25

Dear Package maintainers and hackers. Below package(s) in openSUSE:Factory have had problems for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted. - budgie-calendar-applet: Unresolvable - budgie-extras: Unresolvable - budgie-haste-applet: Unresolvable - budgie-screenshot-applet: Unresolvable - vala-panel-appmenu: Unresolvable Unless somebody is stepping up and submitting fixes, the listed package(s) are going to be removed from openSUSE:Factory. Kind regards, DimStar / Dominique Leuenberger <dimstar(a)opensuse.org>

3 3

New Tumbleweed snapshot 20250329 released!
by Dominique Leuenberger 30 Mar '25

30 Mar '25

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio… Please do not reply to this email to report issues, rather file a bug on bugzilla.opensuse.org. For more information on filing bugs please see https://en.opensuse.org/openSUSE:Submitting_bug_reports Packages changed: 389-ds openSUSE-release (20250328 -> 20250329) === Details === ==== 389-ds ==== Subpackages: lib389 libsvrcore0 - Add python-psutil requires (boo#1240340). ==== openSUSE-release ==== Version update (20250328 -> 20250329) Subpackages: openSUSE-release-appliance-custom openSUSE-release-dvd - automatically generated by openSUSE-release-tools/pkglistgen

1 0