February 2024 - openSUSE Factory - openSUSE Mailing Lists

Disabling /dev/fb0 on TW
by Thomas Zimmermann 23 Oct '24

23 Oct '24

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)

12 35

Plan to delete vagrant & Virtualization:vagrant by the end of November
by Dan Čermák 18 Oct '24

18 Oct '24

Dear all, due to Hashicorp changing the license of vagrant to the BUSL, we can no longer update vagrant in openSUSE. I don't have the cycles to maintain vagrant myself indefinitely and plan to send a delete request at the end of November to Factory. Once that goes in, I also plan to remove the Virtualization:vagrant project to reduce the number of rubygems we have in openSUSE. If you don't like this plan and decide to scream at me, please scream an actionable plan that involves you :-) Cheers, Dan -- Dan Čermák <dcermak(a)suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstr. 146 90461 Nürnberg Germany www.suse.com Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)

6 14

New Tumbleweed snapshot 20240110 released!
by Dominique Leuenberger 15 Aug '24

15 Aug '24

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&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: certmonger (0.79.15 -> 0.79.19) eog (45.1 -> 45.2) git gnome-remote-desktop (45.0 -> 45.1) gnome-shell (45.2 -> 45.3) gvfs (1.52.1 -> 1.52.2) hwdata (0.377 -> 0.378) libgxps (0.3.2 -> 0.3.2+5) libstorage-ng (4.5.170 -> 4.5.171) libxkbcommon mutter (45.2 -> 45.3) nodejs21 (21.4.0 -> 21.5.0) publicsuffix (20231213 -> 20240107) redis (7.2.3 -> 7.2.4) sg3_utils (1.48+6.7f43e14 -> 1.48+7.63e63cb) transmission (4.0.4 -> 4.0.5) yast2-packager (5.0.1 -> 5.0.2) === Details === ==== certmonger ==== Version update (0.79.15 -> 0.79.19) - Update to 0.79.19 - Removed 0001-Disable-DSA-in-the-RPM-spec.patch - Added 0001-Update-tests-to-be-compatible-with-OpenSSL-3.2.patch ==== eog ==== Version update (45.1 -> 45.2) Subpackages: eog-lang - Update to version 45.2: + data: Update appdata. + Updated translations. ==== git ==== Subpackages: git-core git-email git-web perl-Git - gitweb AppArmor profile: allow reading etc/gitweb-common.conf (boo#1218664) ==== gnome-remote-desktop ==== Version update (45.0 -> 45.1) Subpackages: gnome-remote-desktop-lang - Update to version 45.1: + session: - Assert region size to be greater than 0 - Add debug message to also output new EI regions - Scale absolute pointer position with respect to the EI region - Clear all EI related instances before dbus session stop call - Only notify keysym when EI keyboard is available - Add struct for absolute pointer motion events + vnc-pipewire-stream: Don't remove buffer while dequeueing it + rdp-pipewire-stream: Don't remove buffer while dequeueing it + Adapt usage of abs pointer motion events to GrdEventPointerMotionAbs + Updated translations. ==== gnome-shell ==== Version update (45.2 -> 45.3) Subpackages: gnome-extensions gnome-shell-calendar gnome-shell-lang - Update to version 45.3: + Allow any enter key to be used to screenshot. + Fix spinner in light style variant. + Improve formatting of extension errors. + Fixed crash. + Misc. bug fixes and cleanups. + Updated translations. - Drop gnome-shell_nb_fix_trans.patch: fixed upstream. ==== gvfs ==== Version update (1.52.1 -> 1.52.2) Subpackages: gvfs-backend-afc gvfs-backend-goa gvfs-backend-samba gvfs-backends gvfs-fuse gvfs-lang - Update to version 1.52.2: + smb: Fix livelock when mounting share without enough permissions. + smb: Fi moving files across filesystem boundaries. + Updated transltions. ==== hwdata ==== Version update (0.377 -> 0.378) - update to 0.378: * Update pci, usb and vendor ids ==== libgxps ==== Version update (0.3.2 -> 0.3.2+5) - Update to version 0.3.2+5: + DOAP: Fix 'bug-database' value to point to GNOME GitLab Issues + images: - For jpeg images try to get the image resolution from exif first - Add support for jpeg images with CMYK color space + Fix compiler warnings + Fix meson warnings - Switch to git checkout via source service, use explicit commit. - Use ldconfig_scriptlets macro for post(un) handling. - Update URL to new home. - Drop no longer needed libgxps-rpmlintrc. ==== libstorage-ng ==== Version update (4.5.170 -> 4.5.171) Subpackages: libstorage-ng-lang libstorage-ng-ruby libstorage-ng1 - merge gh#openSUSE/libstorage-ng#977 - provide light_probe function with SystemInfo parameter - 4.5.171 ==== libxkbcommon ==== Subpackages: libxkbcommon-x11-0 libxkbcommon0 libxkbregistry0 - add libxkbregistry-devel to baselibs for use by wine-32bit. (bsc#1218640) ==== mutter ==== Version update (45.2 -> 45.3) Subpackages: mutter-lang - Update to version 45.3: + Fix handling of relative mode for tablets. + Fix forcing EGLStream with NVIDIA proprietary driver. + Sync geometry only when window is mapped. + Improve repick due to transform changes. + wayland/client: Add make_desktop() method. + Fix occasional artifacts at top of X11 fullscreen windows. + background: Fix background color around image. + Fixed crashes. + Plugged leaks. + Misc. bug fixes and cleanups. + Updated translations. ==== nodejs21 ==== Version update (21.4.0 -> 21.5.0) Subpackages: npm21 - Update to 21.5.0: * module: merge config with package_json_reader * src: move package resolver to c++ * doc: + deprecate hash constructor + deprecate dirent.path - linker_lto_jobs.patch: refreshed ==== publicsuffix ==== Version update (20231213 -> 20240107) - Update to version 20240107: * Remove homeoffice.gov.uk (#1909) * util: gTLD data autopull updates for 2024-01-06T15:12:04 UTC (#1918) ==== redis ==== Version update (7.2.3 -> 7.2.4) - redis 7.2.4: (boo#1218646) - Security fixes - (CVE-2023-41056) In some cases, Redis may incorrectly handle resizing of memory buffers which can result in incorrect accounting of buffer sizes and lead to heap overflow and potential remote code execution. - Bug fixes - Fix crashes of cluster commands clusters with mixed versions of 7.0 and 7.2 (#12805, #12832) - Fix slot ownership not being properly handled when deleting a slot from a node (#12564) - Fix atomicity issues with the RedisModuleEvent_Key module API event (#12733) ==== sg3_utils ==== Version update (1.48+6.7f43e14 -> 1.48+7.63e63cb) Subpackages: libsgutils2-1_48-2 - Fix spurious warning for non-SCSI devices (boo#1218666) ==== transmission ==== Version update (4.0.4 -> 4.0.5) Subpackages: transmission-common transmission-gtk transmission-gtk-lang - Update to version 4.0.5: + Fixed 4.0.0 bug where the IP address field in UDP announces were not encoded in network byte order. + Fixed a bug that incorrectly escaped JSON strings in some locales. + Fixed 4.0.4 decreased download speeds for people who set a low upload bandwidth limit. + Fixed bug that prevented editing trackers on magnet links. + Fixed HTTP tracker announces and scrapes sometimes failing after adding a torrent file by HTTPS URL. + In RPC responses, change the default sort order of torrents to match Transmission 3.00. + Fixed tr_sys_path_copy() behavior on some Synology Devices. + Fix: only append .added suffix to watchdir files. + Fixed crash when opening torrent file from "Recently used" section in GTK 4. ==== yast2-packager ==== Version update (5.0.1 -> 5.0.2) - After installation disable the empty installation repository from the SLE15 Online medium (bsc#1182303) - 5.0.2

9 9

Tumbleweed - Review of the week 2024/07
by Dominique Leuenberger 19 Jun '24

19 Jun '24

Dear Tumbleweed users and hackers, This week we have released 5 snapshots (0209, 0211, 0212, 0213, and 0214). With 5 snapshots, this is quite a normal week. The most relevant changes in those snapshots were: * SDL 2.30.0 * c-ares 1.26.0 (after a lengthy staging phase) * fwupd 1.9.13 * PostgreSQL 16.2 * Pulseaudio 17.0 * GTK 4.12.5 * Python 3.11.8 * KDE Frameworks 5.115.0 * RPM 4.19.1.1 * Node.JS 21.6.1 The list of things currently being tested remained largely unchanged: * Meson 1.3.2 * Shadow 4.14.5 * pkgconf 2.1.1 * RPM: enable reproducible builds by default (bsc#1148824). For upstream versions see: https://github.com/rpm-software-management/rpm/pull/2880 * A bunch of cleanup work to eliminate more of python2 (boo#1219306) * dbus-broker: a big step forward; upgrades seem to be an issue that needs to be addressed * libxml 2.12.x: slow progress * GCC 14: our usual 2-phase approach to introduce it. Currently working on phase 1, meaning GCC14 will be providing the base libraries (libgcc_s1, libstdc++…). The compiler itself will stay at version 13 for now. Only one issue left: qemu fails to build Cheers, Dominique

3 3

factory@ is now under moderation
by Neal Gompa 28 May '24

28 May '24

Hello all, Due to the recent continuous inappropriate behavior on the factory@ mailing list, we have taken the extraordinary action of moderating the entire mailing list. Each message being submitted will be actively reviewed for approval until the Board works through the necessary and appropriate behavior to resolve this incident. -- Neal Gompa (ID: Pharaoh_Atem)

3 2

[opensuse-factory] Leap 42.3 Build 0312 released!
by Ludwig Nussel 25 Apr '24

25 Apr '24

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&version=42.3&bui… https://bugzilla.opensuse.org/buglist.cgi?product=openSUSE%20Distribution&q… When you reply to discuss some issues, make sure to change the subject. Please use the test plan at https://docs.google.com/spreadsheets/d/1AGKijKpKiJCB616-bHVoNQuhWHpQLHPWCb3… to record your testing efforts and use bugzilla to report bugs. Packages changed: biosdevname btrfsmaintenance conduit gconf2-branding-openSUSE (42.1 -> 42.3) ibus kactivitymanagerd kde-user-manager kernel-source (4.4.73 -> 4.4.74) libxml2 libzypp (16.12.0 -> 16.13.0) lightdm marble mc plasma5-integration plasma5-openSUSE postgresql (9.4 -> 9.6) python-coverage (3.7.1 -> 4.3.4) ucode-intel (20160714 -> 20170511) yast2-bootloader (3.2.22 -> 3.2.23) yast2-ntp-client (3.2.9 -> 3.2.12) === Details === ==== biosdevname ==== - Duplicate naming of SRIOV VFs by biosdevname when VPD_DCM Strings are present in VFs (bsc#1042185) * Add: biosdevname_avoid_duplicates.patch ==== btrfsmaintenance ==== - Require btrfsprogs (bsc#1047226) - update to 0.2 - updated documentation - no hardcoded paths to external utilities - fixed logger name typos for 'journal' target - defrag fixes (sysconfig, find arguments) - Removed patch: balance-typo.patch - Added patch: sysconfig-override-trim.diff - Add balance-typo.patch (bnc#986543) - version 0.1.1 - fix typo and make journal logging target work - cron refresh: remove bashism - Removed patches: * 0003-Add-COPYING-file.patch * 0011-cron-refresh-remove-debuggiong-output.patch - cron script symlinks are not created on first installation (bsc#907343) - add COPYING to package - refresh script: remove extra messages - add uninstall targets - fix refresh service - adjust sysconfig defaults - Add more package dependencies (cron, zypp-plugin) - minor bugfixes - Add supplements(btrfsprogs) - initial version 0.1 ==== conduit ==== Subpackages: conduit-lang - Use python-vobject instead of vobject per python-vobject change in 42.3. ==== gconf2-branding-openSUSE ==== Version update (42.1 -> 42.3) - do not build novell-sound-theme in the gconf2-branding-SLED build to prevent duplicated binaries in openSUSE Leap. The novell-sound-theme is taken from gconf2-branding-SLES sources on both the SLED product and the SLES WE module. bsc#1046099 - bump versions ==== ibus ==== Subpackages: ibus-branding-openSUSE-KDE ibus-gtk ibus-gtk-32bit ibus-gtk3 ibus-lang libibus-1_0-5 libibus-1_0-5-32bit python-ibus typelib-1_0-IBus-1_0 - Update ibus.spec: copy auto-start files to SOURCE directory to enable modifications before compile. - Add ibus-disable-engines-preload-in-GNOME.patch: Disable load preload-engines actions in SLE, which is unnecessary for mono IMF in SLE and may cause CJK user login failed (bsc#1036729). ==== kactivitymanagerd ==== - Recommend -lang package ==== kde-user-manager ==== - Recommend -lang package ==== kernel-source ==== Version update (4.4.73 -> 4.4.74) Subpackages: kernel-default kernel-default-devel kernel-devel kernel-docs kernel-macros kernel-syms - Delete patches.kabi/kabi-fix-for-kvm-x86-fix-singlestepping-over-syscall. No need for kABI fix yet for Leap 42.3. - commit f0a86d9 - Fix kABI breakage by KVM CVE fix (bsc#1045922). - commit c0308f6 - powerpc/perf: Fix branch event code for power9 (fate#321438, Pending SUSE Kernel Fixes). - commit e954af6 - powerpc: Fix /proc/cpuinfo revision for POWER9 DD2 (bsc#1046789). - commit 444247f - Refresh metadata patches.drivers/ibmvnic-a2-Fix-assignment-of-RX-TX-IRQ-s.patch. - commit be32be9 - drm/i915: Serialize GTT/Aperture accesses on BXT (bsc#1046821). - commit b263fef - Bluetooth: hidp: fix possible might sleep error in hidp_session_thread (bsc#1031784). - Refresh patches.suse/kgr-0008-mark-task_safe-in-some-kthreads.patch. - commit 18c6f3e - KVM: x86: fix singlestepping over syscall (CVE-2017-7518 bsc#1045922). - commit d989643 - nvme/pci: Fix stuck nvme reset (bsc#1043805). - commit 7afe4f0 - Refresh fadump patches to upstream and add metadata patches.arch/powerpc-fadump-add-reschedule-point-while-releasing-memory.patch. patches.arch/powerpc-fadump-avoid-duplicates-in-crash-memory-ranges.patch patches.arch/powerpc-fadump-avoid-holes-in-boot-memory-area-when-fadump-is-registered.patch patches.arch/powerpc-fadump-provide-a-helpful-error-message.patch - commit f0fb5c3 - blacklist.conf: Remove duplicated entries - commit cb960d2 - Remove duplicated blacklist entries and put git-commit tag to patches - commit 12a0cb2 - blacklist.conf: Remove duplicated entry. - commit 561ddb1 - ibmvnic: Fix assignment of RX/TX IRQ's (bsc#1046589). - commit 5fa38bf - blacklist.conf: blacklist 570d8e939801 we do not care about the code in Documentation all that much, do we? - commit 69d5811 - blacklist.conf: blaclist 5380e5644afb it is just not worth backporting without any explicit report where a silently truncated success would lead to a real bug. - commit fc28626 - blacklist.conf: unnecessary patch The bug triggers only upon a malformed descriptor and the comparison is so that our buffer would be too large not too small so no overflow. The device would not work, but it won't anyway. - commit 99f8a16 - Rearrange the previous patches for hpsa and smartpqi to the right position. - commit a1f1f27 - Update patches.fixes/xfs-split-default-quota-limits-by-quota-type.patch (bsc#1040941). Fix the bug nr used. - commit 115ba75 - printk: Correctly handle preemption in console_unlock() (bsc#1046434). - commit 0a3c2a4 - printk/xen: Force printk sync mode when migrating Xen guest (bsc#1043347). - commit e13596b - btrfs: disable possible cause of premature ENOSPC (bsc#1040182) - commit 8bf31da - rbd: make sure pages are freed by libceph (bsc#1045596). - rbd: drop extra rbd_img_request_get (bsc#1045596). - commit c8719f2 - dm-raid: Do not call BUG() in __rdev_sectors() (bsc#1046264). - commit 0b1aab0 - btrfs: Round down values which are written for total_bytes_size (bsc#1043912). - btrfs: Manually implement device_total_bytes getter/setter (bsc#1043912). - commit c4d2eb7 - pipe: cap initial pipe capacity according to pipe-max-size limit (bsc#1045330). - commit 4ee3ec2 - Blacklist drivers/net/ethernet/ibm/emac We do not build the driver. - commit d432b2b - blacklist.conf: this patch breaks the API It disallows some operations that are now allowed - commit 98325c2 - arm64: Update config files. (bsc#1036737) Disable XGENE_PMU. - commit 7bb0115 - Disable Xilinx network drivers (bsc#1046170). - commit 656fc83 - hwpoison, memcg: forcibly uncharge LRU pages (bnc#1046105). - commit 2b252e1 - blacklist.conf: blacklist 570d8e939801 the issue is visible only when 80df554275c2 is applied (4.7+ and not backported to our trees) - commit 47b83ce - config/x86_64: make CONFIG_SERIAL_8250_DW and *_MID built-in (bsc#1024449) - commit 2e3ca7e - Refresh patches.drivers/0477-nvme-add-hostid-token-to-fabric-options.patch. Update mainline references. - commit eee1109 - fs/exec.c: account for argv/envp pointers (bnc#1039354, CVE-2017-1000365). - commit 7418d0f - Refresh ibmvnic patch metadata patches.drivers/ibmvnic-98-ibmvnic-Correct-return-code-checking-for-ibmvnic_init-during-probe.patch. patches.drivers/ibmvnic-a0-ibmvnic-Fix-incorrectly-defined-ibmvnic_request_map_rsp-structure.patch. patches.drivers/ibmvnic-a1-ibmvnic-Fix-error-handling-when-registering-long-term-mapped-buffers.patch. - commit babc17a - Refresh metadata patches.fixes/powerpc-tm-Fix-stack-pointer-corruption-in-__tm_recheckpoint. - commit 0b5bdc6 - powerpc/ftrace: Pass the correct stack pointer for DYNAMIC_FTRACE_WITH_REGS (FATE#322421). - commit 936e653 - nvme: add hostid token to fabric options (bsc#1045293). - commit 52dffb9 - iw_cxgb4: Fix error return code in c4iw_rdev_open() (bsc#1026570). - RDMA/iw_cxgb4: Always wake up waiter in c4iw_peer_abort_intr() (bsc#1026570). - commit 2ce43b1 - clocksource/drivers/arm_arch_timer: Fix read and iounmap of incorrect variable (bsc#1045937). - commit 594f037 - Linux 4.4.74 (CVE-2017-1000364 bnc#1012382 bnc#1039348 bnc#1045340 bsc#1031717 bsc#1043231). - Delete patches.drivers/media-pvrusb2-reduce-stack-usage-pvr2_eeprom_analyze. - Delete patches.drivers/media-vb2-Fix-an-off-by-one-error-in-vb2_plane_vaddr. - Delete patches.drivers/staging-rtl8188eu-prevent-an-underflow-in-rtw_check_. - Delete patches.fixes/mm-fix-new-crash-in-unmapped_area_topdown.patch. - Delete patches.fixes/mm-larger-stack-guard-gap-between-vmas.patch. - commit 5e41880 - tty: Fix ldisc crash on reopened tty (bnc#1043488). - commit 04cca20 - tty: Destroy ldisc instance on hangup (bnc#1043488). - tty: Refactor tty_ldisc_reinit() for reuse (bnc#1043488). - tty: Use 'disc' for line discipline index name (bnc#1043488). - tty: Move tty_ldisc_kill() (bnc#1043488). - tty: Handle NULL tty->ldisc (bnc#1043488). - tty: Prepare for destroying line discipline on hangup (bnc#1043488). - tty: Reset c_line from driver's init_termios (bnc#1043488). - tty: Simplify tty_set_ldisc() exit handling (bnc#1043488). - commit c016cca - kabi: ignore fs_info parameter for tracepoints that didn't have it (bsc#1044912). - commit 24869ea ==== libxml2 ==== Subpackages: libxml2-2 libxml2-2-32bit libxml2-devel libxml2-tools - Security fix: * libxml2-CVE-2017-7376.patch [bsc#1044887, CVE-2017-7376] * Increase buffer space for port in HTTP redirect support - Security fix: * libxml2-CVE-2017-7375.patch [bsc#1044894, CVE-2017-7375] * Prevent unwanted external entity reference - Upstream patches updated and with tests: * libxml2-CVE-2017-9047.patch and libxml2-CVE-2017-9048.patch merged into libxml2-CVE-2017-9047.patch [bsc#1039066, bsc#1039661] * libxml2-CVE-2017-9049.patch and libxml2-CVE-2017-9050.patch merged into libxml2-CVE-2017-9049.patch [bsc#1039063, bsc#1039064] ==== libzypp ==== Version update (16.12.0 -> 16.13.0) - Adapt loop mounting of iso images (bsc#1038132, bsc#1033236) - Adjust zypp.conf for openSUSE Tumbleweed (bsc#1031756) - Change arch variable names conflicting with compiler macros (fixes #70) - Fix potential crash if repo has no baseurl (bnc#1043218) - version 16.13.0 (0) ==== lightdm ==== Subpackages: liblightdm-gobject-1-0 lightdm-lang - Augment patch to also resolve the target of symlink sessions for detemining the preselected option: * ignore-known-symlink-sessions.patch ==== marble ==== Subpackages: libastro1 libmarblewidget-qt5-27 marble-data marble-devel marble-doc marble-kde marble-lang - Add Fix-utm-enum-value.patch and reverse-apply it, this upstream commit causes a crash when adding bookmarks if switched to UTM view angles because the necessary handler functions for the dialog are not implemented yet (boo#1044747, kde#381872) - Add Fix-plain-map-and-political-map-showing-no-content.patch to fix the plain map and the political map being not displayed at all (kde#379297) ==== mc ==== Subpackages: mc-lang - sftp.patch: Backport upstream fixes for SFTP (boo#1004280, boo#1042797) ==== plasma5-integration ==== - Move the Recommends: %{name}-plugin-lang to the plasma5-integration-plugin sub package, otherwise the translations won't get installed as there is no main package (boo#1027925) - Actually apply the aforementioned patch (shouldn't the source validator have warned?) ==== plasma5-openSUSE ==== Subpackages: plasma5-defaults-openSUSE plasma5-theme-openSUSE plasma5-workspace-branding-openSUSE sddm-theme-openSUSE - Fix installation of the sddm theme files (boo#1047254) ==== postgresql ==== Version update (9.4 -> 9.6) Subpackages: postgresql-contrib postgresql-devel postgresql-docs postgresql-server - Bump version and defaultpackage to 9.6. - Move ~postgres/.bash_profile to postgresql-server to avoid a file conflict between the versioned server packages. - Bump version and defaultpackage to 9.4. - Bump version and defaultpackage to 9.3. - Change license string to PostgreSQL. - Make all dummy packages noarch. - Make PostgreSQL 9.2 the default. - Reduce the postgresql packages with unversioned names to dummy packages that require the respective versioned package names. ==== python-coverage ==== Version update (3.7.1 -> 4.3.4) - uninstall alternatives in %postun - update for singlespec - update to 4.3.4: - Using the --skip-covered option on an HTML report with 100% coverage would cause a ?No data to report? error, as reported in issue 549. This is now fixed; thanks, Lo�c Dachary. - If-statements can be optimized away during compilation, for example, if 0: or if __debug__:. Coverage.py had problems properly understanding these statements which existed in the source, but not in the compiled bytecode. This problem, reported in issue 522, is now fixed. - If you specified --source as a directory, then coverage.py would look for importable Python files in that directory, and could identify ones that had never been executed at all. But if you specified it as a package name, that detection wasn?t performed. Now it is, closing issue 426. Thanks to Lo�c Dachary for the fix. - If you started and stopped coverage measurement thousands of times in your process, you could crash Python with a ?Fatal Python error: deallocating None? error. This is now fixed. Thanks to Alex Groce for the bug report. - On PyPy, measuring coverage in subprocesses could produce a warning: ?Trace function changed, measurement is likely wrong: None?. This was spurious, and has been suppressed. - Previously, coverage.py couldn?t start on Jython, due to that implementation missing the multiprocessing module (issue 551). This problem has now been fixed. Also, issue 322 about not being able to invoke coverage conveniently, seems much better: jython -m coverage run myprog.py works properly. - Let?s say you ran the HTML report over and over again in the same output directory, with --skip-covered. And imagine due to your heroic test-writing efforts, a file just acheived the goal of 100% coverage. With coverage.py 4.3, the old HTML file with the less-than-100% coverage would be left behind. This file is now properly deleted. - update to Version 4.3.1 ? 2016-12-28: - Some environments couldn?t install 4.3, as described in issue 540. This is now fixed. - The check for conflicting --source and --include was too simple in a few different ways, breaking a few perfectly reasonable use cases, described in issue 541. The check has been reverted while we re-think the fix for issue 265. - update to Version 4.3 ? 2016-12-27: Special thanks to Lo�c Dachary, who took an extraordinary interest in coverage.py and contributed a number of improvements in this release. - The HTML report now supports a --skip-covered option like the other reporting commands. Thanks, Lo�c Dachary for the implementation, closing issue 433. - Subprocesses that are measured with automatic subprocess measurement used to read in any pre-existing data file. This meant data would be incorrectly carried forward from run to run. Now those files are not read, so each subprocess only writes its own data. Fixes issue 510. - Coverage.py wouldn?t execute sys.excepthook when an exception happened in your program. Now it does, thanks to Andrew Hoos. Closes issue 535. - The coverage combine command will now fail if there are no data files to combine. The combine changes in 4.2 meant that multiple combines could lose data, leaving you with an empty .coverage data file. Fixes issues issue 525, issue 412, issue 516, and probably issue 511. - The branch coverage issues described in issue 493, issue 496, and issue 502 are now fixed, thanks to Lo�c Dachary. - Options can now be read from a tox.ini file, if any. Like setup.cfg, sections are prefixed with ?coverage:?, so [run] options will be read from the [coverage:run] section of tox.ini. Implements part of issue 519. Thanks, Stephen Finucane. - Specifying both --source and --include no longer silently ignores the include setting, instead it fails with a message. Thanks, Nathan Land and Lo�c Dachary. Closes issue 265. - Coverage.py can now search .pex files for source, just as it can .zip and .egg. Thanks, Peter Ebden. - update to 4.2: - Since ``concurrency=multiprocessing`` uses subprocesses, options specified on the coverage.py command line will not be communicated down to them. Only options in the configuration file will apply to the subprocesses. Previously, the options didn't apply to the subprocesses, but there was no indication. Now it is an error to use ``--concurrency=multiprocessing`` and other run-affecting options on the command line. This prevents failures like those reported in `issue 495`_. - Filtering the HTML report is now faster, thanks to Ville Skytt�. - update to 4.0.3: - Fixed a mysterious problem that manifested in different ways: sometimes hanging the process (`issue 420`_), sometimes making database connections fail (`issue 445`_). - The XML report now has correct ``<source>`` elements when using a ``--source=`` option somewhere besides the current directory. This fixes `issue 439`_. Thanks, Arcady Ivanov. - Fixed an unusual edge case of detecting source encodings, described in `issue 443`_. - Help messages that mention the command to use now properly use the actual command name, which might be different than "coverage". Thanks to Ben Finney, this closes `issue 438`_. - add LICENSE.txt - Pre require coreutils. This package is needed for the rm call in the pre section. Subprocess failed. Error: RPM failed: /var/tmp/rpm-tmp.gONanE: line 3: rm: command not found - specfile: * updated license * updated update-alternatives * README.txt -> README.rst - update to version 4.0: (long list, see http://coverage.readthedocs.org/en/latest/changes.html) - fix rhel deps by depending on /usr/sbin/update-alternatives ==== ucode-intel ==== Version update (20160714 -> 20170511) - Update to version 20170511 - Update to version 20161104. ==== yast2-bootloader ==== Version update (3.2.22 -> 3.2.23) - AuotYaST configuration: Set StorageDevices flag disks_valid to true. So libstorage can scan valid disks and "/" partition can be found. (bnc#1043132) - 3.2.23 ==== yast2-ntp-client ==== Version update (3.2.9 -> 3.2.12) - Resrict records are written at the end but the default file and most profiles use them at the beginning, which mangles the file completely (bsc#983486). To fix it we have just changed the order of writing. - 3.2.12 - AutoYaST: Fix crash when trying to sanitize not string values, for example initial_sync. - AutoYaST: Sanitize comments by only removing blank spaces at the beginning and adding line break. This avoids augeas parse errors (bsc#1045777). - 3.2.11 - AutoYaST: Fix crash in CFA when creating a command record with some key value option is given (bsc#1045968) - 3.2.10 - AutoYaST: Comments from autoyast profile should not be sanitized to avoid entries without space between value and comment (e.g trustedkey 1# coment). This is caused by a bug in augeas adding new entries. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] acpid requires systemd?
by Felix Miata 25 Apr '24

25 Apr '24

Can this be true? If so, why? Zypper won't let me upgrade acpid without breakage unless systemd is installed too. I have systemd locked out, as I'd rather test things I can understand in Factory, not major overhaul stuff. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 3

enabling reproducible builds in Factory and ALP
by Jan Zerebecki 15 Mar '24

15 Mar '24

Hi *, to support https://en.opensuse.org/openSUSE:Reproducible_Builds I plan to get the following project configuration for Factory and ALP enabled: Macros: %source_date_epoch_from_changelog Y %clamp_mtime_to_source_date_epoch Y %use_source_date_epoch_as_buildtime Y %_buildhost reproducible :Macros I'm still waiting to get https://github.com/openSUSE/product-builder/pull/26 merged to prevent a bug with mirrors that will otherwise happen. Afterwards a time of the build is still in the HTTP header Last-Modified when requesting the rpm file. HTTP mtime is a few seconds earlier than end time of the build (seen in OBS web UI only as start + duration). I didn't double check, but it should also be recorded in the Tumbleweed archive Bernhard keeps, which can with a bit of work be looked up by content hash or name including version of the rpm file if its not on the normal mirrors anymore. Both the build time and host can also still be seen in the build log. Comments welcome. -- Best regards, Jan Zerebecki

4 6

Issues with vagrant / libvirt since snapshot from this week Tuesday or Wednesday?
by Johannes Kastl 08 Mar '24

08 Mar '24

Hi all, is anyone else experiencing issues with libvirt since mid of this week? I can no longer start VMs using vagrant. Vagrant hangs at "Waiting for domain to get an IP address..." and never gets anywhere. Existing VMs can be started using virsh or libvirt, so it might be an issue with vagrant itself. But it was working until mid of this week, despite being outdated (due to the licensing change). I noticed some errors regarding missing directories on Feb 8th and today: > Feb 08 13:09:28 baten systemd[1]: Starting libvirt legacy monolithic daemon... > Feb 08 13:09:28 baten libvirtd[7841]: libvirt version: 10.0.0 > Feb 08 13:09:28 baten libvirtd[7841]: hostname: baten > Feb 08 13:09:28 baten libvirtd[7841]: Failed to initialize libnetcontrol. Management of interface devices is disabled > Feb 08 13:09:28 baten systemd[1]: Started libvirt legacy monolithic daemon. > Feb 08 13:09:29 baten libvirtd[7841]: Interner Fehler: failed to query mdevs from mdevctl: Error: Required directory "/usr/lib/mdevctl/scripts.d/callouts" doesn't exist. This may indicate a packaging or installation error > Feb 08 13:11:28 baten systemd[1]: libvirtd.service: Deactivated successfully. or > > Feb 10 18:31:36 baten systemd[1]: Started libvirt legacy monolithic daemon. > Feb 10 18:31:37 baten libvirtd[4420]: Interner Fehler: failed to query mdevs from mdevctl: Error: Required directory "/usr/lib/mdevctl/scripts.d/notifiers" doesn't exist. This may indicate a packaging or installation error And sure enough there are no directories in /usr/lib/mdevctl/scripts.d/ on all of my machines... Kind Regards, Johannes

6 11

Proposal: amend the packaging guidelines for %fillup_only
by Dan Čermák 02 Mar '24

02 Mar '24

Hi list, our packaging guidelines for %fillup_only [1] currently do not suggest anything for the %files section for the files generated in `/etc/sysconfig/`. I would like to suggest that we start adding the newly generated file `/etc/sysconfig/$pkgname` as follows to the %files section: --8<---------------cut here---------------start------------->8--- %files %ghost %config(noreplace) %attr(0600,root,root) /etc/sysconfig/%{name} %dir /etc/sysconfig --8<---------------cut here---------------end--------------->8--- This ensures that rpm is aware of the files as configuration files. Thoughts, opinions? Cheers, Dan Footnotes: [1] https://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros#%fillup_o… -- Dan Čermák <dcermak(a)suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstr. 146 90461 Nürnberg Germany www.suse.com Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)

3 3