September 2023 - openSUSE Factory - openSUSE Mailing Lists

SCSI device identification and SCSI symlink generation in sg3_utils 1.48
by Martin Wilck 09 Nov '23

09 Nov '23

With the forthcoming update of sg3_utils to v1.48 (currently in Base:System, to be submitted to Factory soon), SCSI device identification and SCSI symlink generation by udev will change. TL;DR: unreliable device identifiers will not be used by default any more, and /dev/disk/by-id symlinks for such identifiers will not be created by default, either. The policy can be changed by editing the udev rules in 00-scsi-sg3_config.rules. Please file bugs and / or notify me if you have trouble with this new identification scheme. Of course, while this is still in Base:System, we can also discuss the general approach for Factory, and the defaults to be applied. Long version: It is well known that referring to disk devices by their device node (like /dev/sda) is unreliable. In most situations, it is recommended to refer to devices by their content, i.e. using file system UUIDs or labels. Sometimes, however, the devices must be referred to by hardware properties. For this purpose, udev maintains various symlinks under /dev/disk/by-id. This post is specifically about SCSI symlinks, which have the format /dev/disk/by-id/scsi-XYZ. If you don't use dm-multipath, and don't use hardware IDs to refer to any disks or partitions anywhere, you can stop reading here. SCSI devices can be identified in different ways by the contents of SCSI VPD (Vital Product Data) pages. In PVD 83 (device identification), the following identifiers may occur (see SCSI spec SPC-6 §7.7.6 for details): a) NAA registered extended: 36... (+ 31 hex digits) b) NAA registered: 35... (+ 15 hex digits) c) NAA extended: 32... (+ 15 hex digits) d) EUI-64: 2... (+ 16 hex digits) e) SCSI name string: 8... (+ utf-8 string) f) NAA local ("L"): 33... (+ 15 hex digits) g) T10 vendor-ID ("T): 1... (+ string) h) vendor-specific ("V") 0... (+ string) Furthermore, we have i) serial number ("S"): S... (+ vendor/product/serial string) The list above is sorted roughly top-down by the reliability (uniqueness) of these identifiers. The udev rules select the most reliable available identifier from the above list to set the ID_SERIAL udev property, which is used e.g. by dm-multipath to identify SCSI devices which represent different paths to the same physical volume. Furthermore, the udev rules create /dev/disk/by-id/scsi-$ID symlinks for all identifiers from the above list that are defined for a given device. This makes sure that whatever identifier a user has chosen for referring to her disks will be available as symlink under /dev/disk/by-id. However, this has also severe disadvantages. The identifiers f)-i) are not reliable; IOW there can be multiple devices in the same system that use the same identifier, although they don't represent the same physical disk. This applies to i) in particular: Some large storage arrays use the same serial number for all LUNs they expose. Using such identifiers for multipath can cause fatal data corruption. Moreover, the creation of these symlinks during boot can slow down booting a lot, because thousands of devices may be contending for the same symlink. Lastly, not creating useless symlinks will tidy up /dev/disk/by-id and make it easier to read. Therefore sg3_utils 1.48 changes the policy for SCSI device identification. The policy can be customized in the udev rule "00-scsi- sg3_config.rules" (to change the policy, copy this file from /usr/lib/udev/rules.d to /etc/udev/rules.d first). For determining ID_SERIAL, only a)-e) above are tried. If users need to use additional identifiers from the list above, they can set the udev property .SCSI_ID_SERIAL_SRC (leading "." is intentional) to any combination of the capital letters in quotes in the list above. E.g. "ST" would mean to take g) and i) into account. To restore the previous behavior, set ENV{.SCSI_ID_SERIAL_SRC}="LTVS". The current upstream default is "T", so that g) above is still enabled. To disable all "unreliable" IDs, set it to the empty string. If udev encounters a device for which ID_SERIAL can't be assigned, it prints a warning to the journal. Symlink generation is controlled by the variable .SCSI_SYMLINK_SRC. It can also be set to any combination of "LTVS", with the same meaning of the letters as above, and controls which scsi-... symlinks udev will create under /dev/disk/by-id/, *in addition* to the symlink /dev/disk/by-id/scsi-$ID_SERIAL, which will always be created if ID_SERIAL could be determined. Again, to restore the previous behavior of the udev rules, set ENV{.SCSI_SYMLINK_SRC}="LTVS". The default is the empty string. Note 1: The symlink generation applies to both disks and partitions. Partition symlinks have a "-part$P" string appended to the name of the symlink of their parent disk. Note 2: Modern SCSI devices usually support one or more of the "reliable" identifiers a)-e) above. I expect that only very few old devices really need one of f)-i). Inform me if you find counter- examples. Note 3: ATA and USB devices have additional identifiers generated by the transport (/dev/disk/by-id/ata-* and /dev/disk/by-id/usb-*) which are unaffected by this change. These devices often don't expose proper SCSI IDs, but they actually don't need them because the ATA or USB identifiers are unique. Regards, Martin

7 27

Disk auto-unlocking with TPM 2.0
by Gary Lin 10 Oct '23

10 Oct '23

Hi, I'm pleased to introduce a new feature for openSUSE Tumbleweed: disk auto-unlocking with TPM 2.0. In short, it boots the encrypted root without asking for a passphrase. This feature is already integrated into Agama on ALP and we plan to merge it into yast-installation (*1). For now, if you're interested, just type a few commands to enable it. The hard requirements are LUKS2 partition(s), UEFI with Secure Boot enabled, and, of course, TPM 2.0. LUKS2 support in yast-installation is still experimental and needs a few extra steps. You could also choose to convert the existing LUKS1 partition to a LUKS2 one. The LUKS2 setup is addressed in the following link: https://en.opensuse.org/SDB:Encrypted_root_file_system#Setup_LUKS2_partitio… First of all, please update all packages, especially shim and grub2. The key package is fde-tools. Currently, there is a minor issue that the TCTI for native devices may not be installed, and the fix is on the way(*2). So, please install fde-tools along with libtss2-tcti-device0 for the time being. # zypper in fde-tools libtss2-tcti-device0 After installing fde-tools, you can test the TPM 2.0 support with # fdectl tpm-present If there is no error, it's time to seal a new random key for your root partition: # fdectl regenerate-key This command will request the passphrase of the root partition to enroll a new random key, seal the random key with TPM, and then update the grub configuration. Next, reboot your system. If everything is setup correctly, the system will boot without showing the passphrase prompt. One thing to be noted is that after a boot component upgrade, such as shim, grub2, or UEFI firmware, the signature in the sealed key may become invalid, and then you have to run the following command to update the signature. # fdectl tpm-authorize We are still working on a solution to update the signature automatically after shim and grub2 update to reduce such hassles. By default, 'fdectl' only manages the keyslots of the root partition. To extend the keyslot management to other partitions such as swap, please check https://en.opensuse.org/SDB:Encrypted_root_file_system#Additional_steps_for… A complete document is available here: https://en.opensuse.org/SDB:Encrypted_root_file_system#Unattended_boot_with… In case you encounter any issue, feel free to file a bug and assign it to bootloader-maintainers(a)suse.de Cheers, Gary Lin (*1) https://github.com/yast/yast-installation/issues/1088 (*2) https://build.opensuse.org/request/show/1100949

17 32

Leap not more useful for WebServer with php
by Walddys Emmanuel Dorrejo Céspedes 09 Oct '23

09 Oct '23

Leap is stuck with PHP 8.0 version, when most devs and project have move to php8.1/8.2, i was hoping that php8.1 at least this version reach leap 15.5, but didn't reached the main repo. sad.

6 6

Changes to dbus packaging (Some Attention maybe required).
by Simon Lees 04 Oct '23

04 Oct '23

Hi All, For Tumbleweed and ALP we plan to follow Red Hat / Fedora / Debian and move from dbus-daemon to dbus-broker as it has a number of advantages and is what upstream is now focusing on. While one of the goals here is to provide the same user experience there will be a couple of changes that will likely require adjustments in a few packages. 1. tools such as dbus-send and dbus-uuid will no longer be installed by default on all systems (we have many use cases that will simply no longer need them and this follows other distro's). Currently the package dbus-1-tools exists and is required by dbus-1 but that will change maybe to a recommends so if you know your package needs one of these tools you can add the Requires there now, otherwise I plan to go through and look at debian and fedora to try and find any packages that need this requires before it becomes optional for dbus. 2. The symlink from /etc/machine-id to /var/lib/dbus/machine-id will no longer be present on all machines and software should be adapted to use /etc/machine-id from systemd rather then the dbus copy. Again this has already happened for Debian and Fedora so hopefully many upstreams have already adapted to this. I'll outline the plan / timeline below. 1. Currently - dbus-broker has been in the distro for quite some time and the dbus-1 package has already been split up and we are at the point of asking people nicely to start testing (instructions below), myself and at least several other people have already been testing this without issues. 2. In 2-3 weeks if I don't hear of any issues we will update the systemd presets to enable dbus-broker rather then dbus-daemon. 3. Unless someone indicates they really want to keep maintaining dbus-daemon and have good reasons for doing so I will make dbus-daemon uninstallable. 4. Once we have done the work to ensure that as many packages that use dbus-send and other tools require the tools package we will drop the requires for dbus-tools from the dbus package. Instead it will probably move to being a Recommends in one of the patterns so it still ends up on most users machines. Switching to dbus-broker: Run the following as root zypper in dbus-broker systemctl disable dbus systemctl enable dbus-broker systemctl --global disable dbus systemctl --global enable dbus-broker https://www.mail-archive.com/debian-policy@lists.debian.org/msg35437.html https://fedoraproject.org/wiki/Changes/DbusBrokerAsTheDefaultDbusImplementa… -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

4 6

Re: Trial to use a CDN for download.opensuse.org
by Jan Engelhardt 03 Oct '23

03 Oct '23

A slow mirror I could live with, but... an unreachable one ううん. This does not actually look like cdn is really used in this particular instance. # wget http://cdn.opensuse.org/debug/tumbleweed/repo/oss/x86_64/libvmime-debugsour… -c --2023-09-30 17:19:37-- http://cdn.opensuse.org/debug/tumbleweed/repo/oss/x86_64/libvmime-debugsour… Resolving cdn.opensuse.org (cdn.opensuse.org)... 151.101.109.91, 2a04:4e42:1a::347 Connecting to cdn.opensuse.org (cdn.opensuse.org)|151.101.109.91|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirrorcache-jp.opensuse.org/debug/tumbleweed/repo/oss/x86_64/libvmim… [following] --2023-09-30 17:19:37-- http://mirrorcache-jp.opensuse.org/debug/tumbleweed/repo/oss/x86_64/libvmim… Resolving mirrorcache-jp.opensuse.org (mirrorcache-jp.opensuse.org)... 139.162.108.149, 2400:8902::f03c:93ff:fec8:af18 Connecting to mirrorcache-jp.opensuse.org (mirrorcache-jp.opensuse.org)|139.162.108.149|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirror-jp.firstyear.id.au/debug/tumbleweed/repo/oss/x86_64/libvmime-… [following] --2023-09-30 17:19:38-- http://mirror-jp.firstyear.id.au/debug/tumbleweed/repo/oss/x86_64/libvmime-… Resolving mirror-jp.firstyear.id.au (mirror-jp.firstyear.id.au)... 139.162.108.7, 2400:8902::f03c:93ff:fec8:afa1 Connecting to mirror-jp.firstyear.id.au (mirror-jp.firstyear.id.au)|139.162.108.7|:80... ^C 17:20 f3:~ $ ping mirror-jp.firstyear.id.au PING mirror-jp.firstyear.id.au (139.162.108.7) 56(84) bytes of data. ^C --- mirror-jp.firstyear.id.au ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2027ms

2 3

Mesa 23.1.7 32-bit libraries missing in updates repo on Slowroll
by Kostadin Shishmanov 03 Oct '23

03 Oct '23

When I try to install steam on slowroll, for some reason Mesa-32bit-23.1.7 is missing from the "updates" repo and instead zypper asks me to downgrade Mesa to 23.1.5 in order to go through, which makes KDE use llvmpipe. Can someone figure out why the 32bit libraries of mesa 23.1.7 are missing from updates?

2 1

slowroll ignoring packages in updates repo
by Felix Miata 03 Oct '23

03 Oct '23

3 4

Puzzling rootless docker issue on TW
by Jim Henderson 01 Oct '23

01 Oct '23

I've been attempting to help a user in the forums[1] with an issue running Docker rootless - he's running into an issue with being able to pull images resulting in the following error: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on 10.0.2.3:53: read udp 10.0.2.100:48971->10.0.2.3:53: i/o timeout He also opened a discussion in the Docker forums (who referred him to our forums), and I've been chatting with the guy (Ákos) who was helping him over there in that thread[2]. The puzzling thing for me is that I can't duplicate the issue. I've tried on GNOME and KDE both, and I just cannot reproduce the problem. In troubleshooting the issue together with Ákos, we seem to have isolated the issue to something in the slirp4netns network that's used in that configuration - but nobody involved has customized that setup at all - yet it fails for both of them and doesn't fail for me. The issue *seems* to be that the DNS server set up in that network (10.0.2.3) is not responsive for either of them - but it is for me. Wondering if anyone here has any ideas about what else to look at beyond what we already have in these two threads. I'm completely out of ideas. Jim [1] https://forums.opensuse.org/t/rootless-docker-i-o-timeout-with-docker- pull/169468/12 [2] https://forums.docker.com/t/rootless-docker-i-o-timeout-with-docker- pull/137848 -- Jim Henderson Please keep on-topic replies on the list so everyone benefits

4 11

openSUSE:Factory - Build fail notification
by DimStar / Dominique Leuenberger 30 Sep '23

30 Sep '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. - flux: Fails to build - gnuprumcu: Unresolvable - goverlay: Fails to build - python-Flask-Security-Too: Fails to build - python-pip-api: Fails to build 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 20230927 released!
by Dominique Leuenberger 30 Sep '23

30 Sep '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: Mesa (23.1.7 -> 23.1.8) Mesa-drivers (23.1.7 -> 23.1.8) autoyast2 (4.6.2 -> 5.0.1) gcc13 gnome-tweaks (42.beta+60 -> 45.0) gpg2 (2.3.8 -> 2.4.0) libsolv (0.7.24 -> 0.7.25) libstorage-ng (4.5.141 -> 4.5.143) mozjs115 (115.2.0 -> 115.2.1) open-vm-tools python-alembic (1.11.2 -> 1.12.0) tracker unar vsftpd yast2-schema (4.6.1 -> 5.0.1) yast2-storage-ng (4.6.12 -> 5.0.1) yast2-users (4.6.4 -> 5.0.1) === Details === ==== Mesa ==== Version update (23.1.7 -> 23.1.8) Subpackages: Mesa-libEGL1 Mesa-libGL1 Mesa-libglapi0 libOSMesa8 libgbm1 - Backport upstream patches for compatibility with LLVM 17: * U_llvmpipe-only-include-old-Transform-includes-when-ne.patch removes unneeded includes of header files that no longer exist. * U_clover-llvm-move-to-modern-pass-manager.patch migrates Clover to the new pass manager, since the old PM has been removed. - disable nine on arm/aarch64 in the hope to fix build on this platform; there is no need for Direct3D/Wine for arm/aarch64 anyway ... - Update to bugfix release 23.1.8: - -> https://docs.mesa3d.org/relnotes/23.1.8.html ==== Mesa-drivers ==== Version update (23.1.7 -> 23.1.8) Subpackages: Mesa-dri Mesa-gallium Mesa-libva libxatracker2 - Backport upstream patches for compatibility with LLVM 17: * U_llvmpipe-only-include-old-Transform-includes-when-ne.patch removes unneeded includes of header files that no longer exist. * U_clover-llvm-move-to-modern-pass-manager.patch migrates Clover to the new pass manager, since the old PM has been removed. - disable nine on arm/aarch64 in the hope to fix build on this platform; there is no need for Direct3D/Wine for arm/aarch64 anyway ... - Update to bugfix release 23.1.8: - -> https://docs.mesa3d.org/relnotes/23.1.8.html ==== autoyast2 ==== Version update (4.6.2 -> 5.0.1) Subpackages: autoyast2-installation - Added several LUKS-related elements to the partitioning schema (jsc#PED-3878, jsc#PED-5518). - 5.0.1 - 5.0.0 (#bsc1185510) ==== gcc13 ==== Subpackages: cpp13 gcc13-locale libasan8 libatomic1 libgcc_s1 libgccjit0 libgfortran5 libgomp1 libhwasan0 libitm1 liblsan0 libobjc4 libquadmath0 libstdc++6 libstdc++6-locale libstdc++6-pp libtsan2 libubsan1 - add pr111411.patch (bsc#1215427) ==== gnome-tweaks ==== Version update (42.beta+60 -> 45.0) Subpackages: gnome-tweaks-lang - Update to version 45.0: + This release removes several features now found in GNOME Settings. There are also some small interface refreshments in preparation for the GTK4 upgrade. More significantly, the core interface has been refactored to use layout files. + Updated translations. - Switch compression to zst both in service and tarball produced. ==== gpg2 ==== Version update (2.3.8 -> 2.4.0) Subpackages: dirmngr gpg2-lang - Install the systemd user units in the _userunitdir [bsc#1201564] * Note that, there is no activation by default. * Rework excludes in the spec's files section. - Temporarily revert back to the pre-2.4 default for key generation. The new rfc4880bis has been set as the default in 2.4 version and might create incompatible keys. Note that, rfc4880bis can still be used with the option flag --rfc4880bis as in previous versions. * More info in the gnupg-devel ML: https://lists.gnupg.org/pipermail/gnupg-devel/2022-December/035183.html * Reverted commit https://dev.gnupg.org/rGcaf4b3fc16e9 * Add gnupg-revert-rfc4880bis.patch - Allow 8192 bit RSA keys in keygen UI when large_rsa is set * Add gnupg-allow-large-rsa.patch - Fix broken GPGME QT tests: Upstram dev task dev.gnupg.org/T6313 * The original patch has been modified to expand the changes also to the tests/gpgme/Makefile.in file. * Add gnupg-tests-Fix-tests-gpgme-for-in-source-tree-builds.patch - Updated to require libgpg-error-devel >= 1.46 - Rebased patches: * gnupg-allow-import-of-previously-known-keys-even-without-UIDs.patch * gnupg-add_legacy_FIPS_mode_option.patch - GnuPG 2.4.0: * common: Fix translations in --help for gpgrt < 1.47. * gpg: Do not continue the export after a cancel for the primary key. * gpg: Replace use of PRIu64 in log_debug. * Update NEWS for 2.4.0. * tests: Fix make check with GPGME. * agent: Allow arguments to "scd serialno" in restricted mode. * scd:p15: Skip deleted records. * build: Remove Windows CE support. * wkd: Do not send/install/mirror expired user ids. * gpgsm: Print the revocation time also with --verify. * gpgsm: Fix "problem re-searching certificate" case. * gpgsm: Print revocation date and reason in cert listings. * gpgsm: Silence the "non-critical certificate policy not allowed". * gpgsm: Always use the chain model if the root-CA requests this. * gpg: New export option "mode1003". * gpg: Remove a mostly duplicated function. * tests: Simplify fake-pinentry to use the option only. * tests: Fix fake-pinentry for Windows. * tests: Fix make check-all. * agent: Fix import of protected v5 keys. * gpgsm: Change default algo to AES-256. * tests: Put a workaround for semihosted environment. * tests: More fix for semihosted environment. * tests: Support semihosted environment. * tests: Fix tests under cms. * tests,w32: Fix for semihosted environment. * w32: Fix for tests on semihosted environment. * w32: Fix gnupg_unsetenv. * wkd: New option --add-revocs and some fixes. * wkd: Make use of --debug extprog. * gpg: New export-filter export-revocs. * gpg: Fix double-free in gpg --card-edit. * gpg: Make --require-compliance work with out --status-fd. * gpg: New option --list-filter. * dirmngr: Silence ocsp debug output. * tests: Fix to support --enable-all-tests and variants. * tests:w32: Fix for non-dot file name for Windows. * tests:gpgscm:w32: Fix for GetTempPath. * tests: Keep .log files in objdir. * tests: Use 233 for invalid value of FD. * w32: Fix gnupg_tmpfile for possible failure. * scd: Redact --debug cardio output of a VERIFY APDU. * common: Remove Windows CE support in common. * gpgsm: Fix colon outout of ECC encryption certificates. * scd:nks: Fix ECC signing if key not given by keygrip. * dirmngr: Fix verification of ECDSA signed CRLs. * agent: Allow trustlist on Windows in Unicode homedirs. * gpg: Fix verification of cleartext signatures with overlong lines. * gpg: Move w32_system function. * gpg: New option --quick-update-pref. * gpg: New list-options show-pref and show-pref-verbose. * tests: Add tests to check that OCB is only used for capable keys. * gpg: Make --list-packets work w/o --no-armor for plain OCB packets. * tests: Add symmetric decryption tests. * tests: Add tr:assert-same function. * agent: Avoid blanks in the ssh key's comment. * build: Update m4 files. * gpg: Merge --rfc4880bis features into --gnupg. * gpg: Allow only OCB for AEAD encryption. * gpg: New option --compatibility-flags. * gpgsm: Also announce AES256-CBC in signatures. * gpg: Fix trusted introducer for user-ids with only the mbox. * gpg: Import stray revocation certificates. * agent: Automatically convert to extended key format by KEYATTR. * card: New commands "gpg" and "gpgsm". * card: Also show fingerprints of known X.509 certificates. * scd:nks: Support non-ESIGN signing with the Signature Card v2. * gpgsm: Allow ECC encryption keys with just keyAgreement specified. * gpgsm: Use macro constants for cert_usage_p. * build: Update gpg-error.m4. * agent,common,dirmngr,tests,tools: Remove spawn PREEXEC argument. * gpg: Move NETLIBS after GPG_ERROR_LIBS. * gpg: Use GCRY_KDF_ONESTEP_KDF with newer libgcrypt in future. * common,w32: Fix struct stat on Windows. * agent,w32: Support Win32-OpenSSH emulation by gpg-agent. * common: Don't use FD2INT for POSIX-only code. * dirmngr: Fix build with no LDAP support. ==== libsolv ==== Version update (0.7.24 -> 0.7.25) Subpackages: libsolv-tools python3-solv ruby-solv - support complex deps in SOLVABLE_PREREQ_IGNOREINST - fix minimization not prefering installed packages in some cases - reduce memory usage in repo_updateinfoxml - fix lock-step interfering with architecture selection - fix choice rule handing for package downgrades - fix complex dependencies with an "else" part sometimes leading to unsolved dependencies - bump version to 0.7.25 ==== libstorage-ng ==== Version update (4.5.141 -> 4.5.143) Subpackages: libstorage-ng-lang libstorage-ng-ruby libstorage-ng1 - merge gh#openSUSE/libstorage-ng#949 - reduce manual memory handing - 4.5.143 - merge gh#openSUSE/libstorage-ng#948 - fixed memory leak - more consistent function naming - 4.5.142 ==== mozjs115 ==== Version update (115.2.0 -> 115.2.1) - Update to version 115.2.1: + Security fix: CVE-2023-4863: Heap buffer overflow in libwebp. ==== open-vm-tools ==== Subpackages: libvmtools0 open-vm-tools-desktop - open-vm-tools is built with containerinfo plugin from 15 sp3 onwards ==== python-alembic ==== Version update (1.11.2 -> 1.12.0) - Clean up the SPEC file - update to 1.12.0 * Added new feature to the "code formatter" function which allows standalone executable tools to be run against code, without going through the Python interpreter. Known as the `exec` runner, it complements the existing `console_scripts` runner by allowing non-Python tools such as `ruff` to be used. * Change the default value of `.EnvironmentContext.configure.compare_type` to `True`. As Alembic's autogenerate for types was dramatically improved in version 1.4 released in 2020, the type comparison feature is now much more reliable so is now enabled by default. * Fixed issue where the `ForeignKeyConstraint.match` parameter would not be rendered in autogenerated migrations. * Fixed issue where the `revision_environment` directive in `alembic.ini` was ignored by the `alembic merge` command, leading to issues when other configurational elements depend upon `env.py` being invoked within the command. * Added support for `op.drop_constraint()` to support PostgreSQL `ExcludeConstraint` objects, as well as other constraint-like objects that may be present in third party dialects, by resolving the `type_` parameter to be `None` for this case. Autogenerate has also been enhanced to exclude the `type_` parameter from rendering within this command when `type_` is `None`. ==== tracker ==== Subpackages: libtracker-sparql-3_0-0 tracker-data-files tracker-lang typelib-1_0-Tracker-3_0 - use pkgconfig(icu-i18n) to use the current libicu. (jsc#PED-6193) ==== unar ==== - use pkgconfig(icu-uc) to use the current libicu. (jsc#PED-6193) ==== vsftpd ==== - Enable crypto-policies support: [bsc#1211301] * Add vsftpd-use-system-wide-crypto-policy.patch ==== yast2-schema ==== Version update (4.6.1 -> 5.0.1) - Added several LUKS-related elements to the partitioning schema (jsc#PED-3878, jsc#PED-5518). - 5.0.1 - 5.0.0 (#bsc1185510) ==== yast2-storage-ng ==== Version update (4.6.12 -> 5.0.1) - AutoYaST: official support for LUKS2 (jsc#PED-3878, jsc#PED-5518) - 5.0.1 - 5.0.0 (#bsc1185510) ==== yast2-users ==== Version update (4.6.4 -> 5.0.1) - Don't use obsolete method Dir.exists? (bsc#1215637) - 5.0.1 - 5.0.0 (#bsc1185510)

1 0