February 2023 - openSUSE Factory - openSUSE Mailing Lists

Re: openSUSE Factory Digest, Vol 168, Issue 3
by Fritz Hudnut 21 Feb '23

21 Feb '23

> ---------- Forwarded message ---------- > From: Larry Len Rainey <llrainey15(a)gmail.com> > To: openSUSE Factory - Mailing List <opensuse-factory(a)opensuse.org>, > OpenSUSE Support <support(a)lists.opensuse.org> > Cc: > Bcc: > Date: Tue, 21 Feb 2023 09:22:17 -0600 > Subject: 15.5 Beta Full disappointment > > The Alpha version of 15.5 had MATE desktop as a choice. MATE is no longer > offer nor is Cinnamon in 15.5. Some say MATE is stale - I say it is Mature, > Stable, and relative bug free - what you want for a stable computer > environment. > > Yes, MATE still is in Tumbleweed, but many of those retired people I > support do not have enough internet to support zypper dup that Tumbleweed > requires way too often. They could not do windows 7, 8, 10 and 11. XP was > the last Windows they were comfortable with. Some still use Windows XP and > the mail app that they used with Windows 95. > > I dropped Windows in the XP days - Centos was the 1st Full time Linux and > I had VirtualBox working with an Windows XP guest on a 4 core computer with > 4mb of ram. I had not completely wean myself off Windows as I had not found > Linux apps to replace my Windows apps. > > Many of us do not care for KDE or Gnome. The other choice LXDE does not > provide all the options needed. > > Looks like 15.4 is the last OpenSUSE version I will be supporting. > > Mint Linux offers MATE as a standard desktop. That will probably be the > winner as it has a long term version. > > Over the next year I will be converting 145 OpenSUSE 15.4 running MATE to > Mint Linux unless you can convince me that MATE is coming. > > Larry Rainey - Unix since 1973, Linux since Mandrake was offered on CD in > 1998. > > @Larry R: I also like MATE quite a bit, I have it as the DE for a few of my distros . . . and I have a Leap 15.5 Alpha>Beta install running. Don't have time to check, but usually any DE can be added into any system . . . via YaSt or possibly just "sudo zypper in mate" ????? If that isn't something you want to mess with, my Leap 15.5 system is running XFCE, which I just picked for the variety. But going back to the early '00's in PPC linux I usually had Xubuntu XFCE and Lubuntu LXDE as the systems most reliable and using the least resources. XFCE is a good choice if MATE can't work in Leap 15.5. Other option, Gecko stable . . . she offers just about every single DE you could imagine for her system . . . Gecko is like ubuntu, a stack on openSUSE . . . works out of the box, etc. Lastly, for the MATE purist is now ubuntu-MATE . . . a bonded system of ubuntu with built-in MATE . . . well supported. I used to have that as an install because I like the simplicity of MATE so much, but ubuntu doesn't play well with others in grub, so, for a single system on a machine, it's fine. If you want a few other non-Debian systems then it messes with UUID numbers. F

1 0

Please improve release notes in the future
by Daniel Noga 21 Feb '23

21 Feb '23

I read announcement https://news.opensuse.org/2023/02/21/leap-reaches-beta-phase/ and it contains two unfortunate misinformations. First, it is not clear, that Plasma missed beta release and will be included a few weeks later. There are already reddit questions what is wrong. Second, "Linux Kernel 5.14.21 will remain the same as that of Leap 15.4.", which is I guess is not true, because every minor release in past contained a lot of driver backports from newer kernels. In the next announcement it will be better to promote info, that number of 5.14.21 does not mean "old kernel", but that it contains graphics (sound, wifi?) drivers of new kernel x.x.x

1 0

Bluetooth issues (ongoing)
by Markus Feilner 21 Feb '23

21 Feb '23

Hi, On my Acer Travelmate connected to a Dell Dock, Bluetooth isn't working after boot. I need to call rfkill and do a bluetooth service restart, then it works flawlessly. This is after a fresh boot: mfeilner@maldacena:~> bluetoothctl Agent registered [bluetooth]# list Controller F4:B3:01:49:51:46 maldacena.feilner-it.net [default] [bluetooth]# devices Device 0C:A6:94:D1:77:5D Büro Regensburg (...) [bluetooth]# connect 0C:A6:94:D1:77:5D Attempting to connect to 0C:A6:94:D1:77:5D [bluetooth]# power on Changing power on succeeded [bluetooth]# connect 0C:A6:94:D1:77:5D Attempting to connect to 0C:A6:94:D1:77:5D Failed to connect: org.bluez.Error.InProgress br-connection-busy [bluetooth]# power off Failed to set power off: org.bluez.Error.Busy Failed to connect: org.bluez.Error.Failed br-connection-unknown Failed to set power off: org.bluez.Error.Failed [bluetooth]# power off Failed to set power off: org.bluez.Error.Failed [bluetooth]# exit mfeilner@maldacena:~> The "connect" commands fail, and after calling them, "power off" will also fail. (Yes, pairing has been successful) I have a solution, but I would love to know the root of the problem and help others, maybe. Here's my little script that fixes it: #!/bin/bash sudo rfkill unblock bluetooth sudo service bluetooth restart sleep 3s bluetoothctl power on After that, Bluetooth works as expected. The script only needs to be called once after boot - I automated that as a start script. I have no idea what goes wrong upon initialization of bluetooth on boot, but only if I call rfkill and restart the service, bluetooth connection to my stereo can be established. I have seen this behaviour also on my media center, the start script fixed it there, too. Any ideas? How can I help? In the meantime, I check the usual pages for a bug related to this. It's been like this for months... -- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Sustainable Open Source Strategy, Networking, Politics, Journalism Knowledge Management, Rubber Ducks, Trainings, Workshops, Documentation https://www.feilner-it.net, 93059 Regensburg Wöhrdstr. 10, +49 170 302 7092 (+Signal) https://mastodon.cloud/@mfeilner https://mastodon.social/@FeilnerIT PGP: 40A3C306F96133067C11CFD9A958A906268C9F0A http://www.feilner-it.net/files/MFpub.asc Xing: http://www.xing.com/profile/Markus_Feilner LinkedIn: https://www.linkedin.com/in/markusfeilner @mfeilner: Mastodon, Matrix, Jabber, ...

6 10

New Tumbleweed snapshot 20230220 released!
by Dominique Leuenberger 21 Feb '23

21 Feb '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: java-11-openjdk openssl-3 (3.0.7 -> 3.0.8) openssl (3.0.7 -> 3.0.8) parole (4.16.0 -> 4.18.0) procps4 (4.0.2 -> 4.0.3) qca-qt5 xfce4-notifyd (0.8.0 -> 0.8.1) zchunk (1.2.3 -> 1.2.4) === Details === ==== java-11-openjdk ==== Subpackages: java-11-openjdk-headless - Remove the accessibility sub-package, since it was never really working and creates another problems (bsc#1205916). It can eventually be built as standalone if needed - Removed patches: * jaw-jdk10.patch * jaw-misc.patch * jaw-nogtk.patch + not needed after the removal of the accessibility sub-package ==== openssl-3 ==== Version update (3.0.7 -> 3.0.8) Subpackages: libopenssl3 libopenssl3-32bit libopenssl3-hmac - Update to 3.0.8: * Fixed NULL dereference during PKCS7 data verification. A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initialization will fail. There is a missing check for the return value from the initialization function which later leads to invalid usage of the digest API most likely leading to a crash. ([bsc#1207541, CVE-2023-0401]) PKCS7 data is processed by the SMIME library calls and also by the time stamp (TS) library calls. The TLS implementation in OpenSSL does not call these functions however third party applications would be affected if they call these functions to verify signatures on untrusted data. * Fixed X.400 address type confusion in X.509 GeneralName. There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. ([bsc#1207533, CVE-2023-0286]) * Fixed NULL dereference validating DSA public key. An invalid pointer dereference on read can be triggered when an application tries to check a malformed DSA public key by the EVP_PKEY_public_check() function. This will most likely lead to an application crash. This function can be called on public keys supplied from untrusted sources which could allow an attacker to cause a denial of service attack. The TLS implementation in OpenSSL does not call this function but applications might call the function if there are additional security requirements imposed by standards such as FIPS 140-3. ([bsc#1207540, CVE-2023-0217]) * Fixed Invalid pointer dereference in d2i_PKCS7 functions. An invalid pointer dereference on read can be triggered when an application tries to load malformed PKCS7 data with the d2i_PKCS7(), d2i_PKCS7_bio() or d2i_PKCS7_fp() functions. The result of the dereference is an application crash which could lead to a denial of service attack. The TLS implementation in OpenSSL does not call this function however third party applications might call these functions on untrusted data. ([bsc#1207539, CVE-2023-0216]) * Fixed Use-after-free following BIO_new_NDEF. The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications. The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash. ([bsc#1207536, CVE-2023-0215]) * Fixed Double free after calling PEM_read_bio_ex. The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected. These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. ([bsc#1207538, CVE-2022-4450]) * Fixed Timing Oracle in RSA Decryption. A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. ([bsc#1207534, CVE-2022-4304]) * Fixed X.509 Name Constraints Read Buffer Overflow. A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. The read buffer overrun might result in a crash which could lead to a denial of service attack. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects. ([bsc#1207535, CVE-2022-4203]) * Fixed X.509 Policy Constraints Double Locking security issue. If an X.509 certificate contains a malformed policy constraint and ... changelog too long, skipping 21 lines ... 7953 AC1F BC3D C8B3 B292 393E D5E9 E43F 7DF9 EE8C (Richard Levitte) ==== openssl ==== Version update (3.0.7 -> 3.0.8) - Update to 3.0.8 ==== parole ==== Version update (4.16.0 -> 4.18.0) Subpackages: parole-lang - Update to version 4.18.0 * Update copyright year * Update bug report address * player: Prevent infinite cycle when setting volume (#119) * Update some icon names (!17) * Reduce hiding controls to 2 seconds (Fixes #80, !12) * autoconf: Some updates * Update `.gitignore` * build: Replace DATADIRNAME no longer set by xfce4-dev-tools >= 4.17.0 * build: Bump GLib minimum required to 2.38 * autoconf: Use AC_CONFIG_MACRO_DIRS (!14) * Fix memory leak when loading cover image (#98) * Fix compilation warnings (!11) * Makefile.am: INCLUDES -> AM_CPPFLAGS * autoconf: Some updates * Remove the deprecated keys from desktop file (!9) * Translation Updates ==== procps4 ==== Version update (4.0.2 -> 4.0.3) Subpackages: libproc2-0 procps4-lang - Update to procps-ng-4.0.3 * library Only changes were in copyright headers and tests * docs: Don't install English manpages twice * pgrep: Add -H match on userspace signal handler merge #165 * pgrep: make --terminal respect other criteria * ps: c flag shows command name again Debian #1026326 * ps.1: Match drs description from top.1 merge #156 * skill: Match on -p again Debian #1025915 * top: E/P-core toggle ('5' key) added to help * vmstat: Referesh memory statistics Debian #1027963 * vmstat: Fix initial si,so,bi,bo,in & cs values issue #15 Debian #668580 * vmstat: Fix conversion errors due to precision merge #75 * w: Add --pids option merge #159 * watch: Pass through beep issue #104 * watch: -r option to not re-exec on SIGWINCH merge #125 * watch: find eol with --no-linewrap merge #157 - Drop patches now upstream * linguas.patch * 82d8e3fa.patch - Port patches * procps-ng-3.3.10-errno.patch * procps-ng-3.3.10-slab.patch * procps-ng-3.3.10-xen.dif * procps-ng-3.3.11-pmap4suse.patch * procps-ng-3.3.8-ignore-scan_unevictable_pages.patch * procps-ng-3.3.8-petabytes.patch * procps-ng-3.3.8-readeof.patch * procps-ng-3.3.8-vmstat-terabyte.dif * procps-ng-3.3.9-w-notruncate.diff * procps-v3.3.3-columns.dif * procps-v3.3.3-ia64.diff * procps-v3.3.3-pwdx.patch * procps-v3.3.3-read-sysctls-also-from-boot-sysctl.conf-kernelversion.diff ==== qca-qt5 ==== Subpackages: libqca-qt5-2 qca-qt5-plugins - Disable the pgp test. It fails randomly. - Remove test that openssl has decided it's wrong [boo#1208393] * Add 0001-Remove-test-that-openssl-has-decided-it-s-wrong.patch ==== xfce4-notifyd ==== Version update (0.8.0 -> 0.8.1) Subpackages: xfce4-notifyd-lang - Update to 0.8.1: * Set 1.5s timeouts for the log dbus proxy * Move log dbus server to its own object/file * Wrap queue item struct creation with a function * Improve old log migration error reporting * Delete old log file if it was empty * Clean up old log action parsing loop * Print a message if log db is busy or locked * Plug memleak when not sending log changed signal * Use GStrvBuilder instead of constructing one manually * Handle empty strings from DBus * Limit notification body to 2 lines in plugin menu * Remove old legacy support options from configure * Ensure gdbus-codegen doesn't generate too-new code * Clean up generate code and deprecate Quit method * Make all notification log access go through dbus * Drop old gtk 3.0 themes (3.20 themes are always used) * Clean up build system * Add hidden setting to restore override-redirect behavior * Remove ChangeLog make target * Markdownify and update the readme * Disconnect from GtkIconTheme::changed when plugin destroyed * Load main panel icon with _load_symbolic() variant * Restore log viewer's scrolled window shadow-type * Update icon when icon-theme changes * Fix incorrect signal handler connections in settings dialog * Translation Updates ==== zchunk ==== Version update (1.2.3 -> 1.2.4) - update to 1.2.4: * Update tests to handle zstd 1.5.4

1 0

openSUSE Leap 15.5 Beta is now available
by ddemaio 21 Feb '23

21 Feb '23

Hi all, I’m happy to announce that we are in the Leap 15.5 Beta phase! The first beta images (Build408.2) should be already synced to mirrors near you and at around 12:00 UTC the front end of get.opensuse.org switches from Alpha to Beta.The official announcement can be found at https://news.opensuse.org/2023/02/21/leap-reaches-beta-phase/ Thank you to all who contributed to this beta release and thank you in advance for testing it. Please contribute to the Beta testing effort and record it on the following document: https://docs.google.com/spreadsheets/d/1AGKijKpKiJCB616-bHVoNQuhWHpQLHPWCb3… v/r Doug

1 0

LegacyX86: port not rolling at the moment
by Dominique Leuenberger 21 Feb '23

21 Feb '23

Dear Tumbleweed LegacyX86 (i586) users - and hackers, The 32bit port has been halted for the last couple days: last published snapshot was 20230208. Starting with 0209, the snapshot has been held back as KDE/Plasma crashes on startup. There is a bug report https://bugzilla.opensuse.org/show_bug.cgi?id=1208188 that likely needs your help to make the i586-port move again. Other users of the port would surely be grateful. Cheers, Dominique

1 0

New Tumbleweed snapshot 20230219 released!
by Dominique Leuenberger 20 Feb '23

20 Feb '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: audit (3.0.6 -> 3.0.9) audit-secondary (3.0.6 -> 3.0.9) elfutils elfutils-debuginfod freeipmi (1.6.9 -> 1.6.10) fuse3 (3.13.1 -> 3.14.0) permissions (1599_20221220 -> 1599_20230217) psmisc python-kiwi (9.24.55 -> 9.24.57) python-reportlab python-zope.event (4.5.0 -> 4.6) python310-pyparsing shadow tree (2.0.4 -> 2.1.0) vim xen === Details === ==== audit ==== Version update (3.0.6 -> 3.0.9) Subpackages: libaudit1 libaudit1-32bit libauparse0 - Enable build for ARM (32-bit) - Update to version 3.0.9: * In auditd, release the async flush lock on stop * Don't allow auditd to log directly into /var/log when log_group is non-zero * Cleanup krb5 memory leaks on error paths * Update auditd.cron to use auditctl --signal * In auparse, if too many fields, realloc array bigger (Paul Wolneykien) * In auparse, special case kernel module name interpretation * If overflow_action is ignore, don't treat as an error (3.0.8) * Add gcc function attributes for access and allocation * Add some more man pages (MIZUTA Takeshi) * In auditd, change the reinitializing of the plugin queue * Fix path normalization in auparse (Sergio Correia) * In libaudit, handle ECONNREFUSED for network uid/gid lookups (Enzo Matsumiya) * In audisp-remote, fix hang with disk_low_action=suspend (Enzo Matsumiya) * Drop ProtectHome from auditd.service as it interferes with rules (3.0.7) * Add support for the OPENAT2 record type (Richard Guy Briggs) * In auditd, close the logging file descriptor when logging is suspended * Update the capabilities lookup table to match 5.16 kernel * Improve interpretation of renamat & faccessat family of syscalls * Update syscall table for the 5.16 kernel * Reduce dependency from initscripts to initscripts-service - Refresh patches (context adjusment): * audit-allow-manual-stop.patch * audit-ausearch-do-not-require-tclass.patch * audit-no-gss.patch * enable-stop-rules.patch * fix-hardened-service.patch * harden_auditd.service.patch - Remove patches (fixed by version update): * libaudit-fix-unhandled-ECONNREFUSED-from-getpwnam-25.patch * audisp-remote-fix-hang-with-disk_low_action-suspend-.patch ==== audit-secondary ==== Version update (3.0.6 -> 3.0.9) Subpackages: audit python3-audit system-group-audit - Replace transitional %usrmerged macro with regular version check (boo#1206798) - Enable build for ARM (32-bit) - Update to version 3.0.9: * In auditd, release the async flush lock on stop * Don't allow auditd to log directly into /var/log when log_group is non-zero * Cleanup krb5 memory leaks on error paths * Update auditd.cron to use auditctl --signal * In auparse, if too many fields, realloc array bigger (Paul Wolneykien) * In auparse, special case kernel module name interpretation * If overflow_action is ignore, don't treat as an error (3.0.8) * Add gcc function attributes for access and allocation * Add some more man pages (MIZUTA Takeshi) * In auditd, change the reinitializing of the plugin queue * Fix path normalization in auparse (Sergio Correia) * In libaudit, handle ECONNREFUSED for network uid/gid lookups (Enzo Matsumiya) * In audisp-remote, fix hang with disk_low_action=suspend (Enzo Matsumiya) * Drop ProtectHome from auditd.service as it interferes with rules (3.0.7) * Add support for the OPENAT2 record type (Richard Guy Briggs) * In auditd, close the logging file descriptor when logging is suspended * Update the capabilities lookup table to match 5.16 kernel * Improve interpretation of renamat & faccessat family of syscalls * Update syscall table for the 5.16 kernel * Reduce dependency from initscripts to initscripts-service - Refresh patches (context adjusment): * audit-allow-manual-stop.patch * audit-ausearch-do-not-require-tclass.patch * audit-no-gss.patch * enable-stop-rules.patch * fix-hardened-service.patch * harden_auditd.service.patch - Remove patches (fixed by version update): * libaudit-fix-unhandled-ECONNREFUSED-from-getpwnam-25.patch * audisp-remote-fix-hang-with-disk_low_action-suspend-.patch ==== elfutils ==== Subpackages: elfutils-lang libasm1 libdw1 libelf1 - Fix build with libcurl version 7.88.0 for various deprecated constants. Add patches: * elfutils-0.188-CURLOPT_PROTOCOLS_STR.patch * elfutils-0.188-CURL_AT_LEAST_VERSION.patch * elfutils-0.188-deprecated-CURLINFO.patch - Add support-DW_TAG_unspecified_type.patch that fixes PR30047. ==== elfutils-debuginfod ==== Subpackages: debuginfod-profile libdebuginfod1 - Fix build with libcurl version 7.88.0 for various deprecated constants. Add patches: * elfutils-0.188-CURLOPT_PROTOCOLS_STR.patch * elfutils-0.188-CURL_AT_LEAST_VERSION.patch * elfutils-0.188-deprecated-CURLINFO.patch - Add support-DW_TAG_unspecified_type.patch that fixes PR30047. ==== freeipmi ==== Version update (1.6.9 -> 1.6.10) Subpackages: libfreeipmi17 libipmiconsole2 libipmidetect0 - freeipmi 1.6.10 * Support IPv6 Lan configuration in ipmi-config IPv6 configuration is supported in the new Lan6_Conf section - add upstream signing key and source signature ==== fuse3 ==== Version update (3.13.1 -> 3.14.0) Subpackages: libfuse3-3 - Update to release 3.14 * Split config.h into private and public config - Delete 0001-Split-config.h-into-private-and-public-config.patch (merged). ==== permissions ==== Version update (1599_20221220 -> 1599_20230217) Subpackages: chkstat permissions-config - Update to version 20230217: * shadow: newgidmap,newuidmap: use capabilities (bsc#1208309) * profiles: whitelist kismet capabilities (bsc#1200954) (#171) ==== psmisc ==== Subpackages: psmisc-lang - allow to switch off Apparmor support via bcond ==== python-kiwi ==== Version update (9.24.55 -> 9.24.57) - Bump version: 9.24.56 â 9.24.57 - Allow squashfscompression for plain squashfs The schematron rule to limit the squashfscompression attribute to certain image types did not allow it for a plain squashfs filesystem build. This commit fixes that limitation. This Fixes #2241 - Use rsync defaults to sync the initrd root-tree This commits makes use of rsync default options to sync the root-tree of the boot image for custom initrds. Fixes bsc#1207128 where it was noted hardlinks were not preserved inside the initrd. Signed-off-by: David Cassany <dcassany(a)suse.com> - Fixed wrong test assertions Former versions of pytest did ignore invalid assertions. Now they are reported as an error and show the mistakes of the past - Added 90-brd.conf for test-image-disk-ramdisk By default the brd ramdisk module is no longer added to the initrd. For ramdisk deployments this is required though. This Fixes #2230 - Delete CentOS v7 build tests CentOS v7 is EOL for kiwi image build tests - Allow to specify fixed size for the root partition So far the last partition (typically root) in the partition table takes all the rest space of the partition table in the image file. At deployment/boot time users had several options to let that partition grow to a custom size. However, during build time of the image it was not possible to specify a specific fixed size for the root partition as we don't wanted to produce gaps of unpartitioned space in the image file. It has turned out that there is hardware available which requires a partition to be an exact multiple of some blocksize. As kiwi supports size constraints for all other partitions but not for root this commit now allows for it. The oem-systemsize element is now also taken into account at build time of the image if the oem-resize which would do that at deployment/boot time is switched off like the following example shows: ```xml <oemconfig>  <oem-systemsize>2048</oem-systemsize> <oem-resize>false</oem-resize> </oemconfig> ``` This Fixes #2203 - Delete ppc:fedora from testing report - Remove Fedora PPC build test from index The integration test unfortunately never got tested anywhere is outdated and I have no PPC hardware here to run any tests. Let's add a real test if there is demand for it - Added kiwi-settings for Fedora arm build tests - Allow fat16/fat32 as filesystem in partitions The partitions element allows to specify the filesystem for the individual partition. In the schema fat16 and fat32 were missing - Stick with tox v3.28.0 for unit testing tox >= 3.0.15 together with virtualenv >= 20.17.1 raises strange incompatibilities and prevents the unit test run because tox calls virtualenv in a wrong way leading to strange error messages like: - -- usage: virtualenv ... virtualenv: error: argument dest: destination '{check,devel,packagedoc,doc,doc_gh_pages,doc_suse,doc_man,scripts,}: /home/runner/work/kiwi/kiwi/.tox/3\n/home/runner/work/kiwi/kiwi/.tox/3.8' must not contain the path separator (:) as this would break the activation scripts - -- All this doesn't make sense to me at all and worked without any issues before. - Bump version: 9.24.55 â 9.24.56 - Fix gh-pages publish ==== python-reportlab ==== - pick the primary interpreter for doc generation even if it is not "python3" ==== python-zope.event ==== Version update (4.5.0 -> 4.6) - update to 4.6: * Port documentation to Python 3. * Add support for Python 3.10, 3.11. ==== python310-pyparsing ==== - do primary/all split only for tumbleweed (similar to flit-core) ==== shadow ==== Subpackages: libsubid4 login_defs - Update shadow-fix-print-login-timeout.patch - Reorder source files and patches - Remove scripts that claim to be config but are in /usr (boo#1191578) * userdel-script.patch * useradd-script.patch * useradd.local * userdel-post.local * userdel-pre.local ==== tree ==== Version update (2.0.4 -> 2.1.0) - tree 2.1.0: * Add support for --info and --gitignore for the --fromfile option. (Suggested by Piotr Andruszkow) * Add options --infofile and --gitfile to load .info and .gitignore files explicitly. Each implies --info or --gitignore respectively. * Add NULL guard for json_printinfo() and xml_printinfo() (and fix ftype printing for XML) (Kenta Arai) * Fix getcharset() to not return a getenv() pointer (fix for ENV34-C issue.) (Kenta Arai) * Another attempt at fixing extraneous /'s in HTML URLs/output. (Sebastian Rose) * Fixed XML output (Dave Rice) * Remove the (very outdated) French version of the manpage. Look to localization projects such as Debian's 'manpages-l10n' for localized translations. (hmartink) * Add support for the NO_COLOR environment variable (https://no-color.org/) Equivalent to the -n option (can be still be overridden with -C). (Timm Fitschen) * Removed many C99isms to enable compiling on C90 compilers with fewer warnings. (Sith Wijesinghe and Matthew Sessions) It should not be necessary to avoid using a standard that is old enough to drink, furthermore it is all but impossible to remove the remaining warnings and have modern features like compound literals. In the meantime I've added - std=c11 to the default CFLAGS for Linux and will likely not worry about C90 compatibility going forward unless there is some other reason for it. * Added a helper function for long command line arguments to clean up option processing (and fixes the processing for a few of the options such as - -timefmt= (Ð½Ð°Ð±?).) * Added --hintro and --houtro options to select files to use as the HTML intro and outro. Use /dev/null or an empty file to eliminate them entirely. This should make it much easier to create your own custom CSS or embed one or more trees into a web page. * Defer printing the version until the character set is known so we can use the linedraw copyright symbol. * Revert change to the error code to not return an error (code 2) when attempting to list a non-directory that actually exists. Tree will still return an error when attempting to list a non-existing directory/file. * Added option --fflinks which will process symbolic link information from a file generated with 'tree -if --noreport' when using --fromfile. (Suggested by Chentao Credungtao) * Updated the totals reporting code to also include in the total the file or directory that is being listed. This should make a correct report when doing something like 'tree *'. ==== vim ==== Subpackages: vim-data vim-data-common - Add patch vim-fix-sh-syntax.patch which fixes broken sh syntax. ==== xen ==== Subpackages: xen-libs xen-tools xen-tools-domU - bsc#1208286 - VUL-0: CVE-2022-27672: xen: Cross-Thread Return Address Predictions (XSA-426) 63ebca9c-x86-spec-ctrl-Mitigate-Cross-Thread-Return-Address-Predictions.patch

1 0

obs-build standalone dist auto detection broken with Leap 15.3+
by Mihai Moldovan 20 Feb '23

20 Feb '23

Hi I'm probably one of three users worldwide that use obs-build as a standalone solution and out of these three the only one that is actually using the distribution auto-detection feature.[0] I'll have to give a bit context for that. If you use obs-build standalone (i.e., without any obs-server integration) and do not pass the --dist parameter, it will try to auto-detect the distribution in expanddeps[1] using some magic in Build.pm[2] by inspecting the DISTRIBUTION RPM tag of the "rpm" package (yes, literally the binary "rpm" package that is falling out of the "rpm" source package). This makes sense, since the "rpm" package is a prime-time member of any distribution release and we know that it will always be there (unless SUSE decides to switch to a different low-level package manager). This method has been working fine for decades. I've had to tune the code slightly in 2016 to get Leap support[3], but generally it has been smooth sailing. Starting with Leap 15.3 (and partially the testing version of Leap 15.2, which was used as a testing ground for Leap 15.3), which copies binaries directly from SLE, this method now breaks: $ rpm -q --queryformat '%{NAME}-%{VERSION}-%{RELEASE}: %{DISTRIBUTION}\n' *.rpm rpm-4.14.1-29.46 [Leap 15.4]: SUSE Linux Enterprise 15 rpm-4.14.1-lp152.17.5 [Leap 15.2]: openSUSE Leap 15.2 rpm-4.14.3-150300.46.1 [Leap 15.3]: SUSE Linux Enterprise 15 (I manually amended the nvr output with the repository I fetched the package from for this post.) "SUSE Linux Enterprise 15" will be automatically mapped to sles15sp2 or sles15 depending on rpm's dependency upon libgcrypt - neither of which is suitable to detect Leap versions and it certainly wouldn't detect Leap 15.3 or 15.4 in any case. The other issue is that, if rpm was really copied from SLE 15 SP2 verbatim[4], the distribution RPM tag used in SLE is omitting any service pack information, so it's impossible to determine the actual operating system version based on that. Hacks, such as looking at the dependencies and figuring out what service pack it's coming from via newly introduced dependencies only work the first time around, i.e., to distinguish between sle15 and sle15sp2, but not between, e.g., sle15 and sle15sp1 or sle15sp2 and sle15sp3. Fixing these two issues is really easy, but requires the introduction of two new policies: 1.) Always rebuild the "rpm" package for Leap - don't just copy it from SLE. While I understand that rebuilds are costly, especially if the sources and dependencies are unchanged, I'm only asking to make an exception for the core package that will be used in auto-detection - "rpm". All other packages can happily be copied from SLE. 2.) For SLE itself, the distribution RPM tag should also include service pack information, and the "rpm" package likewise always be rebuild for any new service pack release - no matter whether the source or direct dependencies actually changed. Is this something that could be done? It's too late for Leap 15.3 now (and by extension sle15sp3), since it's already EOL, but it's not too late to fix Leap 15.4 and higher (also sle15sp4+). Best regards, Mihai [0] The numbers are completely made up, but sound believable. [1] https://github.com/openSUSE/obs-build/blob/eaf56f9af8e4bf4c4cf61560ce245403… [2] https://github.com/openSUSE/obs-build/blob/eaf56f9af8e4bf4c4cf61560ce245403… [3] https://github.com/openSUSE/obs-build/commit/66328f9e93716fb2c24eeebe5057a4… [4] I haven't downloaded the actual SLE media to cross-check this assumption, but I bet that the distribution tag would be the same for the rpm package on the actual SLE installation media/repository.

3 4

New Tumbleweed snapshot 20230218 released!
by Dominique Leuenberger 20 Feb '23

20 Feb '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: ruby (3.1 -> 3.2) ruby-common === Details === ==== ruby ==== Version update (3.1 -> 3.2) - switch the default ruby to 3.2 ==== ruby-common ==== - do not rely on file dependencies for getopt

1 0

kjournald - package not find at Tumbleweed Repos
by Ulf 19 Feb '23

19 Feb '23

Hi, I read an interesting news about kjournald which should nicely show the journald entries and makes it easy especially for newcomers to analyze errors. Only available in German: https://linuxnews.de/2023/02/17/kjournald-journal-grafisch-aufbereitet/ Is it possible to integrate it in tumbleweed main repo? https://github.com/KDE/kjournald Can't find it via Discover in my repos, as well not on flathub or opi. $ opi kjournald No package found. Ulf

2 2