June 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

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

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

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

Packages in OBS not configured for Factory
by Roger Oberholtzer 28 Aug '23

28 Aug '23

I have a newbie question about the decision about what targets a package in OBS are built for. I mean about the logic behind the choice of which to enable. I quite often find that packages are enabled for only 15.2, or only Tumblwweed. But it is quite common that the packages are not enabled for all current openSUSE/SUSE releases. For exampl (not a complaints against this ptroject! I just happen to be following the status of the tensorflow2 and it took me here as a unresolvable package): https://build.opensuse.org/package/show/devel%3Alanguages%3Apython/python-g… Why would a project in devel:languages:python not have Factory enabled? I know that in user's own builds, them might unfortunately do this. But in a place like devel:languages:python, I would have thought the all current openSUSE/SUSE targets would generally be enabled. If it is a 'I don't have time' thing, then I'm okay with that. No problem. I am curious if it is something else that I have just not cottoned on to. -- Roger Oberholtzer

6 14

New package submission for Factory: xdp-tools
by Shung-Hsi Yu 25 Jul '23

25 Jul '23

Hi, I'd like to submit a new package from network to Factory. The package is xdp-tools, which consists of utilities, helper library, and example programs for use with eXpress Data Path (XDP). XDP is a high performance and user-programmable network data path in the Linux kernel, supported since Linux Kernel v4.8. It allows bypassing the kernel's networking stack for performance, but still preserve the possibility of failing back to the network stack if needed; while the user-programmable part are done with eBPF programs. xdp-tools packaged itself provides a few utilities that are powered by XDP under the hood: - xdpdump: a tcpdump-like tool that captures packet - xdp-filter: packet filtering utility with drop rates up to tens of millions of packets per second per core - xdp-trafficgen: network traffic generator that can generate millions of packets per second per core - xdp-loader: simple loader for XDP program with support for attaching multiple XDP program to the same interface - xdp-monitor: monitors and display various XDP related statistics and events - xdp-bench: XDP benchmarking tool It also comes with a helper library libxdp that does the heavy lifting and libxdp-devel that provides the programming interface for those who needs finer control. This is a bit of a late addition. When libbpf (which is in Factory) remove its support for AF_XDP in 2021, the features are moved in libxdp[1]; so in an ideal world xdp-tools should have already been added back then. But better later then never :) Shung-Hsi 1: https://github.com/libbpf/libbpf/wiki/Libbpf:-the-road-to-v1.0#xskch-is-mov…

3 3