February 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

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

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

openSUSE Release Engineering meeting 08.02.2023
by ddemaio 16 Mar '23

16 Mar '23

All meeting minutes can be found here: https://etherpad.opensuse.org/p/ReleaseEngineering-meeting Meeting is hosted here https://meet.opensuse.org/ReleaseEngineeringMeeting ## Attendees DimStar, ddemaio, bittin, rbrown, Sarah, maxlin, Axel, lkocman, Adrian ## Leap Code submission deadline for SLES 15 SP5 Beta4 is today (Jan 25th) at 15:00. Leap Builds were stuck on https://bugzilla.opensuse.org/show_bug.cgi?id=1207395 and previously https://bugzilla.suse.com/show_bug.cgi?id=1206718 Due to this we were not able to produce a decent build that would give us good idea about quality. I'm bit worried that the actual beta release might be delayed. Cisco openh264 setup is finialized on our side https://news.opensuse.org/2023/01/24/opensuse-simplifies-codec-install/ ## openSUSE Tumbleweed openSUSE:Factory build fail stats: 199 failed 1 unresolvable (two weeks ago: 217 / 16) https://tinyurl.com/ysy4nnnz * openSSL 3 has become the default in Snapshot 0202 (problems when users have openssl-devel installed) * glibc 2.37 has been submitted for inclusion; Staging looks reasonably good so far. This might be one of the fastest glibc updates seen in the last years * Staging:H Ruby 3.2 made some progress, only 1 more yast build fails (y2-packager) * Staging:K tests KDE Plasma 5.27 beta * Staging:L has a few failures collected: * gpg2: breaks gpgme * ant and xmlgraphics-common: breaking ant-antlr and xmlgraphics-fop * Staging:M test to also build python311 modules * Staging:O: preparation work to identify the minimal list of 'i586' builds to enable in openSUSE:Factory to allow wine/steam to build/install (currently 992 packages, and counting; big part of it is for rpmlint and such things) * Staging:Gcc7: early experiments to set GCC 13 as distro compiler i586 carve-out from Factory => Automatic migration kicked off with snapshot 0201. The first 'zypper dup' after changing the repo could include a bunch of 'package downgrades' as the rebuild counters are not synced across projects. By end of March, we expect all users to have completed the migration (at least one zypper dup to get the new repos configured), as by then we disable build/publish of i586 packages (except the ~1800 identified in Staging:O - target was wine there) ## Richard (MicroOS) Presentations at FOSDEM about MicroOS Desktop and MicroOS https://www.youtube.com/watch?v=4WuYGcs0t6I "I was wrong about Flatpak, AppImage, and Snap" https://video.fosdem.org/2023/H.1308%20(Rolin)/image_linux_secureboot_suse_… "openSUSE MicroOS Design" https://fosdem.org/2023/schedule/event/image_linux_secureboot_converging_pa… "Converging image and package based OS updates" Desktop-GNOME: Ready for Release, but not released Technically everything is working and release quality in MicroOS GNOME. NO KNOWN BLOCKERS! \o/ Not yet formally released Tests are needed PR/Marketing needed Desktop-KDE: Still Alpha, discussions about maybe considering it Beta, in the hands of the (lone) main maintainer. Next Steps after release 1. mod-check Working on a "mod-check" tool to report the following to users List of installed (1st party) packages, with comparisions to both an upstream pristine list and previous snapshots Automatically reset official packages to that upstream pristine list, or previous snapshots Any 3rd party packages and their origin Any known unsupported configurations/alterations and offer remedies if possible lkocman: is quite interested in this, as we'll be in position in migration leap 15.X to ALP based community offering mod-check doesn't really 'check' as much as planned at the moment, instead going way further and effectively reinstalling MicroOS Desktop (GNOME) in place, making that new snapshot the new boot target. This will be awesome for any user who wants to 'freshen' up an otherwise heavily altered MicroOS Desktop, or when major Tumbleweed/MicroOS changes occur that otherwise cant be easily modeled in patterns. It also potentially could be a method of migrating non-transactional systems to a transactional one. Heavy testing/development underway..and possibly a rename if mod-check doesn't start actually -checking stuff soon. 2. YaST-less installation media with FDE by default Bugs still WIP osinfo-db still doesn't recognise MicroOS as a seperate distribution - debates with upstream ongoing ## Max Leap 15.5 * The orphan package issue occurred in the last Leap build should be fixed, the problem should disappear in the next build * KDE updates is still pending in staging project, it has been just missing the legal review, but KDE staging now has a lot of build fails, need to update those pending submissions to a working version if qt/kdelibs update already accepted into SLE15, will talk to Antonio ** Correction: recheck it, it turned out the contrary, KDE staging have got updated, but qt/kdelibs part is pending for SLE15 SP5 * I'll file the last pacakge updater from Factory to Backports, after we entering Beta phase I'll not trigger that updater ## Guillaume - Arm Not available Tumbleweed: * Blocked due to a broken binutils patch for armv7. Will be unblocked by https://build.opensuse.org/request/show/1060656 * WiFi works again on RPi3/4 (and other systems): https://bugzilla.suse.com/show_bug.cgi?id=1206697 * Pointer Authentication issue, seen in zypper has been fixed: https://bugzilla.suse.com/show_bug.cgi?id=1206684 * NVIDIA: tester with aarch64 server and NVIDIA card wanted - Proprietary drivers are now available for aarch64 (only G06): https://download.nvidia.com/opensuse/tumbleweed/ - New opengpu driver also available in OBS: https://build.opensuse.org/project/monitor/X11:Drivers:Video lkocman to check on who is the aarch64 + nvidia effort blocked on. I recall that there was a chosen point of contact. Leap: * 15.5 aarch64: covered by Leap section above * 15.5 armv7: no blocker ALP: * No aarch64 specific issues 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. 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 ## Sarah - s390x Tumbleweed * Tumbleweed is rolling Leap: * tests are failing because of timeout: Last year there was a SLE bug report (not accessible for the community) * qore updated, but qore-doc is included in qore and should be manually removed from factory: https://build.opensuse.org/request/show/1063674?notification_id=37988455 Sarah needs a help on the request^ => fixed Presentation at FOSDEM about Linux Distributions Collaboration and Upstream Collaboration in the Linux Distributions Working Group at the Open Mainframe Project: https://fosdem.org/2023/schedule/event/open_mainframe_project/ -> CentOS Stream want to join and there is the requirement for an equal Working Group for PowerPC Sarah will give the next presentation (via Accenture) at Chemnitzer Linuxtage. They want to represent also the Open Source Projects Accenture employees are contributing to. ## Doug * Need to order marketing material for CLT & SCALE * GSoC * Application submitted * Completed meetup * New projects added * oSC23 * Waiting on contract signature (in legal review) * 20 registered, 13 submissions lkocman: did send an experimental e-thank yous. Did it work? Axel: issue with the time on the email. lkocman will look into it. * FOSDEM * Good turnout * Thank you to all the volunteers who helped with the booth * Find videos at https://video.fosdem.org/2023/ * https://ftp.fau.de/fosdem/2023/UA2.114%20(Baudoux)/containerised_apps.webm * https://ftp.fau.de/fosdem/2023/UA2.114%20(Baudoux)/open_mainframe_project.w… * Taking care of TSP requests * FLOSS Weekly https://twit.tv/shows/floss-weekly * Podcast scheduled this evening ## Dirk Not available * Initial x86_64-v3 glibc hwcaps package has landed in Factory (libxmlb - visible in GNOME repositories openqa runs) * Determine list of extra shared libraries to enable (likely all compression and media decoding libraries (libpng, jpeg and so on) * Helped with OpenSSL 3.x switch and Python 3.11 modules enablement * Starting to draft https://en.opensuse.org/openSUSE:OpenSUSE_Tumbleweed_Maintainer_Policy (draft, will be announced on the mailing list when ~ ready) DimStar: ~150 python modules are currently failing with 3.11, a lot of fallout is expected. (enabling 3.11 will roughly double those numbers judging from the current devel project state) * Continued work on SUSE:ALP:RISCV * force published 15.4 and 15.5 for armv7 builds, openqa builds have been triggered it appears it is set to do post-release testing? * qemu/libseccomp 15.5 failure still in investigation Biggest speedup can be observed by switching zlib to zlib-ng, so looked into fixing the build failures caused by switching to zlibo-ng-compat ## Wolfgang (Package Hub), Scott Bahling Not available Discussion about moving ipxe package to SLE and release ipxe-bootimgs for x86_64 and aarch64 to HPC-Module (SLE-15-SP5). Needs to be accepted by Michal Svec. If that is the case ipxe will be removed from openSUSE:Backports:SLE-15-SP5 and subpackage ipxe-bootimgs for ppc64le and s390x will be released via subpackages repository. Need to sync with Max regarding the package list for subpackages repository for SLE-15-SP5 when he is back from vacation. 15 SP5 Package HUB channel is set up. Stefan did initial testing and looks good. Some packages are still missing, this is on agenda for today and next week. The workshop regarding Package HUB equivalent for ALP Lubos will schedule a call with wolfgang and Scott to ensure that they're in loop for the High Level requirements document. https://en.opensuse.org/openSUSE:ALP/Workgroups/Community/Workshops/Consumi… Package Hub for SLE-15-SP5 product definition added and SCC is currently picking it up so it will be ready for testing with the beta of SLE-15-SP5 ## Maintenance team (Marcus or Maurizio (m4u)) Fixed a long standing issue with gnome-music that was blocking openqa for a long time. 15.4 is working 5.3 is working 15.5 setup TBD (Mid-to-End February would be preferred). lkocman needs to do official 15.5 Maint setup request beta in ~2 weeks Nothing worrysome, preannoucement for 15.3 EOL was sent to mainling list End of December 2022. There were three chromium updates in single week. 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? Configuration setup problem for Maintenance of Leap 15.4 maintenance updates / openQA Marcus regarding Leap 15.4 Image respin - package set will change, we do need to refresh the packagelist * Lubos to talk to Jan Stehlik, we can't put all on Marcuses shoulder. https://etherpad.opensuse.org/p/ReleaseEngineering-20221110-maintenance-dis… Confirmation that QA/QA-maint team will oversee the setup (issues) Lubos: I was asked to provide requirements for the QA team. Mostly for the GA/current release but also for the update. Lubos will make wiki with requirements (something like maintenance plan perhaps). Marcus will review it. * Leap Micro 5.3 maint setup done ffmpeg - (still unsolved) possible file conflict on the next update, no idea how to avoid vendor switching at the moment. Removing the patch on the openSUSE side (that might contain security fixes) or releasing update on the packman side could fix the issue. Lubos to give Marcus some working contact for the team. ## Adrian - OBS Heads up: working on spdx sbom data generation for containers After changing the signing key of Factory without rebuilding the distribution "osc build" using chroot builds run into the problem that gpg verification of the rpm's failed. To tell osc to use also the old gpg key we introduced a temporary openSUSE:Tumbleweed:OldKey project. We will remove this project again after full rebuild of Factory. This should work for all arches. Users get additional question if they want to trust the additional project once. This solves the issue for people who build against openSUSE:Tumbleweed/standard or openSUSE:Factory/snapshot. It does not solve it when building against openSUSE:Factory/standard directly (not the default in OBS). Dirk: Recommended solution is to use the kvm build (add `build-type = kvm` to your ~/.oscrc) Adrian: Agreed that we should aim for switching the osc default here (also wanted by security team). Still some issues to solve to make it more convinient. ## Project maintainer work flow Status * Base policy to be developed Background on topic found at https://etherpad.opensuse.org/p/ReleaseEngineering-20221221 For me it comes down to a matter of communication. A note like 'thx for your SR, I think we should adapt the following ' or ' we are reviewing your SR, and quite stuck with work...' could already change a lot. Silence for more then 4 week is clearly a perfect way to annoy contributors. And the question should be asked if those unresponsive maintainers are still willing to maintain their projects. Or they may even not be active anymore, another discussion we are having

4 7

will saa7146-based DVB cards stop working in the near future?
by mh＠mike.franken.de 13 Mar '23

13 Mar '23

Hi *, I saw an announcement for the following patch: https://www.spinics.net/lists/linux-media/msg224909.html Does this mean, all of my saa7146-based DVB cards will stop working after the according openSUSE kernel will be released? Or will anyone at SUSE port the deprecated frontend to newer kernels? Sry, if the question sounds silly, but I'm not familiar with the handling of such things regarding kernel or kernel drivers. Thx and bye. Michael.

12 33

openSUSE Leap 15.5 Windows Subsystem for Linux
by Andreas Artz 10 Mar '23

10 Mar '23

Hey folks! I am interested in testing out openSUSE Leap 15.5 on WSL. Is there a way to get the image in order to help out? Best Andi

3 4

Which dev repo I should submit if I want to add yacreader to openSUSE Factory?
by Xu Zhao 04 Mar '23

04 Mar '23

Hi folks, I am using yacreader (https://www.yacreader.com/) for e-book and comics reading. I am interested in contributing my packaging at https://build.opensuse.org/package/show/home:opensuse_zh/yacreader to the Factory repo, but I need to first find a development repo to host it. Which one is the best to submit this application? Best, Xu -- Xu Zhao i(a)xuzhao.net

2 1

openSUSE:Factory - Build fail notification
by DimStar / Dominique Leuenberger 28 Feb '23

28 Feb '23

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

1 0

i586 port split from Factory
by Dominique Leuenberger / DimStar 28 Feb '23

28 Feb '23

Dear Tumbleweed users, more specifically users of the 32bit intel architecture (i586), Throughout the last few weeks, I have prepared the entire setup, and it is now time to let 'i586' live its own life. ## What does this mean for users ## =================================== The repositories need to be adjusted. The main repositories are no longer http://download.opensuse.org/tumbleweed/repo/oss and http://download.opensuse.org/tumbleweed/repo/non-oss, but those two are now moved to https://download.opensuse.org/ports/i586/tumbleweed/repo/oss and https://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss You should update your repository list accordingly when running an i586 setup (the command 'arch' would tell you) ## i586 will be removed from the main tree ## ============================================= You have until the end of March) to migrate to the new repositories. After April 1st (no joke), i586 packages will no longer be shipped as part of the main repositories (we will keep shipping the -32bit.x86_64 packages for things like steam, wine, …) ## What does this mean for contributors / package maintainers ## ================================================================ Just like for all the other ports, we as a community strive to support the architecture as well as we can. If somebody submits fixes for those architectures, we accept them, assuming they are not causing problems to the main architecture (x86_64). The Staging process will not monitor all i586 builds anymore. If something is not supported on i586 and should not be shipped (or build-attempted), we keep on using the ExcludeArch tags, as we did in the past. ## Is the i586 port tested / usable? ## ======================================== Just like all the other ports, i586 inherits the same sources, so is built from the same tarballs and spec files as the main x86_64 tree. After the build is complete, the port is handed over to openQA in the same way too and tested there. The i586 test progress can be monitored at https://openqa.opensuse.org/group_overview/75 Compared to when i586 was part of the main group I have even extended the test coverage a bit and the GNOME, KDE, and XFCE desktops are now tested on this architecture. In case there are issues only on i586, not seen on x86_64, this now even allows us to release x86_64 without having to risk i586 (or explicitly having to ignore it), which is a win. ## Call for help - somebody to look after the port ## ===================================================== The port still requires somebody to take responsibility for it. As is visible on openQA, since December 11 this port has been silently rolling along the main port. Most snapshots have been published without much interaction at all. Yet, when something goes wrong, somebody needs to look after it and 'chase the relevant fixes'. Some people have expressed their interest to take on this task, but nobody has fully committed to it (of course there was also the holiday when people shifted their priorities to families, which is perfectly fine) Please help spread the word so that all i586 users are aware of this change. Cheers, Dominique

9 21