August 2023 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Leap 42.3 Build 0312 released!
by Ludwig Nussel 25 Apr '24

25 Apr '24

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&version=42.3&bui… https://bugzilla.opensuse.org/buglist.cgi?product=openSUSE%20Distribution&q… When you reply to discuss some issues, make sure to change the subject. Please use the test plan at https://docs.google.com/spreadsheets/d/1AGKijKpKiJCB616-bHVoNQuhWHpQLHPWCb3… to record your testing efforts and use bugzilla to report bugs. Packages changed: biosdevname btrfsmaintenance conduit gconf2-branding-openSUSE (42.1 -> 42.3) ibus kactivitymanagerd kde-user-manager kernel-source (4.4.73 -> 4.4.74) libxml2 libzypp (16.12.0 -> 16.13.0) lightdm marble mc plasma5-integration plasma5-openSUSE postgresql (9.4 -> 9.6) python-coverage (3.7.1 -> 4.3.4) ucode-intel (20160714 -> 20170511) yast2-bootloader (3.2.22 -> 3.2.23) yast2-ntp-client (3.2.9 -> 3.2.12) === Details === ==== biosdevname ==== - Duplicate naming of SRIOV VFs by biosdevname when VPD_DCM Strings are present in VFs (bsc#1042185) * Add: biosdevname_avoid_duplicates.patch ==== btrfsmaintenance ==== - Require btrfsprogs (bsc#1047226) - update to 0.2 - updated documentation - no hardcoded paths to external utilities - fixed logger name typos for 'journal' target - defrag fixes (sysconfig, find arguments) - Removed patch: balance-typo.patch - Added patch: sysconfig-override-trim.diff - Add balance-typo.patch (bnc#986543) - version 0.1.1 - fix typo and make journal logging target work - cron refresh: remove bashism - Removed patches: * 0003-Add-COPYING-file.patch * 0011-cron-refresh-remove-debuggiong-output.patch - cron script symlinks are not created on first installation (bsc#907343) - add COPYING to package - refresh script: remove extra messages - add uninstall targets - fix refresh service - adjust sysconfig defaults - Add more package dependencies (cron, zypp-plugin) - minor bugfixes - Add supplements(btrfsprogs) - initial version 0.1 ==== conduit ==== Subpackages: conduit-lang - Use python-vobject instead of vobject per python-vobject change in 42.3. ==== gconf2-branding-openSUSE ==== Version update (42.1 -> 42.3) - do not build novell-sound-theme in the gconf2-branding-SLED build to prevent duplicated binaries in openSUSE Leap. The novell-sound-theme is taken from gconf2-branding-SLES sources on both the SLED product and the SLES WE module. bsc#1046099 - bump versions ==== ibus ==== Subpackages: ibus-branding-openSUSE-KDE ibus-gtk ibus-gtk-32bit ibus-gtk3 ibus-lang libibus-1_0-5 libibus-1_0-5-32bit python-ibus typelib-1_0-IBus-1_0 - Update ibus.spec: copy auto-start files to SOURCE directory to enable modifications before compile. - Add ibus-disable-engines-preload-in-GNOME.patch: Disable load preload-engines actions in SLE, which is unnecessary for mono IMF in SLE and may cause CJK user login failed (bsc#1036729). ==== kactivitymanagerd ==== - Recommend -lang package ==== kde-user-manager ==== - Recommend -lang package ==== kernel-source ==== Version update (4.4.73 -> 4.4.74) Subpackages: kernel-default kernel-default-devel kernel-devel kernel-docs kernel-macros kernel-syms - Delete patches.kabi/kabi-fix-for-kvm-x86-fix-singlestepping-over-syscall. No need for kABI fix yet for Leap 42.3. - commit f0a86d9 - Fix kABI breakage by KVM CVE fix (bsc#1045922). - commit c0308f6 - powerpc/perf: Fix branch event code for power9 (fate#321438, Pending SUSE Kernel Fixes). - commit e954af6 - powerpc: Fix /proc/cpuinfo revision for POWER9 DD2 (bsc#1046789). - commit 444247f - Refresh metadata patches.drivers/ibmvnic-a2-Fix-assignment-of-RX-TX-IRQ-s.patch. - commit be32be9 - drm/i915: Serialize GTT/Aperture accesses on BXT (bsc#1046821). - commit b263fef - Bluetooth: hidp: fix possible might sleep error in hidp_session_thread (bsc#1031784). - Refresh patches.suse/kgr-0008-mark-task_safe-in-some-kthreads.patch. - commit 18c6f3e - KVM: x86: fix singlestepping over syscall (CVE-2017-7518 bsc#1045922). - commit d989643 - nvme/pci: Fix stuck nvme reset (bsc#1043805). - commit 7afe4f0 - Refresh fadump patches to upstream and add metadata patches.arch/powerpc-fadump-add-reschedule-point-while-releasing-memory.patch. patches.arch/powerpc-fadump-avoid-duplicates-in-crash-memory-ranges.patch patches.arch/powerpc-fadump-avoid-holes-in-boot-memory-area-when-fadump-is-registered.patch patches.arch/powerpc-fadump-provide-a-helpful-error-message.patch - commit f0fb5c3 - blacklist.conf: Remove duplicated entries - commit cb960d2 - Remove duplicated blacklist entries and put git-commit tag to patches - commit 12a0cb2 - blacklist.conf: Remove duplicated entry. - commit 561ddb1 - ibmvnic: Fix assignment of RX/TX IRQ's (bsc#1046589). - commit 5fa38bf - blacklist.conf: blacklist 570d8e939801 we do not care about the code in Documentation all that much, do we? - commit 69d5811 - blacklist.conf: blaclist 5380e5644afb it is just not worth backporting without any explicit report where a silently truncated success would lead to a real bug. - commit fc28626 - blacklist.conf: unnecessary patch The bug triggers only upon a malformed descriptor and the comparison is so that our buffer would be too large not too small so no overflow. The device would not work, but it won't anyway. - commit 99f8a16 - Rearrange the previous patches for hpsa and smartpqi to the right position. - commit a1f1f27 - Update patches.fixes/xfs-split-default-quota-limits-by-quota-type.patch (bsc#1040941). Fix the bug nr used. - commit 115ba75 - printk: Correctly handle preemption in console_unlock() (bsc#1046434). - commit 0a3c2a4 - printk/xen: Force printk sync mode when migrating Xen guest (bsc#1043347). - commit e13596b - btrfs: disable possible cause of premature ENOSPC (bsc#1040182) - commit 8bf31da - rbd: make sure pages are freed by libceph (bsc#1045596). - rbd: drop extra rbd_img_request_get (bsc#1045596). - commit c8719f2 - dm-raid: Do not call BUG() in __rdev_sectors() (bsc#1046264). - commit 0b1aab0 - btrfs: Round down values which are written for total_bytes_size (bsc#1043912). - btrfs: Manually implement device_total_bytes getter/setter (bsc#1043912). - commit c4d2eb7 - pipe: cap initial pipe capacity according to pipe-max-size limit (bsc#1045330). - commit 4ee3ec2 - Blacklist drivers/net/ethernet/ibm/emac We do not build the driver. - commit d432b2b - blacklist.conf: this patch breaks the API It disallows some operations that are now allowed - commit 98325c2 - arm64: Update config files. (bsc#1036737) Disable XGENE_PMU. - commit 7bb0115 - Disable Xilinx network drivers (bsc#1046170). - commit 656fc83 - hwpoison, memcg: forcibly uncharge LRU pages (bnc#1046105). - commit 2b252e1 - blacklist.conf: blacklist 570d8e939801 the issue is visible only when 80df554275c2 is applied (4.7+ and not backported to our trees) - commit 47b83ce - config/x86_64: make CONFIG_SERIAL_8250_DW and *_MID built-in (bsc#1024449) - commit 2e3ca7e - Refresh patches.drivers/0477-nvme-add-hostid-token-to-fabric-options.patch. Update mainline references. - commit eee1109 - fs/exec.c: account for argv/envp pointers (bnc#1039354, CVE-2017-1000365). - commit 7418d0f - Refresh ibmvnic patch metadata patches.drivers/ibmvnic-98-ibmvnic-Correct-return-code-checking-for-ibmvnic_init-during-probe.patch. patches.drivers/ibmvnic-a0-ibmvnic-Fix-incorrectly-defined-ibmvnic_request_map_rsp-structure.patch. patches.drivers/ibmvnic-a1-ibmvnic-Fix-error-handling-when-registering-long-term-mapped-buffers.patch. - commit babc17a - Refresh metadata patches.fixes/powerpc-tm-Fix-stack-pointer-corruption-in-__tm_recheckpoint. - commit 0b5bdc6 - powerpc/ftrace: Pass the correct stack pointer for DYNAMIC_FTRACE_WITH_REGS (FATE#322421). - commit 936e653 - nvme: add hostid token to fabric options (bsc#1045293). - commit 52dffb9 - iw_cxgb4: Fix error return code in c4iw_rdev_open() (bsc#1026570). - RDMA/iw_cxgb4: Always wake up waiter in c4iw_peer_abort_intr() (bsc#1026570). - commit 2ce43b1 - clocksource/drivers/arm_arch_timer: Fix read and iounmap of incorrect variable (bsc#1045937). - commit 594f037 - Linux 4.4.74 (CVE-2017-1000364 bnc#1012382 bnc#1039348 bnc#1045340 bsc#1031717 bsc#1043231). - Delete patches.drivers/media-pvrusb2-reduce-stack-usage-pvr2_eeprom_analyze. - Delete patches.drivers/media-vb2-Fix-an-off-by-one-error-in-vb2_plane_vaddr. - Delete patches.drivers/staging-rtl8188eu-prevent-an-underflow-in-rtw_check_. - Delete patches.fixes/mm-fix-new-crash-in-unmapped_area_topdown.patch. - Delete patches.fixes/mm-larger-stack-guard-gap-between-vmas.patch. - commit 5e41880 - tty: Fix ldisc crash on reopened tty (bnc#1043488). - commit 04cca20 - tty: Destroy ldisc instance on hangup (bnc#1043488). - tty: Refactor tty_ldisc_reinit() for reuse (bnc#1043488). - tty: Use 'disc' for line discipline index name (bnc#1043488). - tty: Move tty_ldisc_kill() (bnc#1043488). - tty: Handle NULL tty->ldisc (bnc#1043488). - tty: Prepare for destroying line discipline on hangup (bnc#1043488). - tty: Reset c_line from driver's init_termios (bnc#1043488). - tty: Simplify tty_set_ldisc() exit handling (bnc#1043488). - commit c016cca - kabi: ignore fs_info parameter for tracepoints that didn't have it (bsc#1044912). - commit 24869ea ==== libxml2 ==== Subpackages: libxml2-2 libxml2-2-32bit libxml2-devel libxml2-tools - Security fix: * libxml2-CVE-2017-7376.patch [bsc#1044887, CVE-2017-7376] * Increase buffer space for port in HTTP redirect support - Security fix: * libxml2-CVE-2017-7375.patch [bsc#1044894, CVE-2017-7375] * Prevent unwanted external entity reference - Upstream patches updated and with tests: * libxml2-CVE-2017-9047.patch and libxml2-CVE-2017-9048.patch merged into libxml2-CVE-2017-9047.patch [bsc#1039066, bsc#1039661] * libxml2-CVE-2017-9049.patch and libxml2-CVE-2017-9050.patch merged into libxml2-CVE-2017-9049.patch [bsc#1039063, bsc#1039064] ==== libzypp ==== Version update (16.12.0 -> 16.13.0) - Adapt loop mounting of iso images (bsc#1038132, bsc#1033236) - Adjust zypp.conf for openSUSE Tumbleweed (bsc#1031756) - Change arch variable names conflicting with compiler macros (fixes #70) - Fix potential crash if repo has no baseurl (bnc#1043218) - version 16.13.0 (0) ==== lightdm ==== Subpackages: liblightdm-gobject-1-0 lightdm-lang - Augment patch to also resolve the target of symlink sessions for detemining the preselected option: * ignore-known-symlink-sessions.patch ==== marble ==== Subpackages: libastro1 libmarblewidget-qt5-27 marble-data marble-devel marble-doc marble-kde marble-lang - Add Fix-utm-enum-value.patch and reverse-apply it, this upstream commit causes a crash when adding bookmarks if switched to UTM view angles because the necessary handler functions for the dialog are not implemented yet (boo#1044747, kde#381872) - Add Fix-plain-map-and-political-map-showing-no-content.patch to fix the plain map and the political map being not displayed at all (kde#379297) ==== mc ==== Subpackages: mc-lang - sftp.patch: Backport upstream fixes for SFTP (boo#1004280, boo#1042797) ==== plasma5-integration ==== - Move the Recommends: %{name}-plugin-lang to the plasma5-integration-plugin sub package, otherwise the translations won't get installed as there is no main package (boo#1027925) - Actually apply the aforementioned patch (shouldn't the source validator have warned?) ==== plasma5-openSUSE ==== Subpackages: plasma5-defaults-openSUSE plasma5-theme-openSUSE plasma5-workspace-branding-openSUSE sddm-theme-openSUSE - Fix installation of the sddm theme files (boo#1047254) ==== postgresql ==== Version update (9.4 -> 9.6) Subpackages: postgresql-contrib postgresql-devel postgresql-docs postgresql-server - Bump version and defaultpackage to 9.6. - Move ~postgres/.bash_profile to postgresql-server to avoid a file conflict between the versioned server packages. - Bump version and defaultpackage to 9.4. - Bump version and defaultpackage to 9.3. - Change license string to PostgreSQL. - Make all dummy packages noarch. - Make PostgreSQL 9.2 the default. - Reduce the postgresql packages with unversioned names to dummy packages that require the respective versioned package names. ==== python-coverage ==== Version update (3.7.1 -> 4.3.4) - uninstall alternatives in %postun - update for singlespec - update to 4.3.4: - Using the --skip-covered option on an HTML report with 100% coverage would cause a ?No data to report? error, as reported in issue 549. This is now fixed; thanks, Lo�c Dachary. - If-statements can be optimized away during compilation, for example, if 0: or if __debug__:. Coverage.py had problems properly understanding these statements which existed in the source, but not in the compiled bytecode. This problem, reported in issue 522, is now fixed. - If you specified --source as a directory, then coverage.py would look for importable Python files in that directory, and could identify ones that had never been executed at all. But if you specified it as a package name, that detection wasn?t performed. Now it is, closing issue 426. Thanks to Lo�c Dachary for the fix. - If you started and stopped coverage measurement thousands of times in your process, you could crash Python with a ?Fatal Python error: deallocating None? error. This is now fixed. Thanks to Alex Groce for the bug report. - On PyPy, measuring coverage in subprocesses could produce a warning: ?Trace function changed, measurement is likely wrong: None?. This was spurious, and has been suppressed. - Previously, coverage.py couldn?t start on Jython, due to that implementation missing the multiprocessing module (issue 551). This problem has now been fixed. Also, issue 322 about not being able to invoke coverage conveniently, seems much better: jython -m coverage run myprog.py works properly. - Let?s say you ran the HTML report over and over again in the same output directory, with --skip-covered. And imagine due to your heroic test-writing efforts, a file just acheived the goal of 100% coverage. With coverage.py 4.3, the old HTML file with the less-than-100% coverage would be left behind. This file is now properly deleted. - update to Version 4.3.1 ? 2016-12-28: - Some environments couldn?t install 4.3, as described in issue 540. This is now fixed. - The check for conflicting --source and --include was too simple in a few different ways, breaking a few perfectly reasonable use cases, described in issue 541. The check has been reverted while we re-think the fix for issue 265. - update to Version 4.3 ? 2016-12-27: Special thanks to Lo�c Dachary, who took an extraordinary interest in coverage.py and contributed a number of improvements in this release. - The HTML report now supports a --skip-covered option like the other reporting commands. Thanks, Lo�c Dachary for the implementation, closing issue 433. - Subprocesses that are measured with automatic subprocess measurement used to read in any pre-existing data file. This meant data would be incorrectly carried forward from run to run. Now those files are not read, so each subprocess only writes its own data. Fixes issue 510. - Coverage.py wouldn?t execute sys.excepthook when an exception happened in your program. Now it does, thanks to Andrew Hoos. Closes issue 535. - The coverage combine command will now fail if there are no data files to combine. The combine changes in 4.2 meant that multiple combines could lose data, leaving you with an empty .coverage data file. Fixes issues issue 525, issue 412, issue 516, and probably issue 511. - The branch coverage issues described in issue 493, issue 496, and issue 502 are now fixed, thanks to Lo�c Dachary. - Options can now be read from a tox.ini file, if any. Like setup.cfg, sections are prefixed with ?coverage:?, so [run] options will be read from the [coverage:run] section of tox.ini. Implements part of issue 519. Thanks, Stephen Finucane. - Specifying both --source and --include no longer silently ignores the include setting, instead it fails with a message. Thanks, Nathan Land and Lo�c Dachary. Closes issue 265. - Coverage.py can now search .pex files for source, just as it can .zip and .egg. Thanks, Peter Ebden. - update to 4.2: - Since ``concurrency=multiprocessing`` uses subprocesses, options specified on the coverage.py command line will not be communicated down to them. Only options in the configuration file will apply to the subprocesses. Previously, the options didn't apply to the subprocesses, but there was no indication. Now it is an error to use ``--concurrency=multiprocessing`` and other run-affecting options on the command line. This prevents failures like those reported in `issue 495`_. - Filtering the HTML report is now faster, thanks to Ville Skytt�. - update to 4.0.3: - Fixed a mysterious problem that manifested in different ways: sometimes hanging the process (`issue 420`_), sometimes making database connections fail (`issue 445`_). - The XML report now has correct ``<source>`` elements when using a ``--source=`` option somewhere besides the current directory. This fixes `issue 439`_. Thanks, Arcady Ivanov. - Fixed an unusual edge case of detecting source encodings, described in `issue 443`_. - Help messages that mention the command to use now properly use the actual command name, which might be different than "coverage". Thanks to Ben Finney, this closes `issue 438`_. - add LICENSE.txt - Pre require coreutils. This package is needed for the rm call in the pre section. Subprocess failed. Error: RPM failed: /var/tmp/rpm-tmp.gONanE: line 3: rm: command not found - specfile: * updated license * updated update-alternatives * README.txt -> README.rst - update to version 4.0: (long list, see http://coverage.readthedocs.org/en/latest/changes.html) - fix rhel deps by depending on /usr/sbin/update-alternatives ==== ucode-intel ==== Version update (20160714 -> 20170511) - Update to version 20170511 - Update to version 20161104. ==== yast2-bootloader ==== Version update (3.2.22 -> 3.2.23) - AuotYaST configuration: Set StorageDevices flag disks_valid to true. So libstorage can scan valid disks and "/" partition can be found. (bnc#1043132) - 3.2.23 ==== yast2-ntp-client ==== Version update (3.2.9 -> 3.2.12) - Resrict records are written at the end but the default file and most profiles use them at the beginning, which mangles the file completely (bsc#983486). To fix it we have just changed the order of writing. - 3.2.12 - AutoYaST: Fix crash when trying to sanitize not string values, for example initial_sync. - AutoYaST: Sanitize comments by only removing blank spaces at the beginning and adding line break. This avoids augeas parse errors (bsc#1045777). - 3.2.11 - AutoYaST: Fix crash in CFA when creating a command record with some key value option is given (bsc#1045968) - 3.2.10 - AutoYaST: Comments from autoyast profile should not be sanitized to avoid entries without space between value and comment (e.g trustedkey 1# coment). This is caused by a bug in augeas adding new entries. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] acpid requires systemd?
by Felix Miata 25 Apr '24

25 Apr '24

Can this be true? If so, why? Zypper won't let me upgrade acpid without breakage unless systemd is installed too. I have systemd locked out, as I'd rather test things I can understand in Factory, not major overhaul stuff. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 3

enabling reproducible builds in Factory and ALP
by Jan Zerebecki 15 Mar '24

15 Mar '24

Hi *, to support https://en.opensuse.org/openSUSE:Reproducible_Builds I plan to get the following project configuration for Factory and ALP enabled: Macros: %source_date_epoch_from_changelog Y %clamp_mtime_to_source_date_epoch Y %use_source_date_epoch_as_buildtime Y %_buildhost reproducible :Macros I'm still waiting to get https://github.com/openSUSE/product-builder/pull/26 merged to prevent a bug with mirrors that will otherwise happen. Afterwards a time of the build is still in the HTTP header Last-Modified when requesting the rpm file. HTTP mtime is a few seconds earlier than end time of the build (seen in OBS web UI only as start + duration). I didn't double check, but it should also be recorded in the Tumbleweed archive Bernhard keeps, which can with a bit of work be looked up by content hash or name including version of the rpm file if its not on the normal mirrors anymore. Both the build time and host can also still be seen in the build log. Comments welcome. -- Best regards, Jan Zerebecki

4 6

Proposal: amend the packaging guidelines for %fillup_only
by Dan Čermák 02 Mar '24

02 Mar '24

Hi list, our packaging guidelines for %fillup_only [1] currently do not suggest anything for the %files section for the files generated in `/etc/sysconfig/`. I would like to suggest that we start adding the newly generated file `/etc/sysconfig/$pkgname` as follows to the %files section: --8<---------------cut here---------------start------------->8--- %files %ghost %config(noreplace) %attr(0600,root,root) /etc/sysconfig/%{name} %dir /etc/sysconfig --8<---------------cut here---------------end--------------->8--- This ensures that rpm is aware of the files as configuration files. Thoughts, opinions? Cheers, Dan Footnotes: [1] https://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros#%fillup_o… -- Dan Čermák <dcermak(a)suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstr. 146 90461 Nürnberg Germany www.suse.com Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)

3 3

wine and zlib
by Joe Salmeri 22 Feb '24

22 Feb '24

I did a fresh install of TW 20230222 on a new PC. My main desktop which was installed back in 2021 has also been updated ( zypper dup ) to 20230222. I found something odd when comparing packages between the 2 machines. Both PC's have wine installed, however... On my main desktop when the original install in 2021 of wine was done it installed libz1-32bit ( as per the zypper history logs ) and it still has that installed after it was updated to 20230222. On the new PC fresh install of 20230222 when wine was installed it installed libz-ng-compat1-32bit. The libz-ng-compat1-32bit version looks like it was forked in 2021, just after my main machine was originally built so that would explain why it has libz1-32bit but shouldn't it have been updated by zypper dup ??? Is this a bug that I should report? If so, which system is wrong / which version should be used? Thanks!

5 6

Recent e2fsprogs update flag changes
by Patrick Schaaf 22 Feb '24

22 Feb '24

Hi, as I haven't found discussion by searching, I thought I bring up a gotcha I ran into today, on a host recently updated to tumbleweed 20230801 level. With a somewhat recent update to e2fsprogs, now at 1.47.0 compared to May '23 at 1.46.5, the set of mkfs flags has changed: --- /root/mke2fs.conf.20230512 2023-08-09 12:00:14.379476597 +0200 +++ /etc/mke2fs.conf 2023-06-14 19:20:22.000000000 +0200 @@ -14 +14 @@ - features = has_journal,extent,huge_file,flex_bg,metadata_csum,64bit,dir_nlink,extra_isize + features = has_journal,extent,huge_file,flex_bg,metadata_csum,metadata_csum_seed,64bit,dir_nlink,extra_isize,orphan_file For me, this resulted in an otherwise fine virtual machine with 20230512 userlevel, not booting after an "rsync copy migration" into a fresh root filesystem mkfs'ed with these new flags. Reason being that 3 months older fsck - the sytemd boot time rootfs service actually - goes "failed". I guess I'll need just use flag override options going forward, to cope with that, but thought I'd bring it to attention here at least. best regards Patrick

3 4

snapd applications not working on Tumbleweed (20230613)
by Jim Henderson 19 Jan '24

19 Jan '24

Wondering if anyone else is seeing this. I attempted to launch two apps (slack and spotify) installed with snapd, and the launch failed. Troubleshooting it, I removed all of the snaps from the system, uninstalled and reinstalled snapd, and I get the following output: --- $ snap install spotify error: cannot perform the following tasks: - Run configure hook of "spotify" snap if present (run hook "configure": ----- go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Matcha-dark-sea /snap/spotify/67/data-dir/themes/Matcha-dark-sea none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Matcha-sea /snap/spotify/67/data-dir/themes/Matcha-sea none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Materia-compact /snap/spotify/67/data-dir/themes/Materia-compact none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Materia-dark-compact /snap/spotify/67/data-dir/themes/Materia-dark-compact none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Materia-dark /snap/spotify/67/data-dir/themes/Materia-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Materia-light-compact /snap/spotify/67/data-dir/themes/Materia-light-compact none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Materia-light /snap/spotify/67/data-dir/themes/Materia-light none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Materia /snap/spotify/67/data-dir/themes/Materia none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Radiance /snap/spotify/67/data-dir/themes/Radiance none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Radiant-MATE /snap/spotify/67/data-dir/themes/Radiant-MATE none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-MATE-dark /snap/spotify/67/data-dir/themes/Yaru-MATE-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-MATE-light /snap/spotify/67/data-dir/themes/Yaru-MATE-light none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-bark-dark /snap/spotify/67/data-dir/themes/Yaru-bark-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-bark /snap/spotify/67/data-dir/themes/Yaru-bark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-blue-dark /snap/spotify/67/data-dir/themes/Yaru-blue-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-blue /snap/spotify/67/data-dir/themes/Yaru-blue none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-dark /snap/spotify/67/data-dir/themes/Yaru-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-light /snap/spotify/67/data-dir/themes/Yaru-light none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-magenta-dark /snap/spotify/67/data-dir/themes/Yaru-magenta-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-magenta /snap/spotify/67/data-dir/themes/Yaru-magenta none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-mate-dark /snap/spotify/67/data-dir/themes/Yaru-mate-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-mate /snap/spotify/67/data-dir/themes/Yaru-mate none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-olive-dark /snap/spotify/67/data-dir/themes/Yaru-olive-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-olive /snap/spotify/67/data-dir/themes/Yaru-olive none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-prussiangreen-dark /snap/spotify/67/data-dir/themes/Yaru-prussiangreen-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-prussiangreen /snap/spotify/67/data-dir/themes/Yaru-prussiangreen none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-purple-dark /snap/spotify/67/data-dir/themes/Yaru-purple-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-purple /snap/spotify/67/data-dir/themes/Yaru-purple none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-red-dark /snap/spotify/67/data-dir/themes/Yaru-red-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-red /snap/spotify/67/data-dir/themes/Yaru-red none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-sage-dark /snap/spotify/67/data-dir/themes/Yaru-sage-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-sage /snap/spotify/67/data-dir/themes/Yaru-sage none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-viridian-dark /snap/spotify/67/data-dir/themes/Yaru-viridian-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-viridian /snap/spotify/67/data-dir/themes/Yaru-viridian none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru /snap/spotify/67/data-dir/themes/Yaru none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/elementary /snap/spotify/67/data-dir/themes/elementary none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied cannot update snap namespace: cannot create writable mimic over "/usr/lib/x86_64-linux-gnu": permission denied snap-update-ns failed with code 1 -----) --- The execution of both programs prior to the reinstallation did the same thing. I did note that /usr/lib/x86_64-linux-gnu does not exist on my system. Happy to report a bug on bugzilla, but wanted to see if anyone else had noticed this. -- Jim Henderson Please keep on-topic replies on the list so everyone benefits

5 10

[TESTERS WANTED] Using git to maintain packages on OBS - test run
by Dan Čermák 08 Dec '23

08 Dec '23

Dear packagers for openSUSE Tumbleweed, we have been working on a prototype that allows you to maintain your packages in git (similarly to Fedora's dist git) on src.opensuse.org instead of on OBS. Contributions to the package are then handled via pull requests on src.opensuse.org which get automatically forwarded as submitrequests on OBS. This is currently just a prototype and we are looking for testers and general feedback. So if you want to participate as a maintainer, please check the full guide here: https://opensuse.github.io/scm-staging/user_guide.html tl;dr; you'll have to convert the develpackage to use `<scmsync>` from src.opensuse.org/pool and everything else should "just work". FAQ: - Where can I report issues or provide feedback? https://github.com/openSUSE/scm-staging/issues (for bugs) or https://github.com/openSUSE/scm-staging/discussions (for general feedback) - Is this how the future of packaging in openSUSE is going to look like? Maybe, maybe not. This is currently just a test drive and its outcome will influence the way forward. - Will submitrequests to my develpackage still work? Sadly no, branching a git maintained package on OBS does not work. Please indicate in the description of your package that users should contribute on src.opensuse.org instead. - Which tools do I need? Just git, git-lfs and osc (at least version 1.2.0 is recommended for service runs to work) Looking forward to your feedback! Dan -- Dan Čermák <dcermak(a)suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstrasse 146 90461 Nürnberg Germany (HRB 36809, AG Nürnberg) Managing Director/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman

23 66

Disk auto-unlocking with TPM 2.0
by Gary Lin 10 Oct '23

10 Oct '23

Hi, I'm pleased to introduce a new feature for openSUSE Tumbleweed: disk auto-unlocking with TPM 2.0. In short, it boots the encrypted root without asking for a passphrase. This feature is already integrated into Agama on ALP and we plan to merge it into yast-installation (*1). For now, if you're interested, just type a few commands to enable it. The hard requirements are LUKS2 partition(s), UEFI with Secure Boot enabled, and, of course, TPM 2.0. LUKS2 support in yast-installation is still experimental and needs a few extra steps. You could also choose to convert the existing LUKS1 partition to a LUKS2 one. The LUKS2 setup is addressed in the following link: https://en.opensuse.org/SDB:Encrypted_root_file_system#Setup_LUKS2_partitio… First of all, please update all packages, especially shim and grub2. The key package is fde-tools. Currently, there is a minor issue that the TCTI for native devices may not be installed, and the fix is on the way(*2). So, please install fde-tools along with libtss2-tcti-device0 for the time being. # zypper in fde-tools libtss2-tcti-device0 After installing fde-tools, you can test the TPM 2.0 support with # fdectl tpm-present If there is no error, it's time to seal a new random key for your root partition: # fdectl regenerate-key This command will request the passphrase of the root partition to enroll a new random key, seal the random key with TPM, and then update the grub configuration. Next, reboot your system. If everything is setup correctly, the system will boot without showing the passphrase prompt. One thing to be noted is that after a boot component upgrade, such as shim, grub2, or UEFI firmware, the signature in the sealed key may become invalid, and then you have to run the following command to update the signature. # fdectl tpm-authorize We are still working on a solution to update the signature automatically after shim and grub2 update to reduce such hassles. By default, 'fdectl' only manages the keyslots of the root partition. To extend the keyslot management to other partitions such as swap, please check https://en.opensuse.org/SDB:Encrypted_root_file_system#Additional_steps_for… A complete document is available here: https://en.opensuse.org/SDB:Encrypted_root_file_system#Unattended_boot_with… In case you encounter any issue, feel free to file a bug and assign it to bootloader-maintainers(a)suse.de Cheers, Gary Lin (*1) https://github.com/yast/yast-installation/issues/1088 (*2) https://build.opensuse.org/request/show/1100949

17 32

Leap not more useful for WebServer with php
by Walddys Emmanuel Dorrejo Céspedes 09 Oct '23

09 Oct '23

Leap is stuck with PHP 8.0 version, when most devs and project have move to php8.1/8.2, i was hoping that php8.1 at least this version reach leap 15.5, but didn't reached the main repo. sad.

6 6

Changes to dbus packaging (Some Attention maybe required).
by Simon Lees 04 Oct '23

04 Oct '23

Hi All, For Tumbleweed and ALP we plan to follow Red Hat / Fedora / Debian and move from dbus-daemon to dbus-broker as it has a number of advantages and is what upstream is now focusing on. While one of the goals here is to provide the same user experience there will be a couple of changes that will likely require adjustments in a few packages. 1. tools such as dbus-send and dbus-uuid will no longer be installed by default on all systems (we have many use cases that will simply no longer need them and this follows other distro's). Currently the package dbus-1-tools exists and is required by dbus-1 but that will change maybe to a recommends so if you know your package needs one of these tools you can add the Requires there now, otherwise I plan to go through and look at debian and fedora to try and find any packages that need this requires before it becomes optional for dbus. 2. The symlink from /etc/machine-id to /var/lib/dbus/machine-id will no longer be present on all machines and software should be adapted to use /etc/machine-id from systemd rather then the dbus copy. Again this has already happened for Debian and Fedora so hopefully many upstreams have already adapted to this. I'll outline the plan / timeline below. 1. Currently - dbus-broker has been in the distro for quite some time and the dbus-1 package has already been split up and we are at the point of asking people nicely to start testing (instructions below), myself and at least several other people have already been testing this without issues. 2. In 2-3 weeks if I don't hear of any issues we will update the systemd presets to enable dbus-broker rather then dbus-daemon. 3. Unless someone indicates they really want to keep maintaining dbus-daemon and have good reasons for doing so I will make dbus-daemon uninstallable. 4. Once we have done the work to ensure that as many packages that use dbus-send and other tools require the tools package we will drop the requires for dbus-tools from the dbus package. Instead it will probably move to being a Recommends in one of the patterns so it still ends up on most users machines. Switching to dbus-broker: Run the following as root zypper in dbus-broker systemctl disable dbus systemctl enable dbus-broker systemctl --global disable dbus systemctl --global enable dbus-broker https://www.mail-archive.com/debian-policy@lists.debian.org/msg35437.html https://fedoraproject.org/wiki/Changes/DbusBrokerAsTheDefaultDbusImplementa… -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

4 6

Off topic: Can't log in to Bugzilla
by Mark Rubin 23 Sep '23

23 Sep '23

I believe I have a login at https://bugzilla.opensuse.org/ with the same username and password that I use here and at https://forums.opensuse.org/. It works at both those sites, and used to work at Bugzilla although the last time I used it there was several years ago. Bugzilla seems to know me, but when I try to log in using "openSUSE_IDP Log In" (the only choice) it rejects me, before asking for username/password/etc, with "There is already an account with the login name <my email address>". I did a password reset, and got a token in my email which it accepted back along with a new password, which then brought me to a page ending with my info and "Your profile is up to date". But I can't continue to the site from there, and trying to log in again restarts the same "already an account" loop. If anyone has any suggestions, or a way to contact the Bugzilla administrators to plead my case, I'd appreciate it. I have some new information to post there regarding my thread here, plus another new/verifiable bug to report. It's very frustrating to be trying to contribute (in some small way) to openSUSE only to get blocked by things like this.

7 16

RFC: turn off ppc32 and ppc64 big endian builds on openSUSE:Factory:PowerPC
by Dirk Müller 14 Sep '23

14 Sep '23

Hi all, recently I was made aware that openSUSE:Factory:PowerPC is quite a large distribution as it is building for ppc 32bit, ppc64 big endian and ppc64 little endian. in OpenQA as far as I know we are only testing the ppc64 little endian builds. Given the upcoming data center move and the lack of testing, are there any concerns about turning off the builds for ppc 32bit and ppc64 big endian? It would reduce build power needs as well as disk storage /publishing bandwidth which is shared with other distributions and architectures and becomes a problem because of PowerPC being exceptionally large. Thanks a lot in advance for any insight you can provide, Greetings, Dirk

10 26

Thunderbird 115
by Joe Salmeri 07 Sep '23

07 Sep '23

Is there a reason that Thunderbird 115 is being held back ? Version 115.0.1 was released on 07/20/2023 which was almost a month ago Version 115.1.0 was released on 08/01/2023 Version 115.1.1 was released on 08/15/2023 If I look at openSUSE build the builds are disabled https://build.opensuse.org/package/show/mozilla/thunderbird115 Is there an ETA as to when it will be published ? Thanks -- Regards, Joe

13 27

[RFC] Switching to drop-in files (systemd)
by Franck Bui 04 Sep '23

04 Sep '23

Hi, The way the systemd daemons (such as PID1, logind) parse their configuration file is specified in systemd-system.conf(5) man page (section CONFIGURATION DIRECTORIES AND PRECEDENCE). Basically the daemons parse first their "main" configuration file (e.g /etc/systemd/system.conf for PID1) and then read and apply the optional drop-in files located in the following directories: /usr/lib/systemd/*.conf.d/ /usr/local/lib/systemd/*.conf.d/ /run/systemd/*.conf.d/ /etc/systemd/*.conf.d/ It's important to note that drop-in files have higher precedence than the main configuration file. Hence if a package customizes an option by shipping a drop-in file in /usr/lib/systemd/*.conf.d/, it might override the value already set by the user if the same option was customized by the sysadmin in the main configuration. There were various discussions [1] about addressing this concern but at the end upstream preferred keeping the existing logic. This implies that using the main configuration files is not 100% safe (even if it's been documented since a long time) especially since openSUSE distros relies on drop-in files to tune a few upstream defaults, see systemd-default-settings package to get the list. To avoid inconvenient divergences with upstream, we'll follow the existing logic but this implies that: - use of main config files, such as /etc/systemd/{system.conf,logind.conf}, should be avoided and instead customization should be done via drop-in files, such as /etc/systemd/system.conf.d/50-local.conf. - Some drop-in priority ranges should be defined to make sure that drop-in created by users have always higher precedence over the ones shipped by packages. The priority ranges reserved for users and downstream will be defined and documented in the relevant wiki page. - at installation, systemd packages will stop installing (empty/template) main configuration files and instead users will find the templates in drop-in directories (such as /etc/systemd/*.conf.d/50-{local,main,xxx}.conf, exact filename to be defined). - optionally, the packaging stuff will take care of converting existing main configuration files into drop-in files during package update. If there's no objection with the above, this change will be probably take place during the upgrade to systemd v254 or quickly after. Thanks. [1] https://github.com/systemd/systemd/pull/17161

13 37

new pkg pipewire-module-xrdp
by Jason Craig 04 Sep '23

04 Sep '23

I have created a new package to facilitate sound with xrdp when using pipewire. At least one user has tested it and I have submitted it to X11:RemoteDesktop[1]. This request has stalled without response for a bit, if anyone can help with that. I intend to submit this to Factory after it is accepted into the devel project. thanks /Jason Craig [1] https://build.opensuse.org/request/show/1105159

2 2

Maintenance of library packages in topical teams?
by Dominik George 01 Sep '23

01 Sep '23

Heisan, this topic came up during my submission of python-mmllib to the Python devel project [1]. But, in fact, it seems to be a quite general discussion, so I am raising it here to get a general picture. As a side note, my current endeavour is exploring the maintenance, especially team maintenance and mentoring approaches, of packages in openSUSE, in comparison to how it is handled in Debian. I am a Debian Developer and therefore quite used to the workflows and basic approaches over there. The general question I'd like to discuss is where libraries for development in various languages should be maintained. There are development teams for all major languages, and these seem, to some extent, to maintain development libraries as well. Then, looking at MMLlib as an example, this package can be seen in two ways: * it is a library that can be used for various kinds of programs written in Python, among which are games, educational toys, and multimedia applications * it is not _really_ generic, as it is somewhat specialized in not only, but probably mostly the fields mentioned above So, in *theory*, MMLlib is a generic library that can be used by whoever thinks they need it in their program, but in practice, it will be mostly useful for the mentioned fields. Matej therefore proposed it be moved to another team, with the Education devel project in mind (because education is the field where I, also being the upstream maintainer, developed it). I, i ncontrast, are still in favour of having all sorts of Python libraries maintained in a language team. Let me summarize what I think are the arguments for the two approaches: a) Maintaining all development libraries in a single language project - high maintenance load for a single team - large collection of packages in a single, probably not too well namespaced bunch + simplified auto-maintenance and batch changes + better control over adherence to library packaging guidelines b) Maintaining specialised libraries in topical projects - less control over adherence to library packaging guidelines - not clear which topic fits the best (see example above) sometimes + less maintenance burden for a single team Closely related to this question is the question whether development libraries should go into the distribution at all. More recently, I found the stance of the Go language team on that [2]. In conclusion, this is "we do not want a large collection of development packages in the distribution, only those needed to build and run leaf binaries". Taht implies that developers who use openSUSE for their work are told to use non-openSUSE sources instead, and install development libraries from the repositories provided by their language ecosystem, and that we make a clear distinction: * packages in openSUSE are for end users * developers use their language ecosystem tools Generally, I am in favour of providing all tools, including libraries, for everyone in a distribution, but that's a very "Debian" view of things. In practice, it shows that for Python development, virtual environments managed with poetry or whtever, and installing packages from PyPI, is far better suited. So I am somewhat moving into that direction. But then again, I find it questionnable that the Go language team should be responsible for maintaining any binary leaf packages. Why is teh Go devel project responsible for maintaining, say, hugo [3], and not a devel project tailored at website topics? All in all, I think my favourite pattern would be somethign like this: * maintain binary leaf packages in a topical team * maintain libraries in a language team, independent of topic * do not accept libraries that are not dependencies of leaf packages I am aware that there is no "one size fits all" solution, but hopefully, others can contribute valuable views on that topic ☺. Ha det bra, Nik [1] https://build.opensuse.org/request/show/1103110?notification_id=42200225 [2] https://en.opensuse.org/openSUSE:Packaging_Go#Not_all_packages_will_be_acce… [3] https://build.opensuse.org/package/show/openSUSE:Factory/hugo

4 4

Heads up regarding future log spamming by memfd_create()
by Larry Finger 31 Aug '23

31 Aug '23

In kernel 6.3, memfd_create() was modified to issue a pr_warn_once() when called with neither MFD_EXEC nor MFD_NOEXEC_SEAL was set in the flags associated with the request. The warning was intended to get to user-space maintainers to fix their code. That attempt failed as the first such event happened during boot, and no one ever saw the warning. In kernel 6.6, the log statement has been changed to pr_info_ratelimited(), thus the event is logged regularly. Most of these will need to be fixed upstream, but I am announcing the ones I see on my system in case we will need to fix them in TW. My system has logged 1250 of these events in less than 17 hours of up time. The different user-space programs triggering this event on my system are as follows: akonadi_followu akonadi_indexin chrome IPDL Background kmozillahelper ksplashqml kwin_x11 plasmashell pulseaudio qemu-system-x86 Renderer (sd-executor) systemd TaskCon~ller #0 TaskCon~ller #1 TaskCon~ller #2 TaskCon~ller #3 thunderbird-bin Xorg.bin If you are the openSUSE maintainer of any of these, please push a fix. Thanks, Larry

2 2

openSUSE Tumbleweed download URL changed?
by Andrei Borzenkov 31 Aug '23

31 Aug '23

The https://build.opensuse.org/repositories/openSUSE:Tumbleweed shows downloadcontent.opensuse.org (instead of download.opensuse.org) which gives 403 for all links.

3 2

Re: Thunderbird 115
by Eric Schwarzenbach 31 Aug '23

31 Aug '23

On 8/31/23 08:32, Richard Biener wrote: > On Thu, 31 Aug 2023, Rainer Klier wrote: > >> hi, >> >> Am 31.08.23 um 14:05 schrieb Wolfgang Rosenauer: >>> I've submitted Thunderbird 115.2.0 today for inclusion in Tumbleweed. >>> >>> ... and I'm waiting for the first thread to complain about the changes ;-) >> do we have to somehow "convert" or upgrade all the settings, when we first >> start the new version? >> >> or is this done automatically on the fly? > On the fly didn't work for me (on Leap, from an even older Thunderbird > profile), I've successfully copied away the old profile and used > import profile from the new TB to "convert". > > "successfully" in the sense that it works, GPG stuff required quite > some fiddling. And my - the new UI sucks, maybe I'll get used to it. I seem to recall Thunderbird assuring us, when they touted the upcoming changes, that there would be setting to change any of them back to way they were in the old UI. Is that not the case?

2 1

Fwd: Problem with openSUSE Bugzilla login?
by ddemaio 31 Aug '23

31 Aug '23

Hi all, If you are having difficulties with the login to openSUSE Bugzilla (bugzilla.opensuse.org), please let me know and provide the name, user name & email you used to login in the the system previously. I realized that some people have had issues with it for various reasons including migration to the IDP. I've raise a ticket for this and am trying to fully address the issue, but we need to know the extent of the amount of people who are having issues with this. As simple reply to this email is preferred. v/r Doug

1 0

Incompatible API update for podofo package in factory
by Frank Kunz 30 Aug '23

30 Aug '23

Hello, with the update to version 0.10.0 of the podofo package in factory (https://build.opensuse.org/package/show/openSUSE%3AFactory/podofo) the API of libpodofo has been changed to be not backwards compatible. The package release notes list that as intentional: "The release is complete re-imagination of PoDoFo 0.9.x API in C++17, and it's API/ABI incompatible with the previous releases." (https://github.com/podofo/podofo/releases). This causes dependent projects not to build anymore for factory/tumbleweed, e.g. https://build.opensuse.org/package/show/electronics/horizon, as well as the upstream github CI build fails. What would be the solution for that issue, adding a 0.9.8 release based compatibility package to factory? Br, Frank

3 2

New Tumbleweed snapshot 20230828 released!
by Dominique Leuenberger 30 Aug '23

30 Aug '23

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: ImageMagick (7.1.1.12 -> 7.1.1.15) clamav (0.103.8 -> 0.103.9) firewalld hwdata (0.372 -> 0.373) java-11-openjdk (11.0.20.0 -> 11.0.20.1) plymouth python-mailman python-psutil tango-icon-theme wtmpdb (0.9.0 -> 0.9.1) xfce4-terminal (1.0.4 -> 1.1.0) === Details === ==== ImageMagick ==== Version update (7.1.1.12 -> 7.1.1.15) Subpackages: ImageMagick-config-7-SUSE ImageMagick-extra libMagickCore-7_Q16HDRI10 libMagickWand-7_Q16HDRI10 - version update to 7.1.1.15 * upstream changelog: https://github.com/ImageMagick/Website/blob/main/ChangeLog.md#711-15---2023… - modified patches % ImageMagick-library-installable-in-parallel.patch (refreshed) - deleted patches - ImageMagick-CVE-2023-3428.patch (upstreamed) ==== clamav ==== Version update (0.103.8 -> 0.103.9) Subpackages: libclamav9 libfreshclam2 - Renew clamav.keyring . - Update to 0.103.9 * CVE-2023-20197: Fixed a possible denial of service vulnerability in the HFS+ file parser. This issue affects versions 1.1.0, 1.0.1 through 1.0.0, 0.105.2 through 0.105.0, 0.104.4 through 0.104.0, and 0.103.8 through 0.103.0. (boo#1214342) * Fixed compiler warnings that may turn into errors in Clang 16. ==== firewalld ==== Subpackages: firewalld-bash-completion firewalld-lang firewalld-zsh-completion python3-firewall - fix(cli): all --list-all-zones output identical (boo#1213609) [+ fix_list_all_zones_output.patch] ==== hwdata ==== Version update (0.372 -> 0.373) - update to 0.373: * Update pci, usb and vendor ids ==== java-11-openjdk ==== Version update (11.0.20.0 -> 11.0.20.1) Subpackages: java-11-openjdk-headless - Update to upstream tag jdk-11.0.20.1+1 (August 2023 emergency release fixing a regression in July 2023 CPU) * Changes: + JDK-8313765: Invalid CEN header (invalid zip64 extra data field size) + JDK-8314678: Bump update version for OpenJDK: jdk-11.0.20.1 ==== plymouth ==== Subpackages: libply-splash-core5 libply-splash-graphics5 libply5 plymouth-dracut plymouth-lang plymouth-plugin-label plymouth-plugin-two-step plymouth-scripts plymouth-theme-bgrt plymouth-theme-spinner - Remove plymouth-runstatedir-revert.patch: Tumbleweed following upstream, which already support "--runstatedir", don't need this modification anymore(jsc#PED-5841). - Add plymouth-runstatedir-revert.patch: For plymouth update successfully build in SLE-15-SP6:GA. The current edition of autoconf on SLE-15-SP6:GA don't support "--runstatedir" yet, so reverse plymouth compile option to the old "--withruntimedir" (jsc#PED-5841). ==== python-mailman ==== - Fix issues with importlib_resources for Python 3.11 * Added mailman-fix-importlib-resources.patch - Add missing require for psycopg2 ==== python-psutil ==== - Add logind_y2038.patch to use logind if systemd >= 254 is used, to fix the issue of ut_tv.tv_sec and the Y2038 problem. ==== tango-icon-theme ==== - BuildRequire bitstream-vera-fonts for SVG text rendering ==== wtmpdb ==== Version update (0.9.0 -> 0.9.1) Subpackages: libwtmpdb0 - Fix last.1 manual page reference - Update to version 0.9.1 - Fix printf format specifier on 32bit ==== xfce4-terminal ==== Version update (1.0.4 -> 1.1.0) Subpackages: xfce4-terminal-lang - Update to version 1.1.0 * Update copyright year * Allow passing arguments to custom commands * Fully translate strings in unsafe paste dialog * window: Properly sync always-show-tabs * cleanup: Include gdkx.h in one place * preferences: Remove unused class member * preferences: Check if channel itself exists instead of check property * screen: Review image loader memory management * image-loader: Review cache management * Add keywords to .desktop files (Fixes #50) * screen: Take window scaling into account when drawing (Fixes #71) * Remove obsolete GNOME default-app file (Fixes #109) * Add "Open File Manager Here" action (Fixes #133) * Properly manage default encoding (Fixes #128) * Move general include in private.h * dropdown: Disable systray icon on Wayland * Fix startup with GDK_BACKEND=x11 (Fixes #177) * shortcuts: Restore broken action toggle-menubar * shortcuts: Fix non-consumed key event for show-menubar * main: Allow GTK to parse its options first (Fixes #216) * search: Add missing sanity check * Use GLib logging functions and do not translate warnings * Remove obsolete CHECK_VERSION() * Use g_new() instead of malloc() * Fix Xfconf memory management * search-dialog: Fix memory leak * Remove extra separator at the end of context menu * Missing shortcut keys in the standalone preferences dialog (Issue #198) * Apply 1 suggestion(s) to 1 file(s) * Enable kinetic scrolling in VteTerminal * Extend --disable-server description wrt. process model * Drop obsolete --disable-server translations * prefs-dialog: Fix untranslated strings * Add sixel support * Add icons at missing sizes, clean up SVG metadata * build: Fix autoconf warnings * build: Add GLib requirement * Add accel entries for scrolling pages (Issue #221) * Remove documentation for dead anti-aliasing option * Make strings translatable (Issue #222) * Fix shortcuts-editor include * Support hyperlinks (Issue #21) * Fix argument type for xfce_shortcuts_editor_new * fix background_notify * Remove disable-help preference. * MR: !51 transitioned to Xfconf (#134) * typos in MR !48 fixed * Remove all references to terminal-preferences.glade * Remove one more mention of terminal-preferences.glade * Remove trailing slash * Remove terminal-preferences-ui.h from makefile * Remove terminal-preferences.glade * MR: !48 shortcuts editor embedded into preferences-dialog (#195) * MR: !48 preferences-dialog rewritten in C (#195) * MR: !46 Change in implementation for TAB accels (#150) * Implementation of MiscShiftArrowsToScroll as accelerators. * Add PCRE2 build dependency * Remove libxfce4ui 4.17 version guards * Replace with xfce_gtk_menu_append_separator * Tweak toolbar * Translation Updates - "gnome-control-center" support is no longer available; remove the corresponding entries from the %files list

1 0

openSUSE Release Engineering meeting 30.08.2023
by Lubos Kocman 30 Aug '23

30 Aug '23

All meeting minutes can be found here: https://etherpad.opensuse.org/p/ReleaseEngineering-meeting The meeting is hosted here https://meet.opensuse.org/ReleaseEngineeringMeeting ## Attendees bittin, bmwiedemann, Sarah, DimStar, lkocman, ddemaio,maxlin, Marcus, AdrianS ## Leap lkocman will be in the Prague office on Aug 31st The Leap replacement survey for contributors closes tomorrow on 31st Aug 11:59pm https://survey.opensuse.org/ All reported feature requests against 15.6 were processed. https://code.opensuse.org/leap/features Big thanks for Simon on pattern works We've got some negative feedback regarding Leap Micro on get-o-o I hope that current tweaks, pointers to docs etc fixed it https://github.com/openSUSE/get-o-o/pull/167 We'll plan to restructure the text and make it look more easy to read. 15.6 is now Alpha in get-o-o Leap Micro is ready too (images were tested manually), I just need to finish some last fiddling on download-o-o, as I had issues with repodata from initial builds. Discussion with Rob Sirchia regarding Leap Micro + BCI talk at https://olfconference.org/open-source-solutions-stage-2023/ Looking for additional speakers for https://www.linuxdays.cz/2023/ I have about 4 topics that I'd like to have there, but ideally in 2+ speakers. So far me and Dan Cermak seem to be the only speakers from SUSE. Linuxdays is bit special, since it's the most Green-painted event in CZ. Max's refresh of 15.6 packages triggered 120+ Legal reviews. I'm slowly processing them WIKI I'd like to move this from the talk section to official space (initially copied from Fedora with annotation. The page was discussed back then with Ciaran). Feedback from this round is welcome. https://en.opensuse.org/openSUSE_talk:Accepted_licences#Licenses_in_openSUS… Leap 15.6 refreshed schedule https://en.opensuse.org/openSUSE:Roadmap ## openSUSE Tumbleweed openSUSE:Factory build fail stats: 70 failed 7 unresolvable (last week: 103 failed, 6 unresolvable) https://tinyurl.com/ysy4nnnz Datacenter move on Thursday/Friday made us stop TW checkins, as we did not want to put more stress on the migrartion than needed. First check- in was done on Monday (0828) - that snapshot is supposed to go out to the mirrors soon™. Next snapshot is 0830 (just checked in) * systemd 254.1 is in the queue, but blocked by the maintainer due a late-identified performance regression https://github.com/systemd/systemd/issues/28765 * glibc performance regression fix in the queue (https://bugzilla.opensuse.org/show_bug.cgi?id=1214324) - check in for 0830 * Kernel 6.5 has just been submitted into the queue * libxml2 2.11.x blocked, as it breaks things raptor, the raptor fix in turn breaks redland. This was postponed for a few weeks, maybe a couple of months. * fmt 10 blocked, as it breaks mariadb boo#1213219, ceph boo#1213217 ## Richard (Aeon) Will work more on it later today Richard's been needing to focus on SUSE ALP topics more than Aeon Not much news this week, more fun with systemd-homed; trying to find a route to making it the default lkocman: If this would be a success we should definitely talk to SUSE IT, to consider home-encryption only as acceptable. As of now it's only FDE on Linux. New aeon-check concept being discussed https://en.opensuse.org/Portal:Aeon/DevelopmentThoughts ## Richard (ALP Architecture) No update this week, as there is poll ongoing until tommorow No progress, waiting for the results of the poll https://etherpad.opensuse.org/p/alp-poll ## Bernhard (Slowroll) Bernhard continued scripting https://en.opensuse.org/openSUSE:Slowroll Dominique: use branch instead of copypac then you'll not have issues with release counters ## Max * Leap Micro tooling part is now complete. * 15.6 first round of submissions from Factory to Leap (1000+ submissions). * We'll postpone checkin by few days to give maintainers some time to react. * New snapshot in openQA, after that I've noticed we're missing binaries in snapshot repo from SLE-15-SP5:Update, thanks to Adrian, this issue got fixed ## Guillaume - Arm Not available Tumbleweed: * Rolling * gcc13 bug leading to build failure of highway (and maybe more) - A fix is available in master branch of GCC and need to be backported to GCC13 - https://bugzilla.opensuse.org/show_bug.cgi?id=1213647 * shim currently not signed by Microsoft for aarch64 (Tumbleweed only, Leap is fine). It has been sent upstream for review, so it is progressing - https://bugzilla.suse.com/show_bug.cgi?id=1211297 Leap: * 15.5 aarch64: kernel oops seen on openQA aarch64 workers - https://bugzilla.opensuse.org/show_bug.cgi?id=1213620 * 15.5: port for armv7: containers are currently not building/created. Dirk mentioned that driver in 15.4 was the k3s team. ALP: * shim not signed by MS (at least for aarch64, not sure for x86_64) - jsc#ARM-100 WSL: * Works with x86 emulator since appx installer is x86-64, but this is not really an issue since arm64 Win11 includes x86 emulator by default. Team is ok to publish it on Microsoft store anyway, but this would require some testing in openQA which is currently not possible (due to technical issues and MS licensing issues) https://progress.opensuse.org/issues/126083. Steps documented on the wiki to install the appx from download.o.o: https://en.opensuse.org/openSUSE:WSL#With_Appx_from_openSUSE_download_server Note: I will miss all next meetings in August. See you in September. ## Sarah - s390x Tumbleweed * no new releases because of missing build nodes for building -> data center move required together with old mainframe. Wolfgang: the date of the final move is unfortunatelly not fixed yet. Physical installation issues such as network installation, and IBS/OBS setup in PRG. Definitely not before August. Leap: * running Dominique: s390x seems to be ahead of time in publishing. It's the only arch where 0828 was already published. ## Doug * Processing KDE Patron paperwork * Budget discussions progressing * New pamphlet complete * openSUSE.Asia Summit * Resent info for openSUSE.Asia Summit payment * Registrations 27, Submissions 31 * CfP closed * Have offer for storage in Furth (awaiting decision) * GSoC * 6 of 8 final evaluations due by Sept. 4 by 18:00 UTC * Two extentions due Oct. 2 by 18:00 UTC Static * Checking on FOSDEM stand & devroom - Annoucements likely to come in September * Storage * AI topics (static) * Nothing new ## Dirk Not available ## Wolfgang (Package Hub), Scott Bahling Not available finish Package Hub SLE-15-SP6 product setup this week on IBS to proceed with SCC and CDN availability we need to check orphaned packages that can be removed from Backports before publishing to CDN ## Maintenance team (Marcus or Maurizio (m4u)) Leap openQA issues with webkitgtk update and gtk4 update Firefox needs updates of dependencies before it can be updated to the current version (Security fixes) libzypp update in 15.5 was fixed by releasing missing dependency. libzypp issue that can be properly addressed only with respin of DVD. See section above for more details. openQA is OK currently. (snapper was fixed) Some 15.5 updates from between freeze and GA need to be released, WIP for Marcus Key rotation: Migration with changed 4k key. Current autoimport solution is not ideal. Marcus will work on update of the opensuse-build-key https://en.opensuse.org/SDB:System_upgrade#0._New_4096_bit_RSA_signing_key Marcus is working also on the SLES side, the update of package with the new key was released last week, it's just not activated yet, but it will be already trusted by Leap 15.5 systems. Leap 15.4 is working Leap Micro 5.3 is working Leap Micro 5.4 testing is now passing as well Leap 16.0 - we should revisit the update/sle repo as the current setup not exactly mirror friendly. Solutions could be dropping not so popular architectures or split repositories per architecture. lkocman: 15.3 EOL could lead to stopping our physical Source DVD effort, as it seems we will not produce. As this was the last release which you could still get on a physical media. Lkocman: anything against decomissioning it? Not a single valid request since I've joined SUSE. We did receive only requests for binary install media which are not subject to ^. We do not plan to offer this for any new releases. ## Adrian - OBS "Virtual" server room migration to PRG seemed to work well. Only some minor issues remains. ## Open Floor

1 0

[opensuse-factory] reproducible builds status 2023-08
by Bernhard M. Wiedemann 30 Aug '23

30 Aug '23

Hi, Did some more nice debugging and patches this month The ghc workaround is still pending to bring another 220+ reproducible packages. https://github.com/opensuse-haskell/ghc-rpm-macros/pull/1 Java still has some way to go, but is improving upstream as well. 313 is probably the lowest percentage of build-compare-failed (very-unreproducible) packages we ever had. 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/2023-07/ I uploaded https://rb.zq1.de/compare.factory-20230830/ today https://rb.zq1.de/spec/glossar.txt explains the meaning of below values: total-packages: 14840 (+28) build-tried: 14803 (+27) build-failed: 29 (-45) build-n-a: 229 (+29) build-succeeded: 14545 (+42) build-official-failed+na: 79 (-30) build-compare-failed: 313 (-98) build-compare-succeeded: 14232 (+140) verify-failed: 603 (-84) verified-semi-reproducible: 11432 (-23) bit-by-bit-identical: 14059 (+128) not-bit-by-bit-identical: 487 (-77) not-bit-by-bit-identicalcheck: 486 (-86) https://rb.zq1.de/compare.factory-20230830/graph.png shows the change over time https://rb.zq1.de/compare.factory-20230830/unreproduciblerings.txt lists very unreproducible core packages (bootstrap+DVD) Of the badly unreproducible packages, 4 were in ring0 37 were in ring1 That makes it 41/3206 => 1.28 % which is below the overall average of 313/14545 => 2.15 % 487/14545 => 3.35 % of packages are not perfectly reproducible package notes: ==> ./alex/.rb.notes <== ghc toolchain parallelism ==> ./apache-arrow/.rb.notes <== = https://github.com/apache/arrow/issues/37276 FTBFS-j1 ==> ./apptainer/.rb.notes <== = https://github.com/apptainer/apptainer/issues/1623 random go buildid from mlocal/frags/go_normal_opts.mk:GO_LDFLAGS += -ldflags="-B 0x`head -c20 /dev/urandom|od -An -tx1|tr -d ' \n'`" ==> ./asymptote/.rb.notes <== remaining pdf issue - toolchain pdflatex #=> https://github.com/vectorgraphics/asymptote/pull/351 date ==> ./checkstyle/.rb.notes <== java toolchain date+time ; xmvn random uuid +++ new//usr/share/java/checkstylecompilation.properties 2020-03-09 23:52:37.968994653 +0000 ==> ./cockpit/.rb.notes <== #=> https://github.com/cockpit-project/cockpit/pull/14276 date ; FTBFS-2035 ==> ./deepin-desktop-schemas/.rb.notes <== # = https://github.com/linuxdeepin/developer-center/issues/5117 golang ordering #=> https://github.com/linuxdeepin/deepin-desktop-schemas/pull/98 ==> ./deno/.rb.notes <== rust toolchain? binary order ==> ./doxygen/.rb.notes <== => https://bugzilla.opensuse.org/show_bug.cgi?id=1201579 = https://github.com/doxygen/doxygen/issues/8158 toolchain, ASLR ==> ./elementary-xfce-icon-theme/.rb.notes <== => SR 1106231 = https://gitlab.gnome.org/GNOME/pango/-/issues/729 toolchain pango ASLR+readdir order ==> ./epy/.rb.notes <== time-based python .pyc, minor ==> ./ezmorph/.rb.notes <== toolchain javadoc ==> ./findbugs/.rb.notes <== java toolchain date+time gets injected into docs and .jar: ==> ./gegl/.rb.notes <== = https://gitlab.gnome.org/GNOME/gegl/-/issues/337 parallelism, memory +++ new//usr/share/gir-1.0/Gegl-0.4.gir 2023-06-26 00:00:00.000000000 +0000 ==> ./ghc-bootstrap/.rb.notes <== TODO filesys order in /usr/lib/ghc-8.2.1/package.conf.d/package.cache ==> ./gh/.rb.notes <== found range good=1704505952 bad=1704507877 (2024-01-06T02:24:37) #= https://github.com/cli/cli/issues/6259 FTBFS-2023 ==> ./ginac/.rb.notes <== pdf from TEXI2DVI ginac.texi => ginac.pdf ==> ./git-interactive-rebase-tool/.rb.notes <== => https://github.com/MitMaro/git-interactive-rebase-tool/pull/881 date --- old /usr/bin/interactive-rebase-tool (objdump) ==> ./glucat/.rb.notes <== pdflatex toolchain pdf /usr/share/doc/packages/glucat-doc/GluCat-API-reference-manual.pdf ==> ./gnutls/.rb.notes <== FTBFS --build-opt=--vm-custom-opt=-rtc base=2038-01-25T00:00:00 failed found range good=1943078121 bad=1943080046 (2031-07-29T08:27:26) ==> ./golang-github-prometheus-prometheus/.rb.notes <== #=> https://github.com/prometheus/promu/pull/267 user host #=> https://github.com/prometheus/prometheus/pull/12515 user host date ==> ./goldendict-ng/.rb.notes <== => https://codereview.qt-project.org/c/qt/qtbase/+/494174 qmake toolchain date+time = https://bugreports.qt.io/browse/QTBUG-115737 qmake toolchain date+time ==> ./google-noto-fonts/.rb.notes <== => https://github.com/notofonts/Arimo/pull/17 downstream patch fix caused mtime to creep into build results - timestamp - seconds via patch mtime /usr/share/fonts/truetype/Arimo-BoldItalic.ttf ==> ./grommunio-web/.rb.notes <== #=> https://github.com/grommunio/grommunio-web/pull/8 make/find filesys readdir order from ["/bin/sh", "-c", "cat client/third-party/tokenizr/tokenizr.js client/third-party/tinymce/TinyMceTextArea.js > deploy/client/third-party/ux-thirdparty-debug.js"] - started ==> ./grpc/.rb.notes <== => SR 1102203 grpc drop log ==> ./gstreamer-plugins-rs/.rb.notes <== rust/llvm asm diff variations in /usr/lib64/pkgconfig/gstwebrtchttp.pc ==> ./guile-parted/.rb.notes <== => SR 1102184 guile-parted parallelism = https://bugzilla.opensuse.org/show_bug.cgi?id=1170378 parallelism into guile object .go files ==> ./httpie/.rb.notes <== FTBFS-SSL found range good=2180619253 bad=2180621178 (2039-02-06T16:06:18) ==> ./icinga2/.rb.notes <== => SR 1104874 hostname in System.BuildHostName ==> ./icu/.rb.notes <== FTBFS-2023 osc build --vm-type=kvm --noservice --clean --build-opt=--vm-custom-opt="-rtc base=2023-09-16T07:30:00" standard FTBFS-DST osc build --vm-type=kvm --noservice --clean --build-opt=--vm-custom-opt="-rtc base=2022-10-30T00:30:00" standard ==> ./java-20-openjdk/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1213796 FTBFS-2032 found range good=1987887184 bad=1987889714 (2032-12-28T23:35:14) ==> ./kakoune/.rb.notes <== FTBFS-j1 osc build --vm-type=kvm --noservice -j1 standard ==> ./kernel-obs-build/.rb.notes <== => https://bugzilla.opensuse.org/show_bug.cgi?id=1189305 ==> ./libarchive/.rb.notes <== => SR 1100254 version update with below fixes => https://github.com/libarchive/libarchive/pull/1836 FTBFS-2038 ==> ./libgav1/.rb.notes <== FTBFS-cpu [ 853s] 4 - common_avx2_test (ILLEGAL) ==> ./libkolabxml/.rb.notes <== remaining order issue from CPU => SR 943530 ASLR ==> ./liquid-dsp/.rb.notes <== => SR 1107870 CPU autodetect => SR 630018 ==> ./mathgl/.rb.notes <== Qt qrc .png, .pdf random example .png ==> ./memcached/.rb.notes <== => https://github.com/memcached/memcached/pull/1074 FTBFS-2038 => https://github.com/memcached/memcached/pull/927 FTBFS-2038 ==> ./memtest86+/.rb.notes <== /boot/efi/EFI/memtest86/memtest.efi differs at offset '292' (Linux/x86 Kernel, Setup Version 0x20c, bzImage, Version Memtest86+ v6.10, RW-rootFS) --- old /boot/efi/EFI/memtest86/memtest.efi (hex) ==> ./mhvtl/.rb.notes <== tar/gz /usr/lib/firmware/mhvtl/mhvtl_kernel.tgz ==> ./mingw64-gcc/.rb.notes <== PE header timestamps? ==> ./mozc/.rb.notes <== => SR 1104227 FTBFS rpm %jobs ==> ./ocaml-camlp-streams/.rb.notes <== = https://github.com/ocaml/camlp-streams/issues/9 parallelism ==> ./openmpi5/.rb.notes <== => https://github.com/openpmix/openpmix/pull/3112 date + date/year sphinx toolchain? date into html/searchindex.js ==> ./orthanc-ohif/.rb.notes <== => https://orthanc.uclouvain.be/hg/orthanc-ohif/rev/154cb76a042f sent by mail to sebastien.jodogne@uclouvain : order, gzip timestamp from gzip.compress variations in /home/abuild/rpmbuild/BUILD/OrthancOHIF-1.0/build/AUTOGENERATED/StaticAssets.cpp ==> ./orthanc-volview/.rb.notes <== => https://orthanc.uclouvain.be/hg/orthanc-volview/rev/c50afec9f978 order, gzip mtime ==> ./ouch/.rb.notes <== # solved by version update: rust libzstd_sys read_dir order => https://github.com/gyscos/zstd-rs/commit/6fe67d6a ==> ./pandoc-cli/.rb.notes <== = ghc toolchain parallelism https://gitlab.haskell.org/ghc/ghc/-/issues/12935 ==> ./perl-Net-DNS/.rb.notes <== = https://rt.cpan.org/Ticket/Display.html?id=149456 FTBFS-2038 = https://github.com/jwilk-mirrors/perl-net-dns/issues/1 FTBFS-2038 ==> ./postgis/.rb.notes <== => SR 1101964 parallelism becomes reproducible with parallelism=1 parallelism2=1 multibuildrbk ==> ./pympress/.rb.notes <== date+time from python-Babel : fix in rb:test --- old /usr/lib/python3.11/site-packages/pympress/share/locale/zh_TW/LC_MESSAGES/pympress.mo (hex) ==> ./python3-pyside6/.rb.notes <== _smp_build_ncpus embedded in .src.rpm https://github.com/rpm-software-management/rpm/issues/2343 ASLR ==> ./python-bpython/.rb.notes <== => SR 1100750 drop sphinx doctrees ==> ./python-bson/.rb.notes <== .=> https://github.com/py-bson/bson/pull/117 FTBFS-2038 => https://github.com/pypa/setuptools/commit/5a0404fa3875a069f7a6436f508116e85… toolchain,filesys ==> ./python-control/.rb.notes <== = https://github.com/python-control/python-control/issues/927 FTBFS-j4 osc build --noservice --vm-type=kvm -j4 standard ==> ./python-cx_Freeze/.rb.notes <== #=> SR 1100867 version upgrade for FTBFS-2038 #=> https://github.com/marcelotduarte/cx_Freeze/pull/1860 FTBFS-2038 ==> ./python-DateTime/.rb.notes <== = https://github.com/zopefoundation/DateTime/issues/56 FTBFS-2038 found range good=2164298238 bad=2164300163 (2038-08-01T18:29:23) ==> ./python-django-graphql-jwt/.rb.notes <== = https://github.com/flavors/django-graphql-jwt/issues/318 FTBFS-2038 ==> ./python-Django/.rb.notes <== #=> https://github.com/django/django/pull/16459 FTBFS-2038 #=> https://github.com/django/django/pull/10994 FTBFS-2028 to 2038 ==> ./python-enaml/.rb.notes <== #=> https://github.com/nucleic/enaml/pull/516 FTBFS-2038 osc build --vm-type=kvm --noservice --clean --build-opt=--vm-custom-opt="-rtc base=2038-02-01T18:00:00" standard ==> ./python-flup/.rb.notes <== => SR 1101194 python-flup drop sphinx doctrees ==> ./python-gns3fy/.rb.notes <== FTBFS-20xx? ==> ./python-grpcio/.rb.notes <== filesys-FTBFS? ==> ./python-HyperKitty/.rb.notes <== toolchain issue? nothing helps from ["python3.11", "build_static_files/manage.py", "compress", "--force"] ==> ./python-iminuit/.rb.notes <== numba toolchain issue #=> https://github.com/scikit-hep/iminuit/pull/355 readdir (python glob for distutil) ==> ./python-librosa/.rb.notes <== unknown numba toolchain issue /usr/lib/python3.9/site-packages/librosa/util/__pycache__/utils.__shear_dense-1846.py39.nbi differs at offset '38' (XENIX 8086 relocatable or 80286 small model) ==> ./python-mpi4py/.rb.notes <== = https://bugzilla.suse.com/show_bug.cgi?id=1212698 lto+parallelism into debug # filterdiff hexdump\ -C R*/usr/lib64/python3.9/site-packages/mpi4py/MPI.cpython-39-x86_64-linux-gnu.so ==> ./python-mysqlclient/.rb.notes <== => SR 1100753 drop sphinx doctrees ==> ./python-pandas/.rb.notes <== random .pyc - ref counters? ==> ./python-pyface/.rb.notes <== = https://github.com/enthought/pyface/issues/1254 date+time ==> ./python-quantities/.rb.notes <== = https://github.com/python-quantities/python-quantities/issues/225 date+time in /usr/lib/python3.9/site-packages/quantities/constants/_codata.py ==> ./python-rdflib/.rb.notes <== toolchain? random Graph identifier ==> ./python-scikit-learn/.rb.notes <== parallelism via cython+openmp - similar to https://github.com/yt-project/yt/issues/4611 random FTBFS-j4 on bernhards ==> ./python-scipy/.rb.notes <== => https://github.com/scipy/scipy/pull/19124 sort python readdir/os.walk => https://github.com/scipy/scipy/pull/19123 drop random path ==> ./python-snimpy/.rb.notes <== = https://github.com/vincentbernat/snimpy/issues/106 stuck tests/test_main.py::TestMain::test_loadfile : osc build --clean --noservice --vm-type=kvm --build-opt=--vm-custom-opt="-rtc base=2038-01-19T08:00:00" standard = https://github.com/vincentbernat/snimpy/issues/105 j1? stuck test after ==> ./python-tasklib/.rb.notes <== => https://github.com/GothenburgBitFactory/taskwarrior/pull/3052 fix FTBFS-2038 = https://github.com/GothenburgBitFactory/taskwarrior/issues/3050 FTBFS-2038 - toolchain from taskwarrior int overflow ==> ./python-Telethon/.rb.notes <== => https://github.com/LonamiWebs/Telethon/pull/4163 sort order in /usr/lib/python3.9/site-packages/telethon/tl/alltlobjects.py from telethon_generator/generators/tlobject.py ==> ./python-toolz/.rb.notes <== other python3 pyc toolchain ASLR ; needs bpo-37596: Make `set` and `frozenset` marshalling deterministic (GH-27926) ==> ./python-waitress/.rb.notes <== => SR 1100756 Drop sphinx doctrees ==> ./python-WebOb/.rb.notes <== => SR 1100758 python-WebOb drop sphinx doctrees ==> ./python-WebTest/.rb.notes <== 1100760 python-WebTest drop sphinx doctrees ==> ./python-xarray-einstats/.rb.notes <== numba toolchain issue ==> ./python-yt/.rb.notes <== = https://github.com/yt-project/yt/issues/4611 parallelism => https://github.com/yt-project/yt/pull/4609 python filesys order ==> ./python-zope.deprecation/.rb.notes <== => SR 1100560 drop sphinx doctrees ==> ./python-zope.event/.rb.notes <== => SR 1100761 python-zope.event drop sphinx doctrees ==> ./python-zope.hookable/.rb.notes <== => SR 1100764 python-zope.hookable drop sphinx doctrees ==> ./python-zope.i18nmessageid/.rb.notes <== => SR 1100765 python-zope.i18nmessageid drop sphinx doctrees ==> ./qtox/.rb.notes <== => SR 1103451 date ==> ./s3fs/.rb.notes <== #=> https://github.com/s3fs-fuse/s3fs-fuse/pull/2026 date -/usr/share/man/man1/s3fs.1.gz ==> ./scheme48/.rb.notes <== unreproducible dump ==> ./sharpfont/.rb.notes <== mono dll ==> ./sonic-pi/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1208969 FTBFS-2038 from app/server/beam/tau/test/erlang_tau_osc_test.exs ErlangTauOSCTest ==> ./starship/.rb.notes <== => https://github.com/starship/starship/pull/5352 filesys readdir, rust in /usr/bin/starship ==> ./tango-icon-theme/.rb.notes <== = https://gitlab.gnome.org/GNOME/librsvg/-/issues/1015 unknown toolchain from librsvg - probably same as https://gitlab.gnome.org/GNOME/pango/-/issues/729 --- old /usr/share/icons/Tango/128x128/apps/internet-news-reader.png (hex) ==> ./texlive/.rb.notes <== = rpm https://github.com/rpm-software-management/rpm/issues/2343#issuecomment-167… => SR 966045 minor gzip mtime ==> ./time-api/.rb.notes <== javadoc ; copyright year ; filesys ==> ./tiny/.rb.notes <== rust unknown/nothing helps /usr/bin/tiny differs in assembler output ==> ./warp/.rb.notes <== = https://github.com/briansmith/ring/issues/1625 rust/ring filesys from ./vendor/ring/build.rs read_dir ==> ./WSL-DistroLauncher/.rb.notes <== PE timestamp ==> ./xindy/.rb.notes <== = https://sourceforge.net/p/xindy/bugs/65/ report FTBFS-2036 osc build --vm-type=kvm --noservice --clean --build-opt=--vm-custom-opt="-rtc base=2036-02-07T06:30:00"

3 3