March 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

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

So Leap is transitioning to a 16 variation?
by Fritz Hudnut 10 Apr '23

10 Apr '23

> > > > It is still possible to make something very much like Leap 15 from the > ALP sources if there is enough community interest in helping to support > packages. It in many cases may even be migratable from Leap 15, A couple > of us worked on a proof of concept during SUSE's last hackweek look > forward to a talk on it at this years conference. > > -- > Simon Lees (Simotek) http://simotek.net @Dominique Thanks for the detailed response on the question. @Simon Thanks also for your response, it seems like the "something very much like Leap 15" is what a number of posters here, and myself, would be interested in . . . i.e, the logical extension of the current Leap concept/technology. I'm running both TW and Leap 15.5 . . . and somewhere "in between" would be the "sweet spot" for me, the end user on aging hardware. I also run Debian Bookworm and Sid . . . seems like of late Sid is "more stable" than TW, but let's say they are roughly "equivalent" . . . Debian has "unstable," "testing" and "stable" . . . "testing" is the famed "middle way" . . . having newer packages, but which have first have run through the crucible of "unstability" . . . . That's where the "gently rolling" concept of future iterations of Leap would come in, i.e., not a total rewrite of the system, for each new day (or whatever it is) vs . . . rolling in new packages to a generally "stable" base, that doesn't run into massive package upgrades every few months, etc. On the new idea of Leap 16 using "containers" . . . have yet to mess with that concept in linux. It sounds like what Apple did with the last of the OSX variations, where they went to apfs formating and it was possible to set up . . . ??? semi-fluid "containers" that were not "solid" like a "partition" . . . but would be similar, place to install a distro?? Apfs formatting seemed to just mess up the system . . . . So, the point of containers is that they are "easier" to make and/or erase?? Or, this is something to do with SSD technology, where "boundaries" like partitions have less meaning, and all of the data is actually "shared" by the entire disk, so containers just gently sketch in the general area where the data will be stored, but it isn't just there, it's everywhere??

7 10

[opensuse-factory] reproducible builds status 2023-02
by Bernhard M. Wiedemann 02 Apr '23

02 Apr '23

Hi, Did some patches this month. Nothing spectacular. 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-01/ I uploaded https://rb.zq1.de/compare.factory-20230301/ today https://rb.zq1.de/spec/glossar.txt explains the meaning of below values: total-packages: 14802 (+61) build-tried: 14744 (+63) build-failed: 30 (+3) build-n-a: 255 (+29) build-succeeded: 14459 (+30) build-official-failed+na: 173 (+67) build-compare-failed: 468 (-6) build-compare-succeeded: 13991 (+36) verify-failed: 182 (+74) verified-semi-reproducible: 10913 (+246) bit-by-bit-identical: 13849 (+154) not-bit-by-bit-identical: 615 (-119) not-bit-by-bit-identicalcheck: 610 (-124) https://rb.zq1.de/compare.factory-20230301/graph.png shows the change over time https://rb.zq1.de/compare.factory-20230301/unreproduciblerings.txt lists very unreproducible core packages (bootstrap+DVD) Of the badly unreproducible packages, 5 were in ring0 53 were in ring1 That makes it 58/3316 => 1.75 % which is below the overall average of 468/14459 => 3.24 % 615/14459 => 4.25 % of packages are not perfectly reproducible package notes: ==> ./boost/.rb.notes <== = https://github.com/boostorg/boost/issues/741 2038-date influences order +++ new /usr/lib64/libboost_log.so.1.81.0 (objdump) ==> ./buildkit/.rb.notes <== go1.19 toolchain parallelism ==> ./dnscrypt-proxy/.rb.notes <== .src.rpm captures randomness from %vendored_licenses_packager_prep -vendored_licenses_packager install "/tmp/tmp_vendored_dir_6bSEoMWEIw" /home/abuild/rpmbuild/BUILDROOT/dnscrypt-proxy-2.1.3-0.0.x86_64""/usr/share/licenses/dnscrypt-proxy/vendored"" ==> ./docker-compose/.rb.notes <== go1.19 toolchain build-id parallelism ==> ./dpdk/.rb.notes <== parallelism in /usr/share/doc/packages/dpdk/dpdk/html/searchindex.js => SR 1067125 dpdk clean Sphinx leftover files ==> ./ebumeter/.rb.notes <== => SR 1066747 CPU: -march=native from source/Makefile:CXXFLAGS += -march=native ==> ./elementary-xfce-icon-theme/.rb.notes <== = https://gitlab.gnome.org/GNOME/pango/-/issues/729 toolchain pango ASLR+readdir order --- old /usr/share/icons/elementary-xfce/apps/24/accessories-dictionary.png (hex) ==> ./findbugs/.rb.notes <== date+time gets injected into docs and .jar: ==> ./firecracker/.rb.notes <== => https://github.com/firecracker-microvm/firecracker/pull/3445 = https://github.com/firecracker-microvm/firecracker/issues/3439 hashmap order ==> ./galera-4/.rb.notes <== FTBFS-2037 found range good=2179559341 bad=2179561266 (2039-01-25T09:41:06) ==> ./gnutls/.rb.notes <== date in man - probably because patch updates mtime # filterdiff zcat R*/usr/share/man/man1/gnutls-cli.1.gz ==> ./jhead/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1208386 gcc12 toolchain random tmpdir from LTO /usr/bin/jhead differs in ELF sections ==> ./ldas-tools-framecpp/.rb.notes <== doxygen doc toolchain, filesys ==> ./libhugetlbfs/.rb.notes <== => SR 1068331 libhugetlbfs drop unreproducible unused file = https://bugzilla.opensuse.org/show_bug.cgi?id=1159558 report unreproducible .ldscript file ==> ./nut/.rb.notes <== date in /usr/share/doc/packages/nut/cables/Makefile ==> ./ongres-stringprep/.rb.notes <== xmvn toolchain random UUID, javadoc ==> ./openEMS/.rb.notes <== octave debuginfo, toolchain issue? ==> ./osgi-service-log/.rb.notes <== java date+time +++ new//usr/share/java/osgi-service-log/org.osgi.service.log.jar/META-INF/maven/org.osgi/org.osgi.service.log/pom.properties 2023-01-29 07:14:54.625684100 +0000 ==> ./pentaho-libxml/.rb.notes <== javadoc toolchain ==> ./perl-DBD-MariaDB/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1203310 mariadb toolchain FTBFS-2038 strings /usr/sbin/mariadbd|grep dates.later ==> ./postfish/.rb.notes <== postfish-wisdomrc random order from ==> ./prosody/.rb.notes <== => SR 1066043 /etc/prosody/certs/example.com.crt and other random key+certs - still in version 0.12.2 ==> ./python-aiohttp/.rb.notes <== => https://github.com/aio-libs/aiohttp/pull/7191 FTBFS-2039 found range good=2177495253 bad=2177497178 (2039-01-01T12:19:38) ==> ./python-azure-agent/.rb.notes <== python3.10 toolchain .pyc ASLR ==> ./python-azure-ai-ml/.rb.notes <== python3.10 toolchain .pyc ASLR ==> ./python-dtaidistance/.rb.notes <== SR 1068462 drop unreproducible unnecessary file ==> ./python-future/.rb.notes <== python3 toolchain ASLR ==> ./python-pyinstaller-hooks-contrib/.rb.notes <== python3.10 toolchain .pyc ASLR ==> ./python-quantities/.rb.notes <== date+time in /usr/lib/python3.9/site-packages/quantities/constants/_codata.py ==> ./python-sqlalchemy-migrate/.rb.notes <== => SR 1067129 python-sqlalchemy-migrate clean Sphinx leftover files ==> ./python-sunpy/.rb.notes <== = https://github.com/sunpy/sunpy/issues/6030 FTBFS-2023 found range good=1687994158 bad=1687997370 (2023-06-29T00:09:30) ==> ./qca/.rb.notes <== FTBFS-2031 found range good=1924935388 bad=1924937313 (2030-12-31T08:48:33) ==> ./qt6-declarative/.rb.notes <== /usr/lib64/libQt6QuickDialogs2QuickImpl.so.6.4.2 differs in ELF sections order variation in qtdeclarative-everywhere-src-6.4.2/build/build.ninja , ColorDialog_qml.cpp from qmlcachegen ==> ./qt6-quick3d/.rb.notes <== TODO /usr/lib64/libQt6Quick3DHelpers.so.6.4.2 differs in ELF sections ==> ./qt6-webengine/.rb.notes <== Qt toolchain issue ; hard to debug because of slow compile time ==> ./smuxi/.rb.notes <== = https://github.com/mono/mono/issues/20172 mono mdb ==> ./spotifyd/.rb.notes <== = https://github.com/Spotifyd/spotifyd/issues/1167 => https://github.com/librespot-org/librespot/commit/9de1f38e926de827cf2f05b4d… random ==> ./tigervnc/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1208478 RSA key ==> ./transfig/.rb.notes <== = https://bugs.ghostscript.com/show_bug.cgi?id=696765 date+time from ghostscript toolchain /usr/share/doc/packages/transfig/fig2mpdf/sample-presentation.pdf differs at offset '13201' (PDF document, version 1.5) ==> ./velociraptor/.rb.notes <== #= https://bugzilla.opensuse.org/show_bug.cgi?id=1207369 report date filterdiff strings RPMS*/usr/bin/velociraptor ==> ./xemacs-packages/.rb.notes <== date+time in .elc date+time from psgml ==> ./zellij/.rb.notes <== reproducible again for unknown reason. was: /usr/bin/zellij differs in ELF sections from LTO? random?

2 2

openSUSE:Factory - Build fail notification
by DimStar / Dominique Leuenberger 31 Mar '23

31 Mar '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. - msr-safe: Uninstallable: nothing provides kernel-uname-r = 6.1.12-1-default needed by msr-safe-kmp-default-1.4.0_k6.1.12_1.i586 - python-tifffile: 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

New Tumbleweed snapshot 20230330 released!
by Dominique Leuenberger 31 Mar '23

31 Mar '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: drkonqi5 glslang (12.0.0 -> 12.1.0) hplip libguestfs libopenmpt (0.6.8 -> 0.6.9) okular patterns-media shaderc (2022.4 -> 2023.2) xorg-x11-server yast2 (4.6.1 -> 4.6.2) yast2-country (4.6.0 -> 4.6.1) === Details === ==== drkonqi5 ==== Subpackages: drkonqi5-lang - Replace '%service_del_postun -n' with '%service_del_postun_without_restart' ==== glslang ==== Version update (12.0.0 -> 12.1.0) - Update to release 12.1.0: * Reject non-float inputs/outputs for version less than 120 * Fix invalid BufferBlock decoration for SPIR-V 1.3 and above * Add HLSL relaxed-precision float/int matrix expansions * Block decorate Vulkan structs with RuntimeArrays * Support InterlockedAdd on float types - Delete 0001-build-set-SOVERSION-on-all-libraries.patch: fixed upstream - Split part of glslang-devel to glslang-nonstd-devel. ==== hplip ==== Subpackages: hplip-hpijs hplip-sane hplip-udev-rules - Add patch to fix hplip applying printf string format parsing to printer attributes returned from CUPS (such as "dnssd://foo%20series._ipp._tcp.local/?uuid=...") which results in a segfault (boo#1209866, lp#2013185): * fix-printer-attributes-parsing.patch ==== libguestfs ==== Subpackages: libguestfs-xfs libguestfs0 - Enable LTO as it works fine now (use FAT lto objects for static libs). ==== libopenmpt ==== Version update (0.6.8 -> 0.6.9) - Update to 0.6.9 * [Bug] An exception could be thrown during rendering when trying to access the release node of an empty envelope. * The fix for the OPL cutoff bug introduced in libopenmpt 0.6.7 was incomplete. * ULT: Offset commands exceeding 65535 samples were sometimes not imported correctly even if there was room for them. * After seeking with seek.sync_samples=1, the filter settings of playing notes were not updated since libopenmpt 0.6.7. * Loading of and seeking inside (malformed) modules with thousands of short sub-songs has been sped up. ==== okular ==== Subpackages: okular-lang - Add Discount 3 compatibility patch: * 0001-Compile-with-discount-3.patch ==== patterns-media ==== - rest_dvd: Add breeze5-wallpapers (boo#1209838) - Remove rest_core_dvd, it's unused. Some deps were added to it by accident, move them to rest_dvd. - Remove rest_cd_{gnome,kde,x11}, unused. ==== shaderc ==== Version update (2022.4 -> 2023.2) - Update to release 2023.2 * Fix C++20 compatibility: explicitly construct string_piece when comparing to `char *` ==== xorg-x11-server ==== Subpackages: xorg-x11-server-Xvfb xorg-x11-server-extra - U_xserver-composite-Fix-use-after-free-of-the-COW.patch * overlay window use-after-free (CVE-2023-1393, ZDI-CAN-19866, bsc#1209543) ==== yast2 ==== Version update (4.6.1 -> 4.6.2) Subpackages: yast2-logs - Replace calls to mkinitrd with dracut as mkinitrd will be dropped (bsc#1203019) - 4.6.2 ==== yast2-country ==== Version update (4.6.0 -> 4.6.1) Subpackages: yast2-country-data - Replace call to mkinitrd with dracut (bsc#1203019) - 4.6.1

1 0

So Leap is transitioning to a 16 variation?
by Fritz Hudnut 31 Mar '23

31 Mar '23

> > Leap 16.0 Putting high level requirements for Alpha. I think I could > have something usable by end of this week. > https://en.opensuse.org/Portal:16.0 So far everything shows that base > system will have traditional 12 months + overlap support. [QUOTE] Migration path from the previous releases Users will be officially able to upgrade to Leap 16 only from the openSUSE Leap 15.5 transactional update server and from Leap Micro 5.X. There are experimental tools that can be used to migrate a non-transactional-update system, but we highly recommend doing a clean installation instead. The migrated system would have to be btrfs based. [/QUOTE] This is good news . . . will this migration path from 15.5 be available sometime soon? Or, the repos will have to be edited to "16" to make it to Alpha stage materials?? F

12 14