November 2022 - openSUSE Factory - openSUSE Mailing Lists

journalctl --list-boots do not show the correct _BOOT_ID (Bengt Gördén)
by Fritz Hudnut 01 Dec '22

01 Dec '22

> ---------- Forwarded message ---------- > From: "Bengt Gördén" <bengan(a)bag.org> > To: factory(a)lists.opensuse.org > Cc: > Bcc: > Date: Mon, 28 Nov 2022 15:34:44 +0100 > Subject: journalctl --list-boots do not show the correct _BOOT_ID > I've got a problem with crashing computer since a couple of weeks and needs to > check logs. journalctl --list-boots doesn't show the right _BOOT_ID. Is this a > known problem? I couldn't find anything in bugzilla. > > time is UTC+1 > @Bengt: I just ran that command in my Leap 15.5 install that is a month or more old and got one entry, because I have been lately booting from the Super Grub2 disk to get into it. Previously I log into each of my installs once a week, so there should have been more entries. # journalctl --list-boots 0 f5339494adda41508d8cf2f7536ba6dd Mon 2022-11-28 08:13:14 PST—Mon 2022-11-28> After a recent zypper in Leap 15.5 a problem with the GUI freezing developed and I filed a bug report on that one . . . so far no crashes. What might be more relevant is that week or so back I ran a zypper in my TW install which had a "grub2" package and letting that go through it seemed to break my grub menu, removing the 7 other distros I had up until then AND it seemed to change the UUID numbers of the non-TW installs (which may relate to your issue?). At that point only TW was showing up to boot, I tried to #update-bootloader but that then removed all of the menu entries. Have another bug report filed on that one. https://bugzilla.suse.com/show_bug.cgi?id=1205772

4 4

openSUSE Release Engineering meeting 30.11.2022
by Lubos Kocman 30 Nov '22

30 Nov '22

All meeting minutes can be found here: https://etherpad.opensuse.org/p/ReleaseEngineering-meeting Meeting is hosted here https://meet.opensuse.org/ReleaseEngineeringMeeting ## Attendees rbrown, DimStar, lkocman, guillaumeg, DocB, ddemaio, dirk, maxlin ## Leap https://etherpad.opensuse.org/p/ReleaseEngineering-openh264-call-20221117 We'll have an update early next week according to Cisco. Code submission deadline for any SLES 15 SP5 related features (does not apply for 15SP4:Update etc), as well as Leap 15.5 Beta code-drop deadline is on January 25th 2023. 15.5 Feature tracking at https://code.opensuse.org/leap/features/issues Ongoing: SUSE Open Source policy review, SUSE Empoyees can participate https://opensource.suse.com/suse-open-source-policy (public facing url) I'd be happy for any feedback from community in form of e.g. email, since the github project SUSE/open-source-policy is private and limited to SUSE Employees as issues might contain discussion regarding confidential topics. Leap Micro 5.4 initial setup in place ## openSUSE Tumbleweed openSUSE:Factory build fail stats: 114 failed 14 unresolvable (last week: 136 / 5) https://tinyurl.com/ysy4nnnz * Still daily snapshots (1124 had no announcement mail, but the snapshot did go out; there was apparently an issue on o3 when it was supposed to prepare the changelog file for that snapshot) * KDE Plasma 5.26.4 staged * Systemd 252.2 (Snapshot 1129) * Staging:G YaST is broken with new rubygem-rspec-* - https://bugzilla.opensuse.org/show_bug.cgi?id=1204871 * Staging:N: experiments with openssl-3 as default: main blocked are nodejs1[89], openssh and ibmtss * util-linux package layout changes remains a topic to be worked out. x86-64-v2 * openSUSE:Factory:LegacyX86 is setup and builds are in a similar state as openSUSE:Factory (slightly worse, would be the same if all pre- existing binaries in oS:F would be deleted and a full rebuild triggered) * Some bots are already up and running: ttm, pkglistgen, trigger- rebuild for rebuild=local * pkglistgen seems to have some trouble, busy debugging that one * once pkglistgen is settled, ttm config will be next, after that we can start the QA setup (possibly we need some more adjustments, as the DVDs are called the same, we have to be careful not to overwrite assets between groups) Only Jiri Slaby volunteered to maintain LegacyX86 so far; he mostly cares for x86-64-v1 in LegacyX86; x86-32 has no explicit volunteers (so it might just be tagging along, similar to what it did so far in openSUSE:Factory, where only few extra cycles are explicit to i586) lkocman: What's our recommendation to devel projects? I guess they should not all mass-enable the legacy target right? dimstar: agreed: Devel Projects are supposed to target Factory - i.e. x86-64-v2; just like most of them don't enable all the other ports ## Richard (MicroOS) openqa.opensuse.org now tests primarily on x86-64-v2/v3 now. New machine definitions will be reintroduced for v0/v1 testing as part of the legacy port. Desktop-GNOME: The Road to Release: transactional-update-notifier is once again WIP after great feedback about why the current approach wasn't the best idea from a security standpoint Bugs fixed Bug 1205108 New: Redundant program for system monitoring on Gnome libcontainers-common/podman was altered to 'better handle' when /home isn't the same filesystem type as the base OS (eg. XFS /home, btrfs /). Unfortunately the first version of this 'fix' caused excessive warnings on every system that was previously working. This is now also resolved. Bugs still WIP osinfo-db still doesn't recognise MicroOS as a seperate distribution - debates with upstream ongoing General MicroOS Stuff in Staging: podman 4.3.1 - broken, maintainer informed https://openqa.opensuse.org/tests/2912733#step/podman/83 Considering FDE by default now single-password-entry full disk encryption is in Tumbleweed Trying to decide if it's a better approach than a fully vertified boot/OS variant of MicroOS, which wouldn't use encryption, but would then encrypt user/system data (eg /home, /var, etc) Please join the Telegram/Matrix group and give your opinion. lkocman: Should we perhaps request addition of FDE devices by gnome- boxes/virt-manager by default? rbrown: the current working theory would be to go LUKS2 based with a nullcipher image, with the user then adding keys/passphrases on first boot. Such an approach would all but eliminate all use of YaST, so, yeah, we'd be making new images, and gnome-boxes/virt-manager/osinfo-db would need to learn how to handle that style of image..but see previous struggles with osinfo-db so far :) KDE MicroOS Desktop is still suffering from a significant lack of contribution. Please join the Telegram/Matrix group and dive in with helping. ## Max 15.5 * lua54 was whitelisted in rpmlint-backports, waiting for package maintainer's ack * The Backports build fail is increased because of 1)newer X/Mesa, and 2)a half of KDE Frameworks got merged to SLE15 SP5, but other KDE Frameworks/Apps are still pending for Backports * The pending KDE update needs some work on permissions/polkit-default- privs, before that the KDE can be broken in the new build * Look into libsnmp30 as an orphaned package issue, looks like some package still depend on libsnmp30 but we have had libsnmp40. The internal package needs a rebuild under my radar: sane-backends Build stats(x86_64): 49 build fails, 4 unresolvables(last week: 24 build fails, 2 unresolvables) ## Guillaume - Arm Tumbleweed: * Rolling * appx WSL image now builds in Factory:ARM (tested manually on a Windows-on-Arm machine). This can be uploaded as part of some "preview" program as a 1st step. * 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 Leap: * appx WSL images (Leap 15.4 and 15.5) work ALP: * SUSE:ALP: - Still waiting for new images to add back aarch64 to openQA ## Sarah - s390 Not availalbe Dimstar: Fails on QA as fonts are unreadable in the installer. (https://bugzilla.opensuse.org/show_bug.cgi?id=1205585) Tumbleweed * No readable fonts: https://bugzilla.opensuse.org/show_bug.cgi?id=1205585 -> It can be, that it is a Mesa bug. * git tests have broken the build for git on s390x, but there is no error output. It is working on Fedora (upstream hint): https://bugzilla.opensuse.org/show_bug.cgi?id=1204762 / https://lore.kernel.org/git/CAN0heSoc+jKxseyyR-=8+ATc8rdY5UyFWZPepaQsGn9m+H… -> Workaround of disabling tests is giving a succeeded result and upstream discussion in progress Leap: * openQA tests have been failing because log files were not uploaded. okurz has created a PR for it at the end of last week: https://progress.opensuse.org/issues/119713, which works only with a single running test * problem exists continuously and is also transferred to openSUSE Tumbleweed: https://progress.opensuse.org/issues/120405 ## Doug * FOSDEM * Bus has 15 sign ups * Contact ddemaio if you're in Nuremberg and want to take the bus to FOSDEM. Space may be limited. * Beer labels arrived * openSUSE - https://paste.opensuse.org/74291193 * OBS - https://paste.opensuse.org/17123615 * Picked up demo machine and will install MicroOS for FOSDEM Booth * waiting on booths annoucedment * Should we consider ALP text-only installations as well? If yuu it on a RP3, I hae a little case with screen that could work * openSUSE on Volla advancing * TW microarchitecture generating interest/news coverage * Will not sponsor FOSS Backstage * oSC23 * Registration open * Waiting on contract for signature * Will annouce CfP next week. goes until April 9. * May 26 - 28 ## Dirk * Won maintainership of SUSE:ALP:RISCV - currently in bootstrap * Working on bisecting qemu/libseccomp/kernel-obs-build tests failure on Step:15-SP4/SP5 so that armv7l builds are published again https://bugzilla.suse.com/show_bug.cgi?id=1205624 ## Wolfgang (Package Hub), Scott Bahling Not available 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)) 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… Need to setup Leap Micro 5.3 (don't have time this week) * Pending Leap Micro 5.3 maint-setup ffmpeg - 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. 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. ## Adrian - OBS No update, OBS is broken at the moment. Axel: there were some cleaning activities in OBS, to determine inactive users and related unmaintained projects. Is there anything going on? Adrian: the script checks a project or a package that has no changes for more than one year. It will create a delete request, that can be deleted. If there is no reaction there will be auto-acceptance in few days. Package can be always manually submitted back if the DR was missed. Users will not be deactivated. Adrian: User cleanup would have to be discussed with IDP team (SUSE IT). OBS is just a consumer. Lubos will create a request to suggest this action in Service desk. Adrian: if the user never logged in into OBS, that's probably a cleanup that could stay in touch. ## Open Floor some members might not be able to join due to conflict with ALP OpenFloor meeting. We might want to give them heads up to provide information in etherpad before the meeting starts

4 3

New Tumbleweed snapshot 20221129 released!
by Dominique Leuenberger 30 Nov '22

30 Nov '22

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: kdesu libiscsi (1.19.0+git.20220303 -> 1.19.0+git.20221112) libreoffice (7.4.2.3 -> 7.4.3.2) libva libva-gl python-pycairo (1.21.0 -> 1.22.0) systemd (252.1 -> 252.2) virt-manager === Details === ==== kdesu ==== Subpackages: libKF5Su5 libKF5Su5-lang - Drop fpie.patch, works as expected without - Drop setgid bit on kdesud, no longer needed since 5.99.0 ==== libiscsi ==== Version update (1.19.0+git.20220303 -> 1.19.0+git.20221112) - Update to version 1.19.0+git.20221112: * ci/build.sh: Enable parallel compilation * ci: Fix the Appveyor Linux and Windows builds * ci: Add ci/install.bat * Add CodeQL workflow for GitHub code scanning * test-tool: remove a redundant semicolon * lib/scsi-lowlevel: Make the REPORT LUNS unmarshalling code more flexible * Fix segmentation fault problem. * Check return value of scsi_malloc in order to avoid dereferencing NULL return value. * fix iscsi-ls parameter parse * iscsi-swp: handle setting of debug_level correctly * Update iscsi-dd.c * iscsi-inq: handle setting of debug_level correctly * Retain the immediate data param during login processing ==== libreoffice ==== Version update (7.4.2.3 -> 7.4.3.2) Subpackages: libreoffice-base libreoffice-calc libreoffice-draw libreoffice-filters-optional libreoffice-gnome libreoffice-gtk3 libreoffice-icon-themes libreoffice-impress libreoffice-l10n-cs libreoffice-l10n-da libreoffice-l10n-de libreoffice-l10n-el libreoffice-l10n-en libreoffice-l10n-en_GB libreoffice-l10n-es libreoffice-l10n-fr libreoffice-l10n-hu libreoffice-l10n-it libreoffice-l10n-ja libreoffice-l10n-pl libreoffice-l10n-pt_BR libreoffice-l10n-ru libreoffice-l10n-zh_CN libreoffice-l10n-zh_TW libreoffice-mailmerge libreoffice-math libreoffice-pyuno libreoffice-qt5 libreoffice-writer libreofficekit - Update to 7.4.3.2: https://wiki.documentfoundation.org/Releases/7.4.3/RC2 https://wiki.documentfoundation.org/Releases/7.4.3/RC1 - Updated bundled dependencies: * curl-7.83.1.tar.xz -> curl-7.86.0.tar.xz - Added patches: * fix_harfbuzz_on_sle12_sp5.patch * fix_webp_on_sle12_sp5.patch - Refresh fix_gtk_popover_on_3.20.patch - Removed upstreamed patches: * bsc1202866.patch * bsc1201095.patch - Fix bsc#1202866 - LO-L3: PPTX: indentation of list items far too far to the left (overruns bullet items) * bsc1202866.patch ==== libva ==== Subpackages: libva-drm2 libva-x11-2 libva2 - Make sure make runs with verbose builds so we see the gcc cmdlines - Added propagate-dpy.patch: (boo#1202828) Patch taken from https://github.com/intel/libva/issues/479 ==== libva-gl ==== Subpackages: libva-glx2 libva-wayland2 - Make sure make runs with verbose builds so we see the gcc cmdlines - Added propagate-dpy.patch: (boo#1202828) Patch taken from https://github.com/intel/libva/issues/479 ==== python-pycairo ==== Version update (1.21.0 -> 1.22.0) - Updtae to version 1.22.0: * Officially support Python 3.11. * PDFSurface.version_to_string(): Fix crash with negative versions. * typing: ImageSurface.get_stride() returns an int. * typing: Fix incorrect interface for Matrix constructor. * typing: Use Generic for Context. * docs: some cairo.Context fixes. * docs: try to make create_from_png/write_to_png more clear. * docs: add an example for how to convert a surface to pillow. * docs: cairo.Format.RGB24: document that unused bytes may be overwritten. * tests: donât depend on specific ref counts. * tests: compatibility fixes for cairo 1.17.6. - Drop f5a795ea.patch: fixed upstream. ==== systemd ==== Version update (252.1 -> 252.2) Subpackages: libsystemd0 libsystemd0-32bit libudev1 libudev1-32bit systemd-32bit systemd-container systemd-devel systemd-lang udev - Import commit e7e931b07edd786dc6ca1dae6c23ff7b785f8efd (merge of v252.2) For a complete list of changes, visit: https://github.com/openSUSE/systemd/compare/64dc546913525e33e734500055a62ed… - Rebase 6000-Revert-tmpfiles-whenever-creating-an-inode-immediate.patch ==== virt-manager ==== Subpackages: virt-install virt-manager-common - bsc#1205675 - [Build 20221122] virt-install: Specifying --boot no longer implies no_install=yes 1cb0be40-virtinstall-split-no_install-conditional-apart-to-track-code-coverage.patch e94786c0-virtinstall-fix-regression-with-boot-and-no-install-method.patch

1 0

tcp mss clamping or ... ?
by L A Walsh 29 Nov '22

29 Nov '22

I use a 9k mtu on my 10gb network @ home -- only exists between my desktop & my server where it can be worthwhile. Bridged to that NW is a 1gb, 1.5k mtu network use for my home IOT (Internet of Things) This works for administrative traffic, for the most part, but in gaining some new 'things', some wish to talk to a media/file server on the higher BW net. Someone referred me to possibly using tcp mss clamping, though they were using it in the context of a VPN tunnel which I'm not using. I'm wondering if it is as simple as installing routes with mtu clamping so hosts wanting(needing) to goto a smaller mtu would take the appropriate network and talk with smaller packets. Seems there maybe something missing there since some traffic can be ip-level w/no tcp in play (ex: dns). Doesn't seem that would really work too well... Has anyone had any experience w/this type of setup? tnx!

4 7

Troubles with sudo - and the fix for it
by Dominique Leuenberger / DimStar 29 Nov '22

29 Nov '22

Dear Tumbleweed users, At a perfectlty bad moment, a snapshot with a configuration change for sudo went out and me not being around on the weekend made this problem even worse for you. Background situation: a user requested the sudo configuration to be changed to no longer ask for the 'target user's password', but rather ask for the user willing to become somebody else's password (as other distros do) That change was submitted to Factory and was unfortunately not identified as being really bad for our existing users. So it went out in snapshot 1103 (published Friday evening) Over the weekend, many of you have struggled with this new default. Understandably so. As the change did not take into account ANY user that never had the need to change the sudo config, because it just worked for them. As this change is definitively bad in its current form I have reverted the sudo package to the state it was before snapshot 1103 and published the same version into the openSUSE Tumbleweed update channel. If you get the sudo version from there, your configuration shold start working again without further changes (if you did not change the config since then! Otherwise rpm will create an .rpmnew file and NOT replace your local modied version) Apologies at this place for the trouble caused to you. Of course I will also request openQA to also test the DEFAULT configuration provided - allowing us to spot such issues hopefully before sending them out to users ever again. Thank you very much for your understanding! Let's get this back on track and let's keep having a lot of fun Best regards, Dominique

26 60

New Tumbleweed snapshot 20221128 released!
by Dominique Leuenberger 29 Nov '22

29 Nov '22

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: plymouth skype4pidgin (1.5 -> 1.7) snapper === Details === ==== plymouth ==== Subpackages: libply-splash-core5 libply-splash-graphics5 libply5 plymouth-dracut plymouth-lang plymouth-plugin-label plymouth-plugin-two-step plymouth-scripts plymouth-theme-bgrt plymouth-theme-spinner ==== skype4pidgin ==== Version update (1.5 -> 1.7) Subpackages: libpurple-plugin-skypeweb pidgin-plugin-skypeweb - Update to version 1.7 (changes since 1.5): * Fix "alt login" giving a 40499 error. * Fix file transfers. * Fix losing admin rights when joining a room. * Fix the Aug 2020 issues with "Failed to get Magic T" errors. Use the "Use alternate auth method" setting in the Advanced tab is always preferred as it's less prone to web-scraping issues. * Fix some issues that some users were experiencing with buddies not appearing as online. * Fix some static analysis warnings (memory leaks, security issues). ==== snapper ==== Subpackages: libsnapper6 snapper-zypp-plugin - fix build with boost 1.81

1 0

openSUSE:Factory - Build fail notification
by DimStar / Dominique Leuenberger 28 Nov '22

28 Nov '22

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. - rubygem-slim: Uninstallable: nothing provides rubygem(ruby:3.1.0:temple) < 0.9 needed by ruby3.1-rubygem-slim-4.1.0.i586 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

Update from 20220908 to 20221101 Breaks SMB
by Joe Salmeri 28 Nov '22

28 Nov '22

Today I updated from TW 20220908 to 20221101 and SMB no longer works I use SMB to access my linux server from both Windows and Linux guest network machines. This configuration has worked fine for years with no issues. Today after updating to TW 20221101 neither the Windows or Linux guests can access the network shares. Samba is running and on the Windows machine when I map to one of the shares it maps the drive but then when i try to access the mapped drive it gets Access Denied. There have been no configuration changes to the system for SMB in years It is not a permission issue on the drive because the user that maps to the SMB share on the Linux machine has full permissions rwx on Linux and Full Control on Linux. I believe the problem is related to apparmour changes for samba but I am unsure how to resolve the issue. Here are the messages that are appearing for the smb service. Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + test No == Yes Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + test -e /etc/apparmor.d/local/usr.sbin.smbd-shares Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + grep -q 'update-apparmor-samba-profile 1.3' /etc/apparmor.d/local/usr.sbin.smbd-shares Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + test /etc/samba/smb.conf -nt /etc/apparmor.d/local/usr.sbin.smbd-shares Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + silentexit 'smb.conf is older than the AppArmor profile sniplet' Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + exit 0 Nov 03 19:59:44 smbd[9988]: [2022/11/03 19:59:44.703896, 0] ../../source3/smbd/server.c:1741(main) Nov 03 19:59:44 smbd[9988]: smbd version 4.17.2-git.273.a55a83528b9SUSE-oS15.9-x86_64 started. Nov 03 19:59:44 smbd[9988]: Copyright Andrew Tridgell and the Samba Team 1992-2022 I suspect that the problem it is because it is complaining about smb.conf being different than what apparmour has but that config has not been changed since I originally set it up. Note that I first updated one of the client machines from TW 20220908 to 20221101 and after that machine was updated both the Windows machine and that TW 20221101 client had no problem accessing the TW 20220908 Linux server and SMB shares. Once the TW 20220908 server was updated to 22021101 then the linux clients and windows cllients could no longer access the TW 20221101 server. Is this a known issue? What are my options? I'd prefer to not have to rollback the machines but I also need a working SMB environment.

4 16

journalctl --list-boots do not show the correct _BOOT_ID
by Bengt Gördén 28 Nov '22

28 Nov '22

I've got a problem with crashing computer since a couple of weeks and needs to check logs. journalctl --list-boots doesn't show the right _BOOT_ID. Is this a known problem? I couldn't find anything in bugzilla. time is UTC+1 > linux-jrxm:~ # grep -e ^NAME -e ^VERSION_ID /etc/os-release > NAME="openSUSE Tumbleweed" > VERSION_ID="20221123" > linux-jrxm:~ # journalctl --list-boots > IDX BOOT ID FIRST ENTRY LAST ENTRY > -19 f1954a84587545feae999e9f37de5bcb Sat 2021-11-27 12:15:28 CET Sun 2021-11-28 20:34:16 CET > -18 aea5b20091a544e28be4b9ac7fa1208c Sun 2021-11-28 21:35:00 CET Tue 2021-12-21 17:14:34 CET > -17 e3b041d425db47b0a9e5475a4377f7f1 Tue 2021-12-21 18:24:06 CET Fri 2022-01-14 16:03:29 CET > -16 0439e448302f42b1b9190c06959dd8fe Fri 2022-01-14 17:22:07 CET Sat 2022-01-15 09:52:50 CET > -15 ca0f88cb3c4e4ac495292c26311f5811 Sat 2022-01-15 11:01:34 CET Wed 2022-02-02 09:53:03 CET > -14 dc5ed27de618455bbefabe80fdd6a885 Wed 2022-02-02 10:53:42 CET Wed 2022-02-02 11:17:47 CET > -13 ad59def20fa3498a9e451118bad0f802 Wed 2022-02-02 12:18:11 CET Wed 2022-02-09 23:20:30 CET > -12 a7f3ad89a1a74cf884d71d395612ef2d Thu 2022-02-10 08:53:30 CET Fri 2022-02-11 17:38:53 CET > -11 43b1403ac60d4d9884890cf25862607a Fri 2022-02-11 18:39:16 CET Tue 2022-02-15 15:02:39 CET > -10 38b6c17bcf404fb1be2e919bc6cef431 Tue 2022-02-15 16:06:20 CET Tue 2022-02-15 15:12:26 CET > -9 85748804c57a455fbda0761a303ed3d8 Tue 2022-02-15 16:12:48 CET Tue 2022-02-15 15:23:07 CET > -8 c627d843f74f4bbea07e8f6aa1a44786 Tue 2022-02-15 16:23:33 CET Tue 2022-02-15 19:19:38 CET > -7 c11187ba74f742e68da3c4f14bf0195b Tue 2022-02-15 20:20:48 CET Tue 2022-02-15 21:20:51 CET > -6 009204e8f5a0423499ed7580f248abab Tue 2022-02-15 22:21:19 CET Mon 2022-02-21 21:21:47 CET > -5 f66e2b3bd7e14399ab342071f2ce92f5 Mon 2022-02-21 21:27:36 CET Mon 2022-02-28 19:35:43 CET > -4 aded82346d404722bf310cd9c658db55 Mon 2022-02-28 20:36:15 CET Tue 2022-03-01 13:23:29 CET > -3 875cd66b3c0d422dbb4492befec0b344 Tue 2022-03-01 13:36:09 CET Tue 2022-03-08 09:58:42 CET > -2 14102c1313d14dc1abdfb54851273930 Tue 2022-03-08 11:22:13 CET Tue 2022-03-08 15:43:00 CET > -1 f35f23ff931444598fcee679503eff6d Tue 2022-03-08 16:36:41 CET Tue 2022-03-08 17:05:32 CET > 0 5b5506b8fd844ecb9175d7eb5f801bcc Tue 2022-03-08 17:31:51 CET Tue 2022-03-08 16:31:55 CET Two latest boots > linux-jrxm:~ # journalctl --since "Nov 28 00:00:00" | grep ^"--" > -- Boot f7d4bd3570294a8c900f1e8b88f9d310 -- > -- Boot 28d96a06f89c407594b6fb50b8af2b7f -- -- /bengan

1 0

New Tumbleweed snapshot 20221127 released!
by Dominique Leuenberger 28 Nov '22

28 Nov '22

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: filesystem gawk (5.2.0 -> 5.2.1) heaptrack (1.3.0 -> 1.4.0) iputils (20211215 -> 20221126) kdump (1.0.2+git20.gcb129d0 -> 1.0.2+git26.gc6fab38) libX11 libeconf (0.4.8+git20221114.7ff7704 -> 0.4.9) libgcrypt (1.9.4 -> 1.10.1) libotr mpfr === Details === ==== filesystem ==== - Add %_user_tmpfilesdir to the filesystem - Added zh_Hans (simplified Chinese) and zh_Hant (traditional chinese) locales ==== gawk ==== Version update (5.2.0 -> 5.2.1) - Update to gawk 5.2.1 * Issues related to the sign of NaN and Inf values on RiscV have been fixed * A few issues with the debugger have been fixed. * More subtle issues with untyped array elements being passed to functions have been fixed. * The rwarray extension's readall() function has had some bugs fixed. * The PMA allocator is now supported on FreeBSD, OpenBSD and Linux on S/390x. - double-free.patch, pma.patch, nan-sign.patch: Removed ==== heaptrack ==== Version update (1.3.0 -> 1.4.0) Subpackages: heaptrack-gui heaptrack-lang - Update to 1.4.0 * Pass client exit code in heaptrack.sh * Leverage non-deprecated mallinfo2 * Add support for the mimalloc allocator * Explicitly encode which hooks are required and which are optional * Make mi_* symbols truly optional by usig weak symbols for them * Prevent malloc from disappearing in inlining example * handle calling heaptrack_stop() without debuginfo * Ensure we don't try to overwrite invalid tables * Make elf_symbol_table a view of const Elf::Sym * Ensure we don't read outside the string table for symbol names * Silence -Wuse-after-free for realloc call ==== iputils ==== Version update (20211215 -> 20221126) - Update to version 20221126 https://github.com/iputils/iputils/releases/tag/20221126 - Update configure variables (ninfod, rarpd and rdisc were removed from upstream in next release => remove -DBUILD_NINFOD=false -DBUILD_RARPD=false - DBUILD_RDISC=false) - Remove 2 backported fixes from this release 0001-ping-Add-SA_RESTART-to-sa_flags.patch 0002-ping-Make-ping_rts-struct-static.patch ==== kdump ==== Version update (1.0.2+git20.gcb129d0 -> 1.0.2+git26.gc6fab38) - Make the kdump-save.service reboot after kdump-save is finished (bsc#1204000) - fix renaming of qeth interfaces (bsc#1204743, bsc#1144337) - ppc64: rebuild initrd image after migration (bsc#1191410) - kdumptool calibrate: modify fadump suggestions (jsc#IBM-1027) ==== libX11 ==== Subpackages: libX11-6 libX11-6-32bit libX11-data libX11-devel libX11-xcb1 - U_Fix-797755-Allow-X-IfEvent-to-reenter-libX11.patch * fixed Firefox freezes (regression since 1.8.2) (boo#1205778) ==== libeconf ==== Version update (0.4.8+git20221114.7ff7704 -> 0.4.9) Subpackages: libeconf0 libeconf0-32bit - Update to version 0.4.9: * libeconf.h: added missing sys/types.h header (#171) * new API calls: econf_readFileWithCallback, econf_readDirsWithCallback, econf_readDirsHistoryWithCallback (#172) * Checking NULL comment parameter in the parsing functions. ==== libgcrypt ==== Version update (1.9.4 -> 1.10.1) Subpackages: libgcrypt20 libgcrypt20-32bit libgcrypt20-hmac - Update to 1.10.1: * Bug fixes: - Fix minor memory leaks in FIPS mode. - Build fixes for MUSL libc. * Other: - More portable integrity check in FIPS mode. - Add X9.62 OIDs to sha256 and sha512 modules. * Add the hardware optimizations config file hwf.deny to the /etc/gcrypt/ directory. This file can be used to globally disable the use of hardware based optimizations. * Remove not needed separate_hmac256_binary hmac256 package - Update to 1.10.0: * New and extended interfaces: - New control codes to check for FIPS 140-3 approved algorithms. - New control code to switch into non-FIPS mode. - New cipher modes SIV and GCM-SIV as specified by RFC-5297. - Extended cipher mode AESWRAP with padding as specified by RFC-5649. - New set of KDF functions. - New KDF modes Argon2 and Balloon. - New functions for combining hashing and signing/verification. * Performance: - Improved support for PowerPC architectures. - Improved ECC performance on zSeries/s390x by using accelerated scalar multiplication. - Many more assembler performance improvements for several architectures. * Bug fixes: - Fix Elgamal encryption for other implementations. [bsc#1190239, CVE-2021-40528] - Check the input length of the point in ECDH. - Fix an abort in gcry_pk_get_param for "Curve25519". * Other features: - The control code GCRYCTL_SET_ENFORCED_FIPS_FLAG is ignored because it is useless with the FIPS 140-3 related changes. - Update of the jitter entropy RNG code. - Simplification of the entropy gatherer when using the getentropy system call. * Interface changes relative to the 1.10.0 release: - GCRYCTL_SET_DECRYPTION_TAG NEW control code. - GCRYCTL_FIPS_SERVICE_INDICATOR_CIPHER NEW control code. - GCRYCTL_FIPS_SERVICE_INDICATOR_KDF NEW control code. - GCRYCTL_NO_FIPS_MODE = 83 NEW control code. - GCRY_CIPHER_MODE_SIV NEW mode. - GCRY_CIPHER_MODE_GCM_SIV NEW mode. - GCRY_CIPHER_EXTENDED NEW flag. - GCRY_SIV_BLOCK_LEN NEW macro. - gcry_cipher_set_decryption_tag NEW macro. - GCRY_KDF_ARGON2 NEW constant. - GCRY_KDF_BALLOON NEW constant. - GCRY_KDF_ARGON2D NEW constant. - GCRY_KDF_ARGON2I NEW constant. - GCRY_KDF_ARGON2ID NEW constant. - gcry_kdf_hd_t NEW type. - gcry_kdf_job_fn_t NEW type. - gcry_kdf_dispatch_job_fn_t NEW type. - gcry_kdf_wait_all_jobs_fn_t NEW type. - struct gcry_kdf_thread_ops NEW struct. - gcry_kdf_open NEW function. - gcry_kdf_compute NEW function. - gcry_kdf_final NEW function. - gcry_kdf_close NEW function. - gcry_pk_hash_sign NEW function. - gcry_pk_hash_verify NEW function. - gcry_pk_random_override_new NEW function. * Rebase libgcrypt-1.8.4-allow_FSM_same_state.patch and rename to libgcrypt-1.10.0-allow_FSM_same_state.patch * Remove unused CAVS tests and related patches: - cavs_driver.pl cavs-test.sh - libgcrypt-1.6.1-fips-cavs.patch - drbg_test.patch * Remove DSA sign/verify patches for the FIPS CAVS test since DSA has been disabled in FIPS mode: - libgcrypt-fipsdrv-enable-algo-for-dsa-sign.patch - libgcrypt-fipsdrv-enable-algo-for-dsa-verify.patch * Rebase libgcrypt-FIPS-SLI-pk.patch * Rebase libgcrypt_indicators_changes.patch and libgcrypt-indicate-shake.patch and merge both into libgcrypt-FIPS-SLI-hash-mac.patch * Rebase libgcrypt-FIPS-kdf-leylength.patch and rename to libgcrypt-FIPS-SLI-kdf-leylength.patch * Rebase libgcrypt-jitterentropy-3.4.0.patch * Rebase libgcrypt-FIPS-rndjent_poll.patch * Rebase libgcrypt-out-of-core-handler.patch and rename to libgcrypt-1.10.0-out-of-core-handler.patch * Since the FIPS .hmac file is now calculated with the internal tool hmac256, only the "module is complete" trigger .fips file is checked. Rename libgcrypt-1.6.1-use-fipscheck.patch to libgcrypt-1.10.0-use-fipscheck.patch * Remove patches fixed upstream: - libgcrypt-1.4.1-rijndael_no_strict_aliasing.patch - libgcrypt-1.5.0-LIBGCRYPT_FORCE_FIPS_MODE-env.diff - libgcrypt-fix-rng.patch - libgcrypt-1.8.3-fips-ctor.patch - libgcrypt-1.8.4-use_xfree.patch - libgcrypt-1.8.4-getrandom.patch - libgcrypt-1.8.4-fips_ctor_skip_integrity_check.patch - libgcrypt-dsa-rfc6979-test-fix.patch - libgcrypt-fix-tests-fipsmode.patch ... changelog too long, skipping 27 lines ... * Update libgcrypt.keyring ==== libotr ==== - Add sys/socket.h to the test suite that FTBFS without the include * Add libotr-4.1.1-include-socket.h.patch ==== mpfr ==== - Add mpfr-4.1.1-patch01.patch to fix bug with code using the mpfr_custom_get_kind macro.

1 0