October 2023 - openSUSE Factory - openSUSE Mailing Lists

Sudo announcement - upcoming changes
by Otto Hollmann 27 Nov '23

27 Nov '23

Hi all, I'm happy to inform you about upcoming changes in our openSUSE implementation of sudo. The first change is splitting configuration files between /etc and /usr/etc. More information about why we are introducing this change can be found here [1]. Sudo will read configuration files in the following order: /etc/sudoers, /usr/etc/sudoers. Our distribution file will be installed in /usr/etc/sudoers. If there is no /etc/sudoers file, the command visudo will open /usr/etc/sudoers and save the result as /etc/sudoers. If /etc/sudoers file already exists, there is no change in visudo behavior - it will open and edit /etc/sudoers. Big thanks to sudo upstream and Jason Sikes for this change. The second change relates to the configuration "Defaults targetpw" SUSE traditionally ships sudo with "Defaults targetpw". That allows any user in the system to use sudo without configuration by authenticating as the target user (usually root). An alternative authentication scheme used by some Linux distributions allows users who are members of a specific group to authenticate as root by typing their own password. So far, this model required manual configuration. To make this approach easier, we are now introducing the following optional packages: * sudo-policy-wheel-auth-self * sudo-policy-sudo-auth-self * system-group-sudo If installed, users in the wheel group (first package) or sudo group (second package) will be asked for their password instead of the password of the target account when executing the sudo command. There is no change for users who are not in those special groups. sudo will continue to prompt for the target password for those users. So updating sudo is safe in any case. The third package (which will be installed as a dependency for the package sudo-policy- sudo-auth-self) creates a configuration file for systemd-sysusers, ensuring that the system group "sudo" will be created. *Please note the meaning of the wheel group is not well defined, so adding users to that group may have effects outside the scope of sudo.* In addition, those packages also install polkit policies so applications using polkit will be also allowed to authenticate in the same way. [1] https://en.opensuse.org/openSUSE:Packaging_UsrEtc Regards, Otto Hollmann

9 23

Remove dependency on /usr/bin/python3
by Daniel Garcia 22 Nov '23

22 Nov '23

Hello, As part of a Python team maintenance task we are trying to remove the dependency on /usr/bin/python3 from as many packages as possible to reduce the problems of changing the system python in the future [1]. Right now /usr/bin/python3 is a link provided by the current system python package that today is python311, in Factory. Any package that provides a python script with the shebang #!/usr/bin/python3 will have the requirement on /usr/bin/python3. There's a macro in the python-rpm-macros to fix the shebang on python scripts automatically, that can be used in the install phase, just before the fdupes call, and point to the real binary and not the link: %python3_fix_shebang This macro expands to: for f in /home/abuild/rpmbuild/BUILDROOT/%{NAME}-%{VERSION}- %{RELEASE}.x86_64/usr/bin/*; do [ -f $f ] && sed -i "1s@#!.*python.*@#!$(realpath /usr/bin/python3)@" $f done And indeed will replace the shebang to point to #!/usr/bin/python3.11. This will make the script to work correctly, even if the system python changes in the distribution, avoiding the problem of running with a different python and not finding the deps that are in /usr/lib/python3.11/site- packages. In some cases it could be okay to have the shebang #!/usr/bin/python3, if there are no external dependencies and it's something that will work with different python versions, but when possible, and as a general rule, it'll be better to fix the shebangs. If you maintain a package that provides some python script, please, consider to add this macro call. [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1212476 -- Daniel García Moreno Python Packager

8 13

Announcing Agama 5
by Imobach Gonzalez Sosa 22 Nov '23

22 Nov '23

Hi all, We have just released Agama 5 which, among other things, includes: * A translated web user interface. By now, it is available in Dutch, English, Japanese, Spanish, Swedish. * A prototype of a software patterns selection. However, the important part is the discussion in the openSUSE Factory mailing list[1]. * Agama does not reuse pre-existing swap partitions. * Support to boot via PXE. As usual, you can find the full announcement in our blog[2]. Regards, Imo [1] https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… [2] https://yast.opensuse.org/blog/2023-10-25/agama5 -- Imobach González Sosa SUSE Linux LLC

2 1

What Tumbleweed patterns do we want to offer during Agama installation
by Ancor Gonzalez Sosa 21 Nov '23

21 Nov '23

We need to talk. ;-) As you may know, the YaST Team is developing an alternative installer called Agama (formerly D-Installer). https://github.com/openSUSE/agama We want the workflow in Agama to be simpler than with YaST. Even without any selection of packages to install. But quite some people expressed their desire of being able to customize the software selection while installing the operating system itself. Since we don't want to bring back complex and specific concepts like the installation roles, we decided to expose the current list of patterns so the users can decide which ones to install... knowing that would expose some organizational problems we have with patterns. Take a look at https://yast.opensuse.org/assets/images/patterns-demo.gif That's a first implementation that shows we have WAY too many patterns that are WAY too arbitrarily organized. If we want to use patterns as the main concept to allow software customization... What can we do? Organize the patterns better? Introduce some kind of flag to distinguish the patterns that make sense to offer during installation? Fix something in the way we categorize the patterns? We feel this is not an UI problem, but an structural one. We are looking forward for realistic suggestions. Meanwhile, you can play with the current list by downloading the staging version of Agama. Ie. any image called agama-live-xxx-openSUSE-yyy.iso from https://download.opensuse.org/repositories/systemsmanagement:/Agama:/Stagin… Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions

12 23

Disabling /dev/fb0 on TW
by Thomas Zimmermann 21 Nov '23

21 Nov '23

tl;dr: Disable fbdev userspace interfaces on TW Hi, the upcoming Linux kernel v6.6 will contain the option to disable fbdev userspace interfaces in the kernel configuration. [1] I intent to enable this and thereby switch off /dev/fb0 et al. The tracker bug is boo#1212947. [2] * Why? The old fbdev subsystem is an endless source of bugs. For example, we recently had an out-of-bounds access in the fbdev emulation, where userspace could write beyond the end of the framebuffer memory. [3] Fbdev is under-maintained. I've been doing improvements in recent kernel releases, but only where it benefits the DRM subsystem. Disabling fbdev userspace interfaces will also help weeding out any programs that still contain hard dependencies on them. * What changes? Enabling the new kernel option disables all fbdev userspace interfaces. These are * the device files, such as /dev/fb0 * the sys files under /sys/class/graphics/fb[0-9]+ * /proc/fb * What are the effects on userspace programs? Userspace applications run on the desktop via Wayland or X. There will be no change to them. Xorg and Wayland compositors run on DRM interfaces. A few programs run on SDL, which has no dependency on fbdev either. Any fbdev support in these mid-layer components should be disabled as well. There's one known affected program: TW's text-mode installer can use the tool fbiterm to display CJK symbols during installation. This comes from a time when some low-end systems where not able to boot graphics installation. fbiterm has been unmaintained for >15 years and is ready for retirement. But there's no good drop-in replacement. I propose to simply remove fbiterm and let the graphics installer handle CJK. * What about the framebuffer console? The kernel-provided framebuffer console does not change. The kernel will still show the regular console. Userspace interfaces in /sys/class/graphics/fbcon are still available. For questions and discussion, please comment here or in boo#1212947. Best regards Thomas [1] https://elixir.bootlin.com/linux/v6.6-rc1/source/drivers/video/fbdev/core/K… [2] https://bugzilla.opensuse.org/show_bug.cgi?id=1212947 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… -- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Frankenstrasse 146, 90461 Nuernberg, Germany GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman HRB 36809 (AG Nuernberg)

9 29

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

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

31 Oct '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. - sonic-pi: 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

[Announcement] support for systemd soft-reboot
by Thorsten Kukuk 31 Oct '23

31 Oct '23

Hi, systemd v254 introduced "soft-reboot" (https://manpages.opensuse.org/systemctl),which reboots the userland, but not the kernel or hardware. This allows a quick reboot after updates of e.g. dbus, glibc or openssl. With the latest snapshot, rebootmgr and os-update support this now, too. Means, if you use os-update for automatic updating your server and an update requires a reboot, but there is no new kernel or bootloader, the reboot will be done much quicker now. transactional-upate will get support for this next. The "zypp-boot-plugin" (https://manpages.opensuse.org/zypp-boot-plugin) looks at the packages which got installed or updated and decides according a config file, if: - a hard reboot is required (e.g. after update of the bootloader - kexec is enough (if only the kernel is updated) - a soft-reboot is sufficient - no reboot is necessary at all It's in the responsibility of the application triggering the reboot which of the method it used, zypp-boot-plugin only gives a hint. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany Managing Director: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)

1 0

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

30 Oct '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. - weblate: Fails to build - yuzu: 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 20231029 released!
by Dominique Leuenberger 30 Oct '23

30 Oct '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: GraphicsMagick apache2-mod_php8 (8.2.11 -> 8.2.12) avahi avahi-glib2 glib2 (2.78.0 -> 2.78.1) gnome-settings-daemon gnome-software gvfs libsoup (3.4.3 -> 3.4.4) libstorage-ng (4.5.154 -> 4.5.155) mozilla-nss (3.93 -> 3.94) open-vm-tools p11-kit (0.25.0 -> 0.25.1) php8 (8.2.11 -> 8.2.12) vim (9.0.2043 -> 9.0.2078) virtualbox virtualbox-kmp xdg-desktop-portal (1.18.0 -> 1.18.1) xfconf (4.18.2 -> 4.18.1) === Details === ==== GraphicsMagick ==== Subpackages: libGraphicsMagick++-Q16-12 libGraphicsMagick-Q16-3 libGraphicsMagick3-config - Have libGraphicsMagick3-config require ghostscript-fonts-std (boo#1216604). ==== apache2-mod_php8 ==== Version update (8.2.11 -> 8.2.12) - version update to 8.2.12 * This is a bug fix release. https://www.php.net/ChangeLog-8.php#8.2.12 ==== avahi ==== Subpackages: avahi-lang libavahi-client3 libavahi-client3-32bit libavahi-common3 libavahi-common3-32bit libavahi-core7 - Add avahi-CVE-2023-38473.patch: derive alternative host name from its unescaped version (bsc#1216419 CVE-2023-38473). ==== avahi-glib2 ==== Subpackages: libavahi-glib1 libavahi-gobject0 libavahi-ui-gtk3-0 - Add avahi-CVE-2023-38473.patch: derive alternative host name from its unescaped version (bsc#1216419 CVE-2023-38473). ==== glib2 ==== Version update (2.78.0 -> 2.78.1) Subpackages: glib2-lang glib2-tools libgio-2_0-0 libglib-2_0-0 libgmodule-2_0-0 libgobject-2_0-0 libgthread-2_0-0 - Update to version 2.78.1: + Fix truncating files when `g_file_set_contents_full()` is called without `G_FILE_SET_CONTENTS_CONSISTENT` + Fix `-Dlibelf=disabled` on Linux + Bugs fixed: - NetworkManager 1.44.0 crashes repeatedly with glib 2.78.0 - gsubprocess-testprog.c: build error with cygwin (sys/ptrace.h: No such file or directory) - gio clears modification time in microseconds when setting with `set_modification_date_time` - Build of glib 2.78.0 ignores -Dlibelf=disabled - glib-2.78.0 fails at gio/tests/gsubprocess.p/gsubprocess.c.o - Segfault when creating GIO GPropertyAction without properties - `g_file_set_contents_full()` doesn't truncate the file (without `G_FILE_SET_CONTENTS_CONSISTENT`) - guniprop.c: Avoid creating (temporarily) out-of-bounds pointers - Fixes for integer cast warnings when targeting CHERI - Fix test_find_program on FreeBSD - gconstructor.h: Ensure [c|d]tor prototypes are present for MSVC - Fix gutils-user-database test on macOS - Add value annotation to G_TYPE_FUNDAMENTAL_MAX - meson: Fix Windows build with PCRE2 as sibling subproject - gconstructor.h: Ensure [c|d]tor prototypes are present for MSVC - glocalfileinfo: Preserve microseconds for access/modify times - Make sure the `GTask` is freed on a graceful disconnect - Buffer needs to be aligned correctly to receive linux_dirent64. - gtestutils.h: Fix warning with -Wsign-conversion caused by g_assert_cmpint - tests: Drop unnecessary include from gsubprocess-testprog.c - wakeup: do single read when using eventfd() - wakeup: Fix g_wakeup_acknowledge if signal comes inâ - Use g_task_return in task threads - build: Fix -Dlibelf=disabled on Linux - gfileutils: Add a missing ftruncate() call when writing files + Updated translations. - Drop 0005-gthreadedresolver-Fix-race.patch: Fixed upstream. ==== gnome-settings-daemon ==== Subpackages: gnome-settings-daemon-lang - Add 538816ff42f682fc4b541810ca107486abab9976.patch: smartcard: Steal error when propagating through GTask. ==== gnome-software ==== Subpackages: gnome-software-lang gnome-software-plugin-packagekit - Rebase gnome-software-disable-offline-update.patch(bsc#1216603). - Add gnome-software-plugin-opensuse-distro-upgrade.patch: plugins: add opensuse-distro-upgrade plugin(glgo#GNOME/gnome-software!1557). ==== gvfs ==== Subpackages: gvfs-backend-afc gvfs-backend-goa gvfs-backend-samba gvfs-backends gvfs-fuse gvfs-lang - Use older way than autopatch on SLE/Leap, which is not ready for the macro. - Rebase gvfs-nvvfs.patch. ==== libsoup ==== Version update (3.4.3 -> 3.4.4) Subpackages: libsoup-3_0-0 libsoup-lang typelib-1_0-Soup-3_0 - Update to version 3.4.4: + Improve HTTP/2 performance when a lot of buffering happens + Support building libnghttp2 as a subproject ==== libstorage-ng ==== Version update (4.5.154 -> 4.5.155) Subpackages: libstorage-ng-lang libstorage-ng-ruby libstorage-ng1 - merge gh#openSUSE/libstorage-ng#963 - extended testsuite - 4.5.155 ==== mozilla-nss ==== Version update (3.93 -> 3.94) Subpackages: libfreebl3 libsoftokn3 mozilla-nss-certs mozilla-nss-tools - update to NSS 3.94 * bmo#1853737 - Updated code and commit ID for HACL* * bmo#1840510 - update ACVP fuzzed test vector: refuzzed with current NSS * bmo#1827303 - Softoken C_ calls should use system FIPS setting to select NSC_ or FC_ variants * bmo#1774659 - NSS needs a database tool that can dump the low level representation of the database * bmo#1852179 - declare string literals using char in pkixnames_tests.cpp * bmo#1852179 - avoid implicit conversion for ByteString * bmo#1818766 - update rust version for acvp docker * bmo#1852011 - Moving the init function of the mpi_ints before clean-up in ec.c * bmo#1615555 - P-256 ECDH and ECDSA from HACL* * bmo#1840510 - Add ACVP test vectors to the repository * bmo#1849077 - Stop relying on std::basic_string<uint8_t> * bmo#1847845 - Transpose the PPC_ABI check from Makefile to gyp - rebased patches - added nss-fips-test.patch to fix broken test ==== open-vm-tools ==== Subpackages: libvmtools0 open-vm-tools-desktop - Fix (bsc#1216432) - VUL-0: CVE-2023-34058: open-vm-tools: SAML token signature bypass vulnerability. - Fix (bsc#1216433) - VUL-0: : CVE-2023-34059: open-vm-tools: file descriptor hijack vulnerability + Add patch: - CVE-2023-34058.patch - CVE-2023-34059.patch ==== p11-kit ==== Version update (0.25.0 -> 0.25.1) Subpackages: libp11-kit0 libp11-kit0-32bit p11-kit-tools - Update to 0.25.1: * fix probing of C_GetInterface [#535] * p11-kit: add command to list tokens [#581] * p11-kit: add command to list mechanisms supported by a token [#576] * p11-kit: add command to generate private-public keypair on a token [#551, #582] * p11-kit: add commands to import/export certificates and public keys into/from a token [#543, #549, #568, #588] * p11-kit: add commands to list and delete objects of a token [#533, #544, #571] * p11-kit: add --login option to login into a token with object and profile management commands [#587] * p11-kit: adjust behavior of PKCS#11 profile management commands [#558, #560, #583, #591] * p11-kit: print PKCS#11 URIs in list-modules [#532] * bug and build fixes [#528 #529, #534, #537, #540, #541, #545, [#547], #550, #557, #572, #575, #579, #585, #586, #590] * test fixes [#553, #580] * Remove patch fixed upstream: - d1d4b0ac316a27c739ff91e6c4153f1154e96e5a.patch ==== php8 ==== Version update (8.2.11 -> 8.2.12) Subpackages: php8-cli php8-ctype php8-dom php8-gd php8-gettext php8-iconv php8-mbstring php8-mysql php8-openssl php8-pdo php8-sqlite php8-tokenizer php8-xmlreader php8-xmlwriter - version update to 8.2.12 * This is a bug fix release. https://www.php.net/ChangeLog-8.php#8.2.12 ==== vim ==== Version update (9.0.2043 -> 9.0.2078) Subpackages: vim-data vim-data-common xxd - Update to version 9.0.2078 * several problems with type aliases * Vim9: No support for type aliases * TextChangedI may not always trigger * Completion menu may be wrong * don't echo empty lines (#13431) * typo in quickfix.c comments * update debian related runtime files (#13423) * Vim9: no nr2str conversion in list-unpack * objdump files not recognized * [security] disallow setting env in restricted mode * possible to escape bracketed paste mode with Ctrl-C * [security] overflow in :history * clarify bracketed paste mode * missing code formatting in if_pyth.txt * xxd: coloring was disabled on Cygwin * xxd: corrupting files when reversing bit dumps * EXPAND flag set for filetype option * cannot use buffer-number for errorformat * Fix typos in several documents (#13420) * pacman hooks are detected as conf filetype * Janet files are not recognised * not able to detect xkb filetypes * *.{gn,gni} files are not recognized * small updates to the documentation for varargs * Update ftplugin - comment motions (#13412) * outstanding exceptions may be skipped * tests: avoid error when no swap files exist * Vim9: no strict type checks for funcrefs varargs * do not use hard-coded match id (#13393) * no digraph for quadruple prime * Vim9: non-consistent error messages * win32: iscygpty needs update * Add new ftplugin (#13385) * zig filetype detection test wrong * win32: using deprecated wsock32 api * Vim9: wrong error for non-existing object var * Update Zig runtime files (#13388) * Vim9: crash with deferred function call and exception * Vim9: not recognizing qualified class vars for infix ops * python: uninitialized warning * perl: warning about inconsistent dll linkage * tests: checking for swap files takes time * Vim9: exceptions confuse defered functions * allow for overriding systemd ftplugin settings (#13373) ==== virtualbox ==== - Update file "fixes_for_leap.patch" to cover API change in Leap 15.6 kernel. ==== virtualbox-kmp ==== - Update file "fixes_for_leap.patch" to cover API change in Leap 15.6 kernel. ==== xdg-desktop-portal ==== Version update (1.18.0 -> 1.18.1) Subpackages: xdg-desktop-portal-lang - Update to version 1.18.1: + Communicate better when the Background portal kills an app. + Properly quote Flatpak command in the Background portal. + Improve documentation of the "cursor_mode" propery of the ScreenCast backend D-Bus interface. + Fix ScreenCast portal removing transient restore permissions too early. This fixes screen sharing dialogs on Chromium asking for the screen multiple times. + Only send the Closed session signal to the sender. + Add Meson options to disable building with Bubblewrap, and without the Flatpak portal documentation. Disabling Bubblewrap is highly discouraged, and only meant to be used on platforms that do not currently support it. By disabling Bubblewrap, bitmap validation happens without a sandbox, which is highly insecure since image parsing is a common source of exploits. Really, just do not disable Bubblewrap please. + Improve the manpage of portals.conf. + Various spelling fixes to the Document portal. + Add a new website! We don't have a fancy domain yet, but the website can be accessed at https://flatpak.github.io/xdg-desktop-portal/ + Improve pid mapping for host system apps. This should get rid of some rare, unnecessary warnings. + Adjust documentation of Global Shortcuts portal's timestamps to millisecond granularity. + Bump minimum Meson version to 0.58. ==== xfconf ==== Version update (4.18.2 -> 4.18.1) Subpackages: libxfconf-0-3 typelib-1_0-Xfconf-0 xfconf-lang

1 0