Bug#1081066: ITP: libjs-htmx -- framework for performing various javascript actions from html
Hi Andrea On 2024/09/09 09:53, Andrea Pappacoda wrote: And, after checking, that's indeed not possible. Could you please ship both a compressed and an uncompressed version of the file? libjs-jquery does this, while libjs-highlight-js only ships uncompressed files: Hmm, I was sure I saw this working on Saturday. Anyway, I was strongly considering shipping the unzipped version anyway, so I'll upload a new version that does just that later today. -Jonathan
Bug#1081066: ITP: libjs-htmx -- framework for performing various javascript actions from html
Hi Andrea On 2024-09-07 23:07, Andrea Pappacoda wrote: On Sat Sep 7, 2024 at 9:51 PM CEST, Jonathan Carter wrote: * Package name: libjs-htmx Should the source package be called htmx.js or libjs-htmx? According to <https://wiki.debian.org/Javascript/Policy>, browser only libraries should be called libjs-htmx, but since version 2.0.0 an ECMAScript Module is provided too. I went with libjs-htmx, it's now in unstable. This installs the htmx binary to: /usr/share/javascript/htmx/htmx.min.js.gz I'm not an expert when it comes to JavaScript (and that's in part why I like htmx), and know even less about JavaScript policies in Debian. But, wouldn't installing a gzipped file create issues? Can I directly include it into a browser? Yes, browsers support gz decompression, and the decompression doesn't cause any noticeable overhead. -Jonathan
Bug#1081066: ITP: libjs-htmx -- framework for performing various javascript actions from html
Package: wnpp Severity: wishlist Owner: Jonathan Carter X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: libjs-htmx Version : 2.0.2 Upstream Contact: bigskysoftware (https://github.com/bigskysoftware * URL : https://htmx.org * License : BSD-0-Clause Programming Lang: JavaScript Description : framework for performing various javascript actions from html htmx gives you access to AJAX, CSS Transitions, WebSockets and Server Sent Events directly in HTML, using attributes, so you can build modern user interfaces with the simplicity and power of hypertext. htmx is tiny, and has no dependencies. This installs the htmx binary to: /usr/share/javascript/htmx/htmx.min.js.gz
Bug#1080380: GNOME: Finish installation screen with wrong buttons
Hi Roland Only seen on the GNOME desktop environment in sid: the Calamares installer shows the wrong buttons after the installation has finished. You can see the result here: https://openqa.debian.net/tests/301443#step/live_install_calamares/44 The 'Install' tab is not shown during the installation, and the content of the 'Finish' tab is overlaid on the still showing 'Summary' tab. See https://openqa.debian.net/tests/301443#step/live_install_calamares/23 for the first message that the installation has finished. I couldn't reproduce this on a local KVM machine, do you know what kind of graphics card the openqa machines use and how much display memory is assigned to them? thanks for all the testing! -Jonathan
Bug#1080188: calamares: Missing dependency: rsync
Hi Roland While preparing a MR for supporting dracut instead of initramfs-tools for live-build, I've noticed that Calamares requires 'rsync' which was not available in the images that I have locally generated. The executable rsync is called here: https://sources.debian.org/src/calamares/3.3.9-1/src/modules/unpackfs/main.py/#L179 Can you add rsync to the Depends list of calamares? Calamares itself doesn't rely on the unpackfs in order to function, for example, someone might use it as a rescue system, OEM setup tool, or even in installations use a mode that doesn't depend on rsync (like using a bootstrap tool, for example). I could add it as a dependency for calamares-settings-debian, or even add it as a recommends for Calamares, but first I'd like more details on what you're doing. What are you doing in an initramfs or in dracut that uses Calamares? Are you building an initial ramdisk that contains Calamares? thanks, -Jonathan
Bug#1080402: bookworm-pu: package calamares-settings-debian/12.0.9-1+deb12u2
Package: release.debian.org Severity: normal Tags: bookworm X-Debbugs-Cc: calamares-settings-deb...@packages.debian.org Control: affects -1 + src:calamares-settings-debian User: release.debian@packages.debian.org Usertags: pu [ Reason ] This update fixes two bugs still found in Debian 12 live sessions: - BTRFS installations with Calamares currently fail (Debian bug: #180158) - On KDE, the calamares icon isn't displayed (currently worked around in live-build, so the bug is still present when building on other build systems (Debian bug: #1057853) [ Impact ] If this update isn't approved, btrfs installations will continue to fail and the calamares icon will in some cases be absent from the live media on KDE sessions. [ Tests ] I build the package in a bookworm chroot, and tested it on current installation media. Both bugs were successfully solved with no other noticable effect. [ Risks ] These are quite trivial fixes, I don't expect any complications. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] Here is the debdiff that contains all the changes: """ diff -Nru calamares-settings-debian-12.0.9/debian/changelog calamares-settings-debian-12.0.9/debian/changelog --- calamares-settings-debian-12.0.9/debian/changelog 2024-08-22 16:35:51.0 +0200 +++ calamares-settings-debian-12.0.9/debian/changelog 2024-09-03 13:27:38.0 +0200 @@ -1,3 +1,12 @@ +calamares-settings-debian (12.0.9-1+deb12u2) bookworm; urgency=medium + + * Fix missing calamares launcher on KDE desktops +(Closes: #1057853) + * Fix broken btrfs space_cache option +(Closes: #1080158) + + -- Jonathan Carter Tue, 03 Sep 2024 13:27:38 +0200 + calamares-settings-debian (12.0.9-1+deb12u1) bookworm; urgency=medium * Fix Xfce launcher permission issue (Closes: #1037299) diff -Nru calamares-settings-debian-12.0.9/debian/patches/remove-btrfs-spacecache-setting calamares-settings-debian-12.0.9/debian/patches/remove-btrfs-spacecache-setting --- calamares-settings-debian-12.0.9/debian/patches/remove-btrfs-spacecache-setting 1970-01-01 02:00:00.0 +0200 +++ calamares-settings-debian-12.0.9/debian/patches/remove-btrfs-spacecache-setting 2024-09-03 13:27:38.0 +0200 @@ -0,0 +1,20 @@ +Description: Remove static btrfs space_cache settings + Calamares sets an option "space_cache", which breaks with newer kernels, + where it should be set to "space_cache=v2". Since "space_cache=v2" is + also default now, this hardcoded option can just be removed, which this + patch does. +Author: Jonathan Carter +Bug-Debian: https://bugs.debian.org/1080158 +Last-Update: 2024-09-03 + +--- calamares-settings-debian-12.0.9.orig/calamares/modules/fstab.conf calamares-settings-debian-12.0.9/calamares/modules/fstab.conf +@@ -1,7 +1,7 @@ + --- + mountOptions: + default: defaults,noatime +-btrfs: defaults,noatime,space_cache,autodefrag ++btrfs: defaults,noatime,autodefrag + ssdExtraMountOptions: + ext4: discard + jfs: discard diff -Nru calamares-settings-debian-12.0.9/debian/patches/remove-calamares-icon-gnome-startup-hint calamares-settings-debian-12.0.9/debian/patches/remove-calamares-icon-gnome-startup-hint --- calamares-settings-debian-12.0.9/debian/patches/remove-calamares-icon-gnome-startup-hint 1970-01-01 02:00:00.0 +0200 +++ calamares-settings-debian-12.0.9/debian/patches/remove-calamares-icon-gnome-startup-hint 2024-09-03 13:27:27.0 +0200 @@ -0,0 +1,18 @@ +Description: Remove calamares icon desktop entry gnome startup hint + The GNOME startup hint in the XDG startup desktop file add-calamares-icon + contains a line "X-GNOME-Autostart-Phase=Initialization" which causes this + script not to run on KDE on Debian 12.x. + . + For more information, please refer to the Debian bug below. +Author: Jonathan Carter +Bug-Debian: https://bugs.debian.org/1057853 + + +--- calamares-settings-debian-12.0.9.orig/conf/calamares-desktop-icon.desktop calamares-settings-debian-12.0.9/conf/calamares-desktop-icon.desktop +@@ -5,5 +5,4 @@ Exec=add-calamares-desktop-icon + StartupNotify=false + NoDisplay=true + +-X-GNOME-Autostart-Phase=Initialization + X-KDE-autostart-phase=1 diff -Nru calamares-settings-debian-12.0.9/debian/patches/series calamares-settings-debian-12.0.9/debian/patches/series --- calamares-settings-debian-12.0.9/debian/patches/series 2024-08-22 16:35:51.0 +0200 +++ calamares-settings-debian-12.0.9/debian/patches/series 2024-09-03 13:27:38.0 +0200 @@ -1 +1,3 @@ fix-xfce-launcher +remove-calamares-icon-gnome-startup-hint +remove-btrfs-spacecache-setting """ thanks, -Jonathan
Bug#1080158: (no subject)
Odd, this was working in my local tests, I installed the calamares-settings-debian pu and the installed system had space_cache=v2 enabled, but I'll take another look at what happens here and then we can push out an update. Thanks for the bug report!
Bug#1057853: Alternative fix proposal
Hey Roland On 2024/08/27 23:29, Roland Clobus wrote: Trixie and sid have a sufficiently new systemd, that contains https:// github.com/systemd/systemd/pull/26379. The bullseye images were generated by a different tool, so there are some differences to be expected. The new bookworm live images are to be generated next weekend, a freeze is already in place. However, since this is a mini change which can be verified quickly, I think the freeze can be lifted for this change. Yeah I added a batch of fixes for all the known bugs in calamares-settings-debian last week that's now in proposed-updates, but missed this once since it was assigned against the debian-live package originally. I can prepare a bookworm-only correction in the builder script (rebuild.sh), that removes the 'X-GNOME-Autostart-Phase' line only in the case of KDE bookworm. I really dislike the idea of hardcoding things like this in a build system, but I suppose it could just be temporary until another calamares-settings-update can make it to stable-updates. -Jonathan
Bug#1054626: Closing
This doesn't seem like a bug in calamares or calamares-settings-debian, but it seems like the local config needed some update or its own settings package. Closing this bug for now, if you need some pointers for integrating calamares into your system, please get in touch or refer to the upstream documentation at: https://calamares.io/docs/users-guide/
Bug#1054626: Calamares hangs on "Removing ## packages" at 73% -- never gets past that
On 2024/08/23 23:03, Fred McKinney wrote: This was downloaded from the Debian Stable repository. Was it used on Debian installation media, or another system or locally created media? -Jonathan
Bug#1054626: Calamares hangs on "Removing ## packages" at 73% -- never gets past that
Hi Fred Is this on the default Debian installation media, or a custom image? thanks, -Jonathan On 2024/08/23 05:10, fredmck wrote: I have had this problem both when installing it in a virtual machine as well as on bare metal. There's nothing unusual I'm doing, as I have tried it with the calamares-settings-debian package installed. I've NEVER been able to get it to work. I currently have Refracta as my installer because of this, but it doesn't appear to be as user-friendly to Linux newbies, IMO, and I'd prefer to have Calamares as my installer, but I can't because of whatever's fouling things up.
Bug#1054626: Calamares hangs on "Removing ## packages" at 73% -- never gets past that
Hi Fred Regarding the bug reported at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054626 I haven't been able to reproduce this or seen it since. Could it be that there was a problem with the installation media, or the hardware that you were installing to at the time? thanks for any further information you can share on this! -Jonathan
Bug#1041617: Calamares issue: The bootloader could not be installed.
Hi László Regarding the bug you filed at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041617 What model of Lenovo laptop is it? Do you know if it's a 32bit only computer that boots EFI? We haven't come across similar issues yet, so just trying to figure out what happened in your specific instance. thanks! -Jonathan
Bug#1079350: bookworm-pu: package calamares-settings-debian/12.0.9-1+deb12u1
Package: release.debian.org Severity: normal Tags: bookworm X-Debbugs-Cc: calamares-settings-deb...@packages.debian.org Control: affects -1 + src:calamares-settings-debian User: release.debian@packages.debian.org Usertags: pu [ Reason ] When launching the desktop icon "Install Debian" from an Xfce session, a user will get a notification that the launcher is not trusted. Adding the gio tools and some snippets to mark the application as trusted fixes this issue. [ Impact ] It's an annoying and somewhat confusing message, and would be nice to fix for the next point release. [ Tests ] I tested this manually on the current 12.6.0 iso and it works fine. [ Risks ] This is a reasonably trivial fix, and poses a low risk. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Debdiff ] """ diff -Nru calamares-settings-debian-12.0.9/debian/changelog calamares-settings-debian-12.0.9/debian/changelog --- calamares-settings-debian-12.0.9/debian/changelog 2023-05-04 20:47:17.0 +0200 +++ calamares-settings-debian-12.0.9/debian/changelog 2024-08-22 16:35:51.0 +0200 @@ -1,3 +1,10 @@ +calamares-settings-debian (12.0.9-1+deb12u1) bookworm; urgency=medium + + * Fix Xfce launcher permission issue (Closes: #1037299) +- Add new dependency: libglib2.0-bin + + -- Jonathan Carter Thu, 22 Aug 2024 16:35:51 +0200 + calamares-settings-debian (12.0.9-1) unstable; urgency=medium * New upstream release diff -Nru calamares-settings-debian-12.0.9/debian/control calamares-settings-debian-12.0.9/debian/control --- calamares-settings-debian-12.0.9/debian/control 2023-04-04 09:51:00.0 +0200 +++ calamares-settings-debian-12.0.9/debian/control 2024-08-22 16:35:51.0 +0200 @@ -13,6 +13,7 @@ Architecture: all Depends: calamares, cryptsetup, +libglib2.0-bin, keyutils, pkexec, qml-module-qtquick-window2, diff -Nru calamares-settings-debian-12.0.9/debian/patches/fix-xfce-launcher calamares-settings-debian-12.0.9/debian/patches/fix-xfce-launcher --- calamares-settings-debian-12.0.9/debian/patches/fix-xfce-launcher 1970-01-01 02:00:00.0 +0200 +++ calamares-settings-debian-12.0.9/debian/patches/fix-xfce-launcher 2024-08-22 16:35:51.0 +0200 @@ -0,0 +1,22 @@ +Description: Fix Xfce launcher + Add gio bits to script so that Xfce doesn't complain about launcher icon + (Closes: #1037299) +Author: Jonathan Carter +Last-Update: 2024-08-22 + +--- calamares-settings-debian-12.0.9.orig/add-calamares-desktop-icon calamares-settings-debian-12.0.9/add-calamares-desktop-icon +@@ -25,3 +25,13 @@ else + # else doesn't seem to care either way. + chmod +x $DESKTOP/install-debian.desktop + fi ++ ++if [ "$XDG_CURRENT_DESKTOP" = "XFCE" ]; then ++#Set desktop launcher as trusted under gnome/xfce (See: #1037299) ++gio set --type=string ~/Desktop/install-debian.desktop \ ++metadata::trusted true ++gio set --type=string ~/Desktop/install-debian.desktop \ ++metadata::xfce-exe-checksum \ ++"$(sha256sum ~/Desktop/install-debian.desktop | cut -f1 -d' ')" ++touch ~/Desktop/install-debian.desktop ++fi diff -Nru calamares-settings-debian-12.0.9/debian/patches/series calamares-settings-debian-12.0.9/debian/patches/series --- calamares-settings-debian-12.0.9/debian/patches/series 1970-01-01 02:00:00.0 +0200 +++ calamares-settings-debian-12.0.9/debian/patches/series 2024-08-22 16:35:51.0 +0200 @@ -0,0 +1 @@ +fix-xfce-launcher """ thanks! -Jonathan
Bug#1078803: Please consider updating to 0.18
Source: wlroots Version: 0.17.4-1 Severity: normal Please consider updating wlroots to 0.18, as some new software need it as a dependency. thanks, -Jonathan
Bug#1078599: O: bcachefs-tools -- bcachefs userspace tools
Package: wnpp Severity: normal X-Debbugs-Cc: bcachefs-to...@packages.debian.org Control: affects -1 + src:bcachefs-tools I intend to orphan the bcachefs-tools package. The package description is: Userspace tools for bcachefs, a modern copy on write, checksumming, multi device filesystem. This package is currently not suitable for inclusion in stable/testing at all. Upstream requires the vendoring of quite a large amount of code. We currently work around this in Debian by relaxing dependencies, but it may cause additional bugs down the line. Also, when a version of bcachefs-tools is one or two minor releases (or a few months) behind, it's considered ancient and buggy and unusable. (see previous bugs filed against the package). I was tempted to remove it completely, but someone suggested that I orphan it instead. I made an upload with the latest version to experimental, and I'm removing it everywhere else.
Bug#1078543: Acknowledgement (RM: bcachefs-tools/stable -- ROM; buggy, obsolete)
If you could also remove version 0.1+git20201025.742dbbdb-1 from oldstable, that would also be great. thanks, -Jonathan
Bug#1078543: RM: bcachefs-tools/stable -- ROM; buggy, obsolete
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: bcachefs-to...@packages.debian.org, debian-rele...@lists.debian.org Control: affects -1 + src:bcachefs-tools User: ftp.debian@packages.debian.org Usertags: remove Dear FTP Team Please remove bcachefs-tools from stable. It's too old to be used with current kernel versions, and may even be harmful. thanks, -Jonathan
Bug#1073821: RM: flask-autoindex -- ROM; RC buggy, no longer maintained
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: flask-autoin...@packages.debian.org, Control: affects -1 + src:flask-autoindex User: ftp.debian@packages.debian.org Usertags: remove Please remove flask-autoindex, It doesn't support Python 3.12, and has not have any upstream releases/uploads for the last 4 years. thanks, -Jonathan
Bug#1054090: zram-tools: diff for NMU version 0.3.3.1-1.2
Hi On 2024/05/30 02:52, Chris Hofstaedtler wrote: I've prepared an NMU for zram-tools (versioned as 0.3.3.1-1.2) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Since this is maintained under /debian (which is basically our collab-maint now), please push the changes [there] and just go ahead and upload it without any needed delay. thanks a lot! -Jonathan [there] https://salsa.debian.org/debian/zram-tools
Bug#1072188: Package error
Package: installation-reports Boot method: Image version: Date: Machine: Dell 7020 Processor:Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz Memory: 16G Partitions: filesystem Type 1K-blocks Used Available Use% Mounted on udev devtmpfs 8108416 0 8108416 0% /dev tmpfs tmpfs 1628976 1552 1627424 1% /run /dev/sda3 btrfs 468253696 32781716 430568940 8% / tmpfs tmpfs 8144876 0 8144876 0% /dev/shm tmpfs tmpfs 5120 16 5104 1% /run/lock efivarfs efivarfs 128 96 28 78% /sys/firmware/efi/efivars /dev/sdb1 btrfs 976761560 5920 974597824 1% /data /dev/sda1 vfat 497684 4480 493204 1% /boot/efi overlay overlay 468253696 32781716 430568940 8% /var/lib/docker/overlay2/afa24d7e3210883370c5732 914467d97f210df47b7a7635495e899928a72/merged tmpfs tmpfs 1628972 232 1628740 1% /run/user/1000 Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06) Subsystem: Dell Device [1028:05a5] Kernel driver in use: hsw_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) DeviceName: Onboard IGD Subsystem: Dell Device [1028:05a5] Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [808 6:0c0c] (rev 06) Subsystem: Dell Device [1028:05a5] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 04) Subsystem: Dell Device [1028:05a5] Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) Subsystem: Dell Device [1028:05a5] Kernel driver in use: mei_me Kernel modules: mei_me 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-LM [8086:153a] (rev 04) DeviceName: Onboard LAN Subsystem: Dell Device [1028:05a4] Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] ( rev 04) Subsystem: Dell Device [1028:05a5] Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [ 8086:8c20] (rev 04) Subsystem: Dell Device [1028:05a5] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [808 6:8c10] (rev d4) Subsystem: Dell Device [1028:05a5] Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 [808 6:8c18] (rev d4) Subsystem: Dell Device [1028:05a5] Kernel driver in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] ( rev 04) Subsystem: Dell Device [1028:05a5] Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:1f.0 ISA bridge [0601]: Intel Corporation Q87 Express LPC Controller [8086:8c4e] (rev 04) Subsystem: Dell Device [1028:05a5] Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c02] (rev 04) DeviceName: Onboard SATA controller #1 Subsystem: Dell Device [1028:05a5] Kernel driver in use: ahci Kernel modules: ahci 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 04) Subsystem: Dell Device [1028:05a5] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 02:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [Stone Peak 2 AC] [8086:5010] Kernel driver in use: iwlwifi Kernel modules: iwlwifi Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect media: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [
Bug#1029007: Bug has reappeared
This bug should've been closed at some point in the past but has reappeared in the newer version: cargo 1.70.0+dfsg2-1 rustc 1.70.0+dfsg2-1 rustc recommends cargo >= 0.71.0~~ and cargo < 0.72.0~~ … The expected solution to the problem (merging of the cargo and rustc sources) has already happened, so it seems that the thing needed now is some frobbing of substvars for the contol file based on the package version? An = versioned recommends based on the standard/automatic substvars? Exercise left to rust stakeholders to discuss. Joseph
Bug#1067925: RFS: fastfetch/2.8.10 [ITP] -- Fastfetch is a neofetch-like tool for fetching system information and displaying them in a pretty way.
Hi Maytham, Sorry for my late reply. Yes. The debian directory was created for submitting fastfetch to my PPA of Ubuntu, and I want to keep it in fastfetch git repo before fastfetch is officially accepted by Debian and Ubuntu so that existing Ubuntu users can keep updating fastfetch. Thanks for your interest. Personally, I am a Fedora user but I am not familiar with Debian. It would be much appreciated if someone could package fastfetch for Debian and Ubuntu users. However, Hiago said that he would take the ITP bug I submitted before. I think I'd like to wait his process first. Regards, Carter -邮件原件- 发件人: Maytham Alsudany 发送时间: 2024年5月2日 20:44 收件人: 1067...@bugs.debian.org 抄送: Carter Li 主题: Re: RFS: fastfetch/2.8.10 [ITP] -- Fastfetch is a neofetch-like tool for fetching system information and displaying them in a pretty way. Hi Carter, It looks like the debian/ directory you have submitted is straight from upstream (which you have also written), and as such seems to be very lacklustre and aimed at Ubuntu. Currently, the packaging does not comply with Debian Policy whatsoever; I recommend that you look at https://wiki.debian.org/Packaging for some basic understanding in (compliant) packaging. I also recommend maintaining packaging for Debian in a separate repo; ideally on Salsa (Debian's GitLab instance) under the "debian" group. If you would like, I am happy to provide a full list of problems with the current package. I'm also interested in getting fastfetch into Debian, so if you don't want to try to fix the packaging, prefer if someone else maintained it in Debian, or want a co-maintainer, I am available :) Kind regards, Maytham On Fri, 29 Mar 2024 01:33:31 + Li Carter wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "fastfetch": > > * Package name : fastfetch > Version : 2.8.10 > Upstream contact : [fill in name and email of upstream] > * URL : https://github.com/fastfetch-cli/fastfetch > * License : Expat > * Vcs : [fill in URL of packaging vcs] Section : universe/utils > > The source builds the following binary packages: > > fastfetch - Fastfetch is a neofetch-like tool for fetching system > information and displaying them in a pretty way. > > To access further information about this package, please visit the > following URL: > > https://mentors.debian.net/package/fastfetch/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x https://mentors.debian.net/debian/pool/main/f/fastfetch/fastfetch_2.8.10.dsc > > Changes for the initial release: > > fastfetch (2.8.10) unstable; urgency=medium . > * Init debian support > > Regards, > -- > Carter Li > >
Bug#1069791: console-setup: Build larger console fonts for HiDPI/accessibility with future 6.9 kernels
My apologies for missing the existing bug scrolling through the list. There were a lot of them to sift through. I may see if some of them have been incidentally fixed as far as I can tell. I understand the eventual goal for the kernel folks is to rid themselves of CONFIG_VT all together, so I realize this is a stopgap. Even so, could you try to include a DejaVuSansMonoBold font as well? I'd appreciate it if it's possible as I can personally read a smaller heavyweight font and it'd really help debugging servers with my portable display. Obviously the long-term solution is some userspace alternative that does the same thing probably using cage and some restricted tabbed terminal maybe? Hmm. I dunno if that's even on anybody's radar any sooner than forky. Joseph On Fri, Apr 26, 2024, at 10:11, Samuel Thibault wrote: > Control: forcemerge -1 816111 > > Hello, > > T. Joseph Carter, le mer. 24 avril 2024 13:25:22 -0700, a ecrit: >> Linux kernel 6.9+ will support larger font sizes for HiDPI screens. This >> is probably aimed at "more than 4k" monitors, but for accessibility >> reasons it would be really useful to have larger sizes available sooner >> for those of us already have 4k sorts of screens. > > Yes, that was the points in adding the support in the kernel :) > >> Perhaps this might best be done by putting those huge-sized fonts in an >> appropriately named -huge fonts package? I'll leave the implementation >> details to you, this is just a request for the fonts to be created. > > We already had the request in #816111, also #595696 was about possibly > generalizing to using rasterized fonts. > > I gave a try at converting terminus.ttf to bdf with otf2bdf: > > otf2bdf -c C -p 32 -r 72 > /usr/share/fonts/truetype/terminus/TerminusTTF-4.46.0.ttf > > /tmp/terminus.bdf > bdf2psf --fb /tmp/terminus.bdf /usr/share/bdf2psf/standard.equivalents > ascii.set 256 /tmp/terminus.psf /tmp/terminus.sfm > > but the baseline is not coherent. Using DejaVuSansMono seems to be > working better: > > otf2bdf -c C -p 32 -r 100 > /usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf > > /tmp/DejaVuSansMono.bdf > bdf2psf --fb --width 32 /tmp/DejaVuSansMono.bdf > /usr/share/bdf2psf/standard.equivalents ascii.set 256 > /tmp/DejaVuSansMono.psf /tmp/DejaVuSansMono.sfm > > (I'm adding a new --width parameter to bdf2psf to specify the expected > width since AVERAGE_WIDTH as set by otf2bdf doesn't really tell) > > Samuel
Bug#1069791: console-setup: Build larger console fonts for HiDPI/accessibility with future 6.9 kernels
Package: console-setup Version: 1.226 Severity: wishlist Dear Maintainer, Linux kernel 6.9+ will support larger font sizes for HiDPI screens. This is probably aimed at "more than 4k" monitors, but for accessibility reasons it would be really useful to have larger sizes available sooner for those of us already have 4k sorts of screens. Perhaps this might best be done by putting those huge-sized fonts in an appropriately named -huge fonts package? I'll leave the implementation details to you, this is just a request for the fonts to be created. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages console-setup depends on: ii console-setup-linux 1.226 ii debconf [debconf-2.0] 1.5.86 ii keyboard-configuration 1.226 ii xkb-data2.41-2 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales2.37-18 ii sysvinit-utils [lsb-base] 3.09-1 Versions of packages keyboard-configuration depends on: ii debconf [debconf-2.0] 1.5.86 ii liblocale-gettext-perl 1.07-7 ii xkb-data2.41-2 Versions of packages console-setup-linux depends on: ii init-system-helpers 1.66 ii kbd 2.6.4-2 ii keyboard-configuration 1.226 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools pn gnome-control-center ii kbd 2.6.4-2 ii systemd 255.4-1+b1 -- debconf information: keyboard-configuration/unsupported_config_options: true keyboard-configuration/ctrl_alt_bksp: false keyboard-configuration/unsupported_options: true console-setup/guess_font: keyboard-configuration/unsupported_layout: true console-setup/fontsize: 16x32 * console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages keyboard-configuration/optionscode: console-setup/framebuffer_only: keyboard-configuration/layout: console-setup/fontsize-text47: 16x32 (framebuffer only) * console-setup/charmap47: UTF-8 keyboard-configuration/other: keyboard-configuration/model: Generic 105-key PC keyboard-configuration/switch: No temporary switch * console-setup/fontsize-fb47: 16x32 (framebuffer only) keyboard-configuration/store_defaults_in_debconf_db: true keyboard-configuration/toggle: No toggling console-setup/store_defaults_in_debconf_db: true debian-installer/console-setup-udeb/title: keyboard-configuration/variantcode: * keyboard-configuration/variant: English (US) console-setup/use_system_font: keyboard-configuration/layoutcode: us keyboard-configuration/unsupported_config_layout: true keyboard-configuration/compose: No compose key console-setup/codesetcode: Lat15 * console-setup/fontface47: TerminusBold keyboard-configuration/altgr: The default for the keyboard layout keyboard-configuration/xkb-keymap: us keyboard-configuration/modelcode: pc105
Bug#1068528: xfce4-settings: xfce4-find-cursor does nothing without … sudo?
Package: xfce4-settings Version: 4.18.3-1+b1 Severity: normal Dear Maintainer, Discovered that xfce4-find-cursor (an accessibility feature) does not work without the use of sudo. Permissions issue of some sort? Should this program be installed with some sgid to access something? I can't imagine what offhand. This isn't documented as far as I can tell. Someone asked why it was necessary to run this with root privs two years ago on askubuntu (no answer) and that's all I could find amongst the AI trash and unrelated responses. If there's some optional permissions I should be changing to make this work, the changes aren't documented and there don't appear to be any measures in place to preserve those changes in maintainer scripts from a quick glance. If it turns out to matter, Xorg with xfwm4 on AMD (6700 XT) using open source drivers. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xfce4-settings depends on: ii exo-utils4.18.0-1+b2 ii libatk1.0-0t64 2.52.0-1 ii libc62.37-15.1 ii libcairo-gobject21.18.0-3 ii libcairo21.18.0-3 ii libcolord2 1.4.7-1+b1 ii libexo-2-0 4.18.0-1+b2 ii libfontconfig1 2.15.0-1.1 ii libgarcon-1-04.18.1-1+b2 ii libgarcon-common 4.18.1-1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b2 ii libglib2.0-0t64 2.78.4-6 ii libgtk-3-0t643.24.41-4 ii libnotify4 0.8.3-1+b1 ii libpango-1.0-0 1.52.1+ds-1 ii libpangocairo-1.0-0 1.52.1+ds-1 ii libupower-glib3 1.90.2-8+b1 ii libx11-6 2:1.8.7-1 ii libxcursor1 1:1.2.1-1 ii libxfce4ui-2-0 4.18.4-1+b1 ii libxfce4util74.18.1-2+b1 ii libxfconf-0-34.18.1-1+b2 ii libxi6 2:1.8.1-1 ii libxklavier165.4-5+b1 ii libxrandr2 2:1.5.4-1 ii xfce4-helpers4.18.3-1+b1 ii xfconf 4.18.1-1+b2 Versions of packages xfce4-settings recommends: ii colord 1.4.7-1+b1 ii x11-utils 7.7+6+b1 ii xiccd 0.3.0-2+b1 xfce4-settings suggests no packages. -- no debconf information
Bug#1067925: RFS: fastfetch/2.8.10 [ITP] -- Fastfetch is a neofetch-like tool for fetching system information and displaying them in a pretty way.
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "fastfetch": * Package name : fastfetch Version : 2.8.10 Upstream contact : [fill in name and email of upstream] * URL : https://github.com/fastfetch-cli/fastfetch * License : Expat * Vcs : [fill in URL of packaging vcs] Section : universe/utils The source builds the following binary packages: fastfetch - Fastfetch is a neofetch-like tool for fetching system information and displaying them in a pretty way. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/fastfetch/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/f/fastfetch/fastfetch_2.8.10.dsc Changes for the initial release: fastfetch (2.8.10) unstable; urgency=medium . * Init debian support Regards, -- Carter Li
Bug#1067743: RFP: librust-parse-display-dev -- Rust library that provides derive macro Display and FromStr
Package: wnpp Severity: wishlist * Package name: librust-parse-display-dev Version : 0.9 Upstream Contact: https://github.com/frozenlib * URL : https://crates.io/crates/parse-display * License : Apache-2.0/MIT (dual license) Programming Lang: Rust Description : Rust library that provides derive macro Display and FromStr parse-display provides derive macro Display and FromStr. These macros use common helper attributes to specify the format. This package is a new dependency for bcachefs-tools, ideally someone else should package it since I'm not familiar with Rust packaging, but I'll take a stab at it later on if no one else gets to it.
Bug#1065533: RFP: libsdl2-pango -- pango extension for sdl2
Package: wnpp Severity: wishlist * Package name: libsdl2-pango Version : 2.1.5 Upstream Contact: https://github.com/markuskimius * URL : https://github.com/markuskimius/SDL2_Pango * License : LGPL-2.1+ Programming Lang: C Description : pango extension for sdl2 This is needed as a depencency for Tuxpaint. Upstream contains an included debian directory with existing packaging that likely just needs to be cleaned up / updated a bit for the archive.
Bug#1064380: Aw: Re: Bug#1064380: RFS: jpeginfo/1.7.1-1 [Team] -- Prints information and tests integrity of JPEG/JFIF files
I'm not on your fucking team. And I said stop sending this fucking spam. Wannabee ninja motherfucker. On 2/28/2024 3:40 AM, xiao sheng wen (肖盛文) wrote: 在 2024/2/27 16:26, Bastian Germann 写道: The string " $Id: hash $" in "jpeginfo.h" file is almost not change in upstream. Even this string changed in upstream, it will not affect do deb package. "almost no change" is a change and dpkg-source will not create a source package for me. Do you meet this question? How to reproduce it? I don't understand it now. How are you able to create one from the released tarball? When upstream release a new version, do a tag on one commit, The "jpeginfo.h" file is not change in this tag version, is it? -- 肖盛文 xiao sheng wen https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统 Debian QA page:https://qa.debian.org/developer.php?login=atzlinux%40sina.com Debian salsa:https://salsa.debian.org/atzlinux-guest GnuPG Public Key: 0x00186602339240CB
Bug#1064318: bash: manpage lists incorrect filename (/etc/bash.bash.logout)
Package: bash Version: 5.2.21-2 Severity: minor Dear Maintainer, The manpage for base states: ``` FILES /bin/bash The bash executable /etc/profile The systemwide initialization file, executed for login shells /etc/bash.bashrc The systemwide per-interactive-shell startup file /etc/bash.bash.logout The systemwide login shell cleanup file, executed when a login shell exits ``` This is incorrect, bash invokes /etc/bash.bash_logout. Debian doesn't provide a bash.bash_logout so I know about this because I was tinkering with adding stuff to these to find bash's config files in XDG-standard locations, if they exist, since I keep ~/.config in git. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bash depends on: ii base-files 13 ii debianutils 5.16 ii libc62.37-15 ii libtinfo66.4+20240113-1 Versions of packages bash recommends: ii bash-completion 1:2.11-8 Versions of packages bash suggests: ii bash-doc 5.2.21-2 -- Configuration Files: /etc/bash.bashrc changed [not included] -- no debconf information
Bug#1060256: Please enable the Rust parts
On 2024/02/14 11:55, Steinar H. Gunderson wrote: Fair enough, do you want to do the honor as the maintainer? Or should I change the upload's version number to 24+really1.4.2~git(etc).? Since you made the change, I think you should own it. thanks again! -Jonathan
Bug#1060256: Please enable the Rust parts
On 2024/02/13 23:53, Steinar H. Gunderson wrote: On Tue, Feb 06, 2024 at 11:55:55AM +0200, Faidon Liambotis wrote: Still required. I uploaded that last week, currently sitting in NEW. Now that this is through NEW, I uploaded an NMU to DELAYED/7-day. I see that this package is in LowThresholdNmu, but given that it adds an epoch, I'm giving everyone a week to speak up if they feel this is wrong :-) Thanks for the work, although Debian policy requires consensus from debian-devel before bumping an epoch: https://www.debian.org/doc/debian-policy/ch-controlfields.html#version -Jonathan
Bug#1063686: installation-reports: GUI checkbox in high contrast dark mode isn't high contrast
Package: installation-reports Severity: wishlist Either normal/a11y or wishlist depending how you wanna call it. I normally use the slang version of the Debian installer. Because I'm using a 14" 1080p portable monitor here, I decided to use the GUI. In dark mode because albino. Bright = pain. Sub-optimal install for me, will switch to ssh as soon as the network's configured. Went to select installer components because parted pls, but when I selected it, I didn't see that it was selected at first. That's odd. Then I looked closer and … oh yeah, I guess it is selected. Just this theme/widget set uses a very small/thin checkmark inside the box. Basically, I'd like a checkbox whose checked/unchecked states are more visually not the same. Particularly important in the dark mode, since that's intended to be high contrast for accessibility reasons. (Which is why I was using it…) Suggest a bigger/bolder checkmark might be the path of least resistance for a fix. Boot method: usb Image version: https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.5.0-amd64-netinst.iso Date: Sat, 10 Feb 2024 17:54:18 -0800 (in the middle of installing now) Machine: Ryzen 3000 series with B450 chipset Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect media: [O] Load installer modules: [?] ← Here's where I noticed the problem
Bug#1061330: calamares: identified for time_t transition but no ABI in shlibs
Hi Jarrah
On 2024/02/01 11:37, Jarrah Gosbell wrote:
As much as I'd love Calamares to start shipping a stable ABI, I think we
can probably get away here with just the rebuild. Is there an order that
is required for these rebuilds? I'm currently preparing an upload for
calamares-{extensions,settings-mobian} and would hold it back if
calamares needs to go first.
I've uploaded a new calamares about a week ago, so I think you can go
ahead with the extensions and this bug can be closed.
-Jonathan
Bug#1061595: Debian Live 12.4.0 AMD64 Xfce Fails to Start Its Graphical Environment
I couldn't reproduce the xfce issue, it started just fine on a Dell Optiplex 7010. Did you run sync after the dd completed?
Bug#1060508: marked as done (gamemode: Please switch Build-Depends to systemd-dev)
On 2024/01/25 17:46, Simon McVittie wrote: libdbus-dev isn't systemd or udev? Hmm... seems like that was quite a brainfart on my part. The request was to replace the B-D on systemd with systemd-dev, without altering the B-D on libdbus-1-dev or libsystemd-dev. Fixed and uploaded! -Jonathan
Bug#996432: ITS: newlib
Package: libnewlib-arm-none-eabi Version: 3.3.0-1.3 Followup-For: Bug #996432 Hi John, Your ITS was posted quite a long time ago and the maintainer is utterly MIA on this package. It's absolutely breaking stuff so that gcc-arm-none-eabi cannot be installed in trixie/sid alongside this package, which is required for the things you'd install that compiler for. Is this still something you're willing to work on? Is there some way folks can assist/help test/help package/something, or are you literally waiting on sponsors or … ? Happy to help if I can. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libnewlib-arm-none-eabi depends on: ii libnewlib-dev 3.3.0-1.3 Versions of packages libnewlib-arm-none-eabi recommends: ii gcc-arm-none-eabi 15:12.2.rel1-1 ii libstdc++-arm-none-eabi-newlib 15:12.2.rel1-1+23 Versions of packages libnewlib-arm-none-eabi suggests: pn libnewlib-doc -- no debconf information
Bug#1037299: (no subject)
Hey Patrick On 2024/01/03 12:37, Patrick Schleizer wrote: Didn't work for me but this did: https://forum.xfce.org/viewtopic.php?id=16357 What did you do from there that made it work? We set the metadata bit from a script on the live image too, but it doesn't seem to have any effect. -Jonathan
Bug#1057295: bcachefs-tools: breaks "mount" if the package is installed
Hi On 2023/12/02 22:22, Adam Borowski wrote: A simple workaround would be to just drop the /sbin/mount.bcachefs symlink until rust pieces are back. But alas, I see that the helper is needed for I've now done so, and uploaded it to experimental. At least on my system, things seem to work fine after a reboot once this package is installed. -Jonathan
Bug#1059159: foliate: Foliate 4-1 is actually 2.6.4, restores segfaults
Whoah, what in *the* world happened here!? I'll check this out tomorrow morning first thing, that seems very, very odd, thanks for the report, I did run it to check that it works and opened a book, but didn't immediately notice anything weird at that time. -Jonathan
Bug#1058592: LXD licensing changes and future for Debian packaging
Hi Matthias On 2023/12/14 00:19, Mathias Gibbens wrote: Other thoughts or opinions? Thanks for the details and thoughtful synopsis! Yep, there's a bunch of things to still figure out, and a lot can still happen in the next year, but in general it all seems like a general good direction for now. thanks! -Jonathan
Bug#1058592: please consider switching to new upstream source: incus
Source: lxd Version: 5.0.2-6 Severity: wishlist X-Debbugs-Cc: Previously, Canonical removed LXD from the community maintained Linux Containers project, and as in-house contributors moved on / resigned, Canonical removed their commit access to the LXD project hosted at Canonical. The original Linux Containers upstream project, along with contributors from other distributions launched the Incus project, a fork of LXD that is community maintained. LWN covered this before: https://lwn.net/Articles/940684/ Now, Canonical has relicensed LXD, including relicensing for contributions that they don't own, in addition to that, they require CLA acceptance for all contributions, which might not have been a big deal if it wernen't for their history. Some more details on stgraber's blog: https://stgraber.org/2023/12/12/lxd-now-re-licensed-and-under-a-cla/ I suggest looking into Incus and consider switching to that as the LXD implementation packaged in Debian. thanks!
Bug#1053995: Info received (ITP: fastfetch -- like neofetch, but much faster because written in C)
Friendly ping > 2023年10月16日 14:39，Debian Bug Tracking System 写道： > > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > w...@debian.org > > If you wish to submit further information on this problem, please > send it to 1053...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 1053995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053995 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems
Bug#1055032: Please update to latest upstream version
Package: python3-textual Severity: normal X-Debbugs-Cc: Dear maintainer, The current version of python3-textual in Debian is quite out of date, and it's not possible to run newer textual apps with it anymore., Please upgrade to the latest upstream version (currenly (0.40.0) so that this package can be useful again. thanks -Jonathan -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-2-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), LANGUAGE=en_ZA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1053995: ITP: fastfetch -- like neofetch, but much faster because written in C
Package: wnpp Severity: wishlist * Package name: fastfetch Version : 2.1.2 Upstream Author : fastfetch-cli * URL : https://github.com/fastfetch-cli/fastfetch DEB : https://github.com/fastfetch-cli/fastfetch/releases/download/2.1.2/fastfetch-2.1.2-Linux.deb * License : MIT Programming Lang: C Description : Like neofetch, but much faster because written in C Fastfetch is a neofetch-like tool for fetching system information and displaying them in a pretty way. It is written mainly in C, with performance and customizability in mind. Currently, Linux, Android, FreeBSD, MacOS and Windows 7+ are supported.
Bug#1053995: Acknowledgement (ITP: fastfetch -- like neofetch, but much faster because written in C)
I am sorry but I did not change the project name. Correction: * Package name : fastfetch From: Debian Bug Tracking System Sent: Sunday, October 15, 2023 10:15:03 PM To: Li Carter Subject: Bug#1053995: Acknowledgement (ITP: fastfetch -- like neofetch, but much faster because written in C) Thank you for filing a new Bug report with Debian. You can follow progress on this Bug here: 1053995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053995. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): w...@debian.org If you wish to submit further information on this problem, please send it to 1053...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1053995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053995: ITP: fastfetch -- like neofetch, but much faster because written in C
Package: wnpp Severity: wishlist * Package name : xournalpp Version : 2.1.2 Upstream Author : fastfetch-cli * URL : https://github.com/fastfetch-cli/fastfetch DEB : https://github.com/fastfetch-cli/fastfetch/releases/download/2.1.2/fastfetch-2.1.2-Linux.deb * License : MIT Programming Lang : C Description : Like neofetch, but much faster because written in C Fastfetch is a neofetch-like tool for fetching system information and displaying them in a pretty way. It is written mainly in C, with performance and customizability in mind. Currently, Linux, Android, FreeBSD, MacOS and Windows 7+ are supported.
Bug#1053106: please create a debian-za list for our Debian local user group in South Africa
On 2023/09/27 17:11, Jonathan Carter wrote: Name: debian-za Hi, any news on my request?
Bug#1053106: please create a debian-za list for our Debian local user group in South Africa
Package: lists.debian.org Severity: wishlist Hi I'm requesting a new list as per https://www.debian.org/MailingLists/HOWTO_start_list Purpose and intended audience: We're in a need of a list to co-ordinate activities for the Debian South Africa Local Group. We have several members already and co-ordinating over individual emails have become a pain. Name: debian-za Rationale: To have a list where we can co-ordinate local events, point new potential developers in the right direction, and to provide basic training or support. Short description: discussion list for the Debian South Africa Local Group Long Description: This list is used by the South African Local Group to: - Discuss local events, like Debian Day, Bug squashing parties, sprints, braais and mini-debconfs - Help local contributors to get set up to be a contributor (sign up to salsa, wiki, set up reportbug, etc) - Provide some basic support or training to new users Category: users Subscription policy: open Web archive: yes thanks, -Jonathan
Bug#1051739: Package is uninstallable, bug unacknowledged, therefore release critical
Control: severity -1 grave I didn't do this when filing the bug since ages ago it was considered impolite for end-users to set severity and particularly to set a severity above important. But it's been a week without acknowledgment or fix, and it is release critical even if it's a contrib package that isn't for the Holy Gnoman Empire DE. Joseph
Bug#1051739: 1.26.0-3 uninstallable due to nonexistent package
Package: caja-dropbox Version: 1.26.0-3 Severity: normal -3 of this package cannot be installed because it depends on: > --- libayatana-appindicator1 | libappindicator1 (UNAVAILABLE) libayatana-appindicator3-1 is available on bookworm, but not testing or sid. Adding this was done apparently to fix an Ubuntu bug, but it completely broke the package installation for Debian. Actually, it broke the package on Ubuntu too—the only version of Ubuntu that has libayatana-appindicator1 is 22.10. It's not in 23.04 and won't be in 23.10 either. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-0-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages caja-dropbox (1.26.0-2) depends on: ii dbus-x11 1.14.10-1 ii gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1 ii gir1.2-glib-2.0 1.78.0-1 ii gir1.2-gtk-3.03.24.38-5 ii gir1.2-pango-1.0 1.51.0+ds-2 ii libc6 2.37-8 ii libcaja-extension11.26.1-1 ii libglib2.0-0 2.78.0-1 ii libgtk-3-03.24.38-5 ii policykit-1 123-1 ii procps2:4.0.3-1 ii python3 3.11.4-5+b1 ii python3-gi3.44.1-2 ii python3-gpg 1.18.0-3+b1 caja-dropbox recommends no packages. Versions of packages caja-dropbox suggests: ii caja 1.26.1-1 -- no debconf information
Bug#1050746: RM: gnome-shell-extension-pixelsaver -- ROM; no longer works in gnome, not fixed upstream
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: gnome-shell-extension-pixelsa...@packages.debian.org Control: affects -1 + src:gnome-shell-extension-pixelsaver Dear FTP team Please remove gnome-shell-extension-pixelsaver It no longer works in GNOME, at least, with most apps, and upstream doesn't seem to release any new releases/fixes for it. thanks, -Jonathan
Bug#1043226: debian-installer: Please consider moving root user setup to expert install, or change text
Source: debian-installer Version: 20230607+deb12u1 Severity: wishlist Dear Maintainer, When setting up users and passwords in debian-installer in a default install, it prompts a user to set up a root password. In d-i, this works very different than in other installers, which causes quite a bit of confusion for users. Firstly, the instructions start off with "You need to set a password for 'root'", followed by seemingly uninteresting text about what a good password should be, which makes it incredibly easy for users to miss the part that sudo won't be set up for the first user. So, many users, and especially newcomers to Debian, follow the instructions in the first line and are then surprised when they can't use sudo from their user from their newly installed system. Would it perhaps make more sense to move the root password setup to the expert install d-i preseed entirely? Since this is likely only something that expert users would require in the first place? Either that, or move the explanation of what happens upward so that it's more prominent and not so easy to miss. In the latter case, it might also be worth while changing the first line that says "you need to..." so that user won't feel compelled to immediately start typing a root password and click on next. Thank you for considering, -Jonathan
Bug#1041358: web-ui downloads extentionless page without
On Mon, Jul 17, 2023, at 23:53, Christian Marillat wrote: > On 17 juil. 2023 15:39, "T. Joseph Carter" > wrote: > >> Package: qbittorrent-nox >> Version: 4.5.4-1 >> Severity: important >> >> The primary (really only) way to use qbittorrent-nox is via the web UI. >> This works in stable (4.5.2) as expected, but in sid it downloads a file >> with a name like "4Az117Jo" (random), no extension, and no MIME type. >> Firefox, Chromium, and Brave all just save the file without displaying >> it—it's the web UI login page as expected. > > The same bug has been reported and fixed (user issue). > > https://bugs.debian.org/1037548 That is indeed what is happening. I do not know the source of this issue—I certainly never created this bogus MIME database entry myself, and it has been reported upstream numerous times now apparently. I sort of think that means there's an issue that ought to be fixed, but I do not know whose issue it is anymore. The solution described here solved the problem for now: https://github.com/qbittorrent/qBittorrent/issues/15316#issuecomment-964855980 Joseph
Bug#1041358: web-ui downloads extentionless page without
Package: qbittorrent-nox Version: 4.5.4-1 Severity: important The primary (really only) way to use qbittorrent-nox is via the web UI. This works in stable (4.5.2) as expected, but in sid it downloads a file with a name like "4Az117Jo" (random), no extension, and no MIME type. Firefox, Chromium, and Brave all just save the file without displaying it—it's the web UI login page as expected. This is definitely a problem for how the -nox package is used (and affects the GUI package as well, but it would be Severity: normal for that package), and I've filed this as issue #19330 against the qBittorrent upstream on Github. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qbittorrent-nox depends on: ii libc62.37-6 ii libgcc-s113.1.0-8 ii libqt6core6 6.4.2+dfsg-11 ii libqt6network6 6.4.2+dfsg-11 ii libqt6sql6 6.4.2+dfsg-11 ii libqt6sql6-sqlite6.4.2+dfsg-11 ii libqt6xml6 6.4.2+dfsg-11 ii libssl3 3.0.9-1 ii libstdc++6 13.1.0-8 ii libtorrent-rasterbar2.0 2.0.9-1 ii zlib1g 1:1.2.13.dfsg-1 qbittorrent-nox recommends no packages. qbittorrent-nox suggests no packages. -- no debconf information
Bug#1041207: debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE
I want to echo what Simon said, please don't partake in commit ping-pong, it is unbecoming of a Debian Developer, and not the correct course of action if you disagree with something. It also reflects poorly on the project, so please refrain from doing so, even if you don't agree with how decisions are made. -Jonathan
Bug#1041192: Recommends: exuberant-ctags, not ctags?
Package: seascope Version: 0.9+8a669e0e-3 Severity: normal I've noted that seascope Recommends: exuberant-ctags which for the longest time was the only form of ctags in Debian. universal-ctags now exists as an alternative. Might any ctags be used for seascope or is there a particular reason to prefer exuberant-ctags? -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages seascope depends on: ii python3 3.11.4-3 ii python3-pyqt55.15.9+dfsg-1 ii python3-pyqt5.qsci 2.13.3+dfsg-3 ii python3-pyqt5.qtsvg 5.15.9+dfsg-1 Versions of packages seascope recommends: ii cscope 15.9-1 pn exuberant-ctags ii id-utils 4.6.28-20200521ss15dab+b1 seascope suggests no packages. -- no debconf information
Bug#1040221: toot: auth output needs a raw option
Hi On 2023/07/03 19:51, Sandro Tosi wrote: It would be nice if you could report all the issues you opened upstream at the link above and forward (https://www.debian.org/Bugs/server-control#forwarded) the debian bugs to the upstream once. +1, that would be ideal, we don't write code for toot or add new features for it in Debian, we package the upstream version, and might carry some bug fixes in the form of patches until they're fixed upstream, but other than that, I suggest filing ideas for improvement on the upstream bug tracker. thanks and keep well! -Jonathan
Bug#1039889: recommends old ffmpeg libs
Package: pqiv Version: 2.12-1+b1 Severity: normal The libavcodec and friends versions pqiv currently expects to use are not available in stable, let alone unstable. Might be fixed by recompile? -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pqiv depends on: ii libc6 2.36-9 ii libcairo2 1.16.0-7 ii libglib2.0-0 2.74.6-2 ii libgtk-3-03.24.37-2 ii libx11-6 2:1.8.6-1 Versions of packages pqiv recommends: ii libarchive13 3.6.2-1 pn libavcodec58 pn libavformat58 pn libavutil56 ii libgdk-pixbuf-2.0-02.42.10+dfsg-1+b1 ii libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6 ii libpoppler-glib8 22.12.0-2+b1 pn libswscale5 ii libwebp7 1.2.4-0.2 pqiv suggests no packages. -- no debconf information
Bug#1037936: Qt6: Dialog minimum size larger than screen
Package: qbittorrent Version: 4.5.3-2 Severity: normal Tags: a11y upstream The new Qt6 version of qBittorrent apparently does a better job reading my font size settings from XFCE. The result is that fonts are scaled up in a way that's comfortably easier for a legally blind reader … except the torrent options dialog no longer fits on screen. I've tried shrinking this to fit, but the minimum size possible still has to fit everything the dialog contains within that minimum dialog size. A solution to this might be to place the dialog's controls inside a widget which can scroll if the dialog is smaller than its contents. I don't really code Qt stuff, so I don't know what widget that would be, but I'm betting the devs do. Workaround for now is to know how to grab a window by something other than the titlebar in your WM or whatever one does under Wayland and move the titlebar offscreen so you can reach the options and buttons at the bottom of the larger than the screen dialog. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qbittorrent depends on: ii libc62.36-9 ii libgcc-s113.1.0-5 ii libqt5sql5-sqlite5.15.8+dfsg-12 ii libqt6core6 6.4.2+dfsg-11 ii libqt6dbus6 6.4.2+dfsg-11 ii libqt6gui6 6.4.2+dfsg-11 ii libqt6network6 6.4.2+dfsg-11 ii libqt6sql6 6.4.2+dfsg-11 ii libqt6widgets6 6.4.2+dfsg-11 ii libqt6xml6 6.4.2+dfsg-11 ii libssl3 3.0.9-1 ii libstdc++6 13.1.0-5 ii libtorrent-rasterbar2.0 2.0.9-1 ii zlib1g 1:1.2.13.dfsg-1 qbittorrent recommends no packages. qbittorrent suggests no packages. -- no debconf information
Bug#1037391: debian-installer: xorg configuration fails when booting d-i graphical mode on netinst iso under virtualbox
On 2023/06/12 12:51, Jonathan Carter wrote: I can't copy and paste from my virtualbox screen, but will add a screenshot in a reply. Screenshot attached.
Bug#1037391: debian-installer: xorg configuration fails when booting d-i graphical mode on netinst iso under virtualbox
Source: debian-installer Version: 20230607 Severity: normal Dear Maintainer, When booting the debian-12.0.0-amd64-netinst.iso image in VirtualBox (7.0.8-dfsg-2 from unstable/contrib) under UEFI and selecting the Graphical Install (default) option, Xorg fails to start, apparently due to being incorrectly configured or incorrectly detecting the hardware. I can't copy and paste from my virtualbox screen, but will add a screenshot in a reply. -Jonathan
Bug#1037123: calamares-settings-debian: 'Minimal HD space required' too small for some live images
I agree that 10GB is way too small, will bump it for the point release and also take some space in to consideration for upgrades.
Bug#1037118: installation-reports: booting to d-i does not complete on Samsung Galaxy Book (arm64 laptop)
Package: installation-reports Severity: normal Boot method: USB Image version: https://cdimage.debian.org/cdimage/bookworm_di_rc4/arm64/iso-cd/debian-bookworm-DI-rc4-arm64-netinst.iso Date: 2023-06-05 Machine: Samsung Galaxy Book Go 5G Partitions: n/a Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] GRUB starts fine, when selecting either Install or Graphical Install, booting halts with just a static "_" on the display. I'll try to troubleshoot this a bit further and attach more info to the bug, this is a student's laptop so I'm not sure how long I'll have access to it.
Bug#1035904: What does merged /usr bring us
On 2023/05/15 20:26, Sam Hartman wrote: I want to stress that I'm not a huge fan of merged /usr, and I know you've encouraged me not to argue from a devil's advocate position in the past. And this is where I stop reading any further. To merge or not to merge is no longer an interesting or more importantly, a relevant discussion. The project has made the choice to implement it, after we've been one of the last major distributions to hold out on implementing it. Sure, it's been bumpy, and there's potential downsides, but none of the technical problems are as harmful as still trying to make this a debate. So, please, file bugs or fix bugs and support the people who need to complete the remaining bits of merged-/usr, or otherwise please move on. -Jonathan
Bug#1035749: related bug
https://gitlab.gnome.org/GNOME/mutter/-/issues/2723 another related or possible dup upstream bug
Bug#1035749: Related bug
It also may be https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2012100
Bug#1035749: mutter: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context()
Package: mutter Version: 44.0-2ubuntu4 Severity: important Dear Maintainer, After upgrading my ubuntu system to 23.04, any time I pull a tab off of a firefox browser, I risk the chance of X11 crashing. I generally hit this issue 6+ times a day. To minimize this, I attempt to not move tabs around, but this has been a part of my browser usage for years. Using coredumpctl, I'm seeing the same callstack as https://gitlab.gnome.org/GNOME/mutter/-/issues/2708 There's a downstream ubuntu bug: https://launchpad.net/bugs/2012230 I asked when ubuntu would incorporate the fix here: https://answers.launchpad.net/ubuntu/+source/mutter/+question/706514 It was suggested I write a debian bug because ubuntu incorporates mutter updates from debian. The mutter fix "wayland: Set compositor when creating MetaWaylandDataSourceXWayland" is https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2956 and merged to main April 12 2023. I can see "wayland: Set compositor when creating MetaWaylandDataSourceXWayland" in 44.1. https://gitlab.gnome.org/GNOME/mutter/-/commits/44.1?search= I believe this is the ubuntu bump to 44.1 when that's available (fix made on April 25 2023): https://git.launchpad.net/mutter/commit/?id=28a6447ff060ae1fbac8f20a13908d6e230eddc2 -- System Information: Debian Release: bookworm/sid APT prefers lunar APT policy: (500, 'lunar') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.2.0-20-generic (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mutter depends on: ii adwaita-icon-theme 41.0-1ubuntu1 ii gnome-settings-daemon-common 44.0-1ubuntu1 ii gsettings-desktop-schemas 44.0-1ubuntu1 ii libc6 2.37-0ubuntu2 ii libgles2 1.6.0-1 ii libglib2.0-0 2.76.1-1 ii libmutter-12-0 44.0-2ubuntu4 ii libwayland-client0 1.21.0-1 ii mutter-common 44.0-2ubuntu4 ii zenity 3.44.0-1 mutter recommends no packages. Versions of packages mutter suggests: ii gnome-control-center 1:44.0-1ubuntu5 ii xdg-user-dirs 0.18-1 -- no debconf information
Bug#1035560: unblock: calamares-settings-debian/12.0.9-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: calamares-settings-deb...@packages.debian.org, k...@debian.org
Control: affects -1 + src:calamares-settings-debian
Please unblock package calamares-settings-debian
[ Reason ]
The method that LUKS encryption tools (cryptsetup, cryptset-initramfs,
keyutils) have changed. Prior to bookworm, these were included in the squashfs
system, so it was installed whether or not it was required, resulting in a
warning on unencrypted systems when update-initramfs were run.
By some happy accident due to updates in the live build system, these aren't
included in the squashfs image anymore, so we've added it to the media package
pool so that it could be installed only when required. This Calamares change
will install the required package only when LUKS have been configured.
[ Impact ]
If this isn't accepted, users who installed via the Calamares installer on
live media will not be able to boot their systems until they install
cryptsetup-initramfs (and potentially keyutils, depending on configuration)
from rescue media.
[ Tests ]
This package was tested manually on the latest live test build.
[ Risks ]
The fixes are trivial and has been tested, and once migrated, we'll test it
yet again asap on the latest installation media. We're also adding luks tests
to our standard live smoke testing to help catch a bug like this sooner in the
future.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ DebDiff ]
"""
diff -Nru calamares-settings-debian-12.0.8/CHANGELOG
calamares-settings-debian-12.0.9/CHANGELOG
--- calamares-settings-debian-12.0.8/CHANGELOG 2023-04-26 14:23:37.0
+0200
+++ calamares-settings-debian-12.0.9/CHANGELOG 2023-05-04 20:34:51.0
+0200
@@ -1,8 +1,15 @@
-[ 10.0.8 ]
+[ 12.0.9 ]
+
+ * Fix typos in version numbers for last two changelog entries
+ * Install cryptsetup-initramfs, cryptsetup and keyutils (only) when needed
+ (required due to these packages only now existing on package pool,
+not on the squashfs filesystem)
+
+[ 12.0.8 ]
* Do grub work within the chroot
-[ 10.0.7 ]
+[ 12.0.7 ]
* Enable os-prober /after/ grub has been installed.
diff -Nru calamares-settings-debian-12.0.8/debian/changelog
calamares-settings-debian-12.0.9/debian/changelog
--- calamares-settings-debian-12.0.8/debian/changelog 2023-04-26
14:25:34.0 +0200
+++ calamares-settings-debian-12.0.9/debian/changelog 2023-05-04
20:47:17.0 +0200
@@ -1,3 +1,10 @@
+calamares-settings-debian (12.0.9-1) unstable; urgency=medium
+
+ * New upstream release
+- Deal with changes in how luks tools are installed from live media
+
+ -- Jonathan Carter Thu, 04 May 2023 20:47:17 +0200
+
calamares-settings-debian (12.0.8-1) unstable; urgency=medium
* New upstream release
diff -Nru calamares-settings-debian-12.0.8/scripts/bootloader-config
calamares-settings-debian-12.0.9/scripts/bootloader-config
--- calamares-settings-debian-12.0.8/scripts/bootloader-config 2023-04-26
14:23:37.0 +0200
+++ calamares-settings-debian-12.0.9/scripts/bootloader-config 2023-05-04
20:34:51.0 +0200
@@ -2,22 +2,24 @@
CHROOT=$(mount | grep proc | grep calamares | awk '{print $3}' | sed -e
"s#/proc##g")
-# Set secure permissions for the initramfs if we're configuring
+# Install luks utilities if needed.
+# Also, set secure permissions for the initramfs if we're configuring
# full-disk-encryption. The initramfs is re-generated later in the
# installation process so we only set the permissions snippet without
# regenerating the initramfs right now:
if [ "$(mount | grep $CHROOT" " | cut -c -16)" = "/dev/mapper/luks" ]; then
echo "UMASK=0077" >
$CHROOT/etc/initramfs-tools/conf.d/initramfs-permissions
+chroot $CHROOT apt-get -y install cryptsetup-initramfs cryptsetup keyutils
fi
echo "Running bootloader-config..."
if [ -d /sys/firmware/efi/efivars ]; then
echo " * Installing grub-efi (uefi)..."
-DEBIAN_FRONTEND=noninteractive chroot $CHROOT apt-get -y install
grub-efi-amd64 cryptsetup keyutils
+DEBIAN_FRONTEND=noninteractive chroot $CHROOT apt-get -y install
grub-efi-amd64
else
echo " * install grub... (bios)"
-DEBIAN_FRONTEND=noninteractive chroot $CHROOT apt-get -y install grub-pc
cryptsetup keyutils
+DEBIAN_FRONTEND=noninteractive chroot $CHROOT apt-get -y install grub-pc
fi
# Re-enable os-prober:
"""
thanks,
-Jonathan
unblock calamares-settings-debian/12.0.9-1
Bug#1035357: unblock: calamares-settings-debian/12.0.5-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: calamares-settings-deb...@packages.debian.org Control: affects -1 + src:calamares-settings-debian Please unblock package calamares-settings-debian This change re-enables os-prober during installation on Debian live images when using Calamares, so that dual-booted systems will detect other operating systems. Sorry for the noise in the debdiff, it took a few times to get just right, the pertinent change is on the last lines. thanks, [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ debdiff ] """ diff -Nru calamares-settings-debian-12.0.5/CHANGELOG calamares-settings-debian-12.0.8/CHANGELOG --- calamares-settings-debian-12.0.5/CHANGELOG 2023-03-06 19:22:24.0 +0200 +++ calamares-settings-debian-12.0.8/CHANGELOG 2023-04-26 14:23:37.0 +0200 @@ -1,3 +1,15 @@ +[ 10.0.8 ] + + * Do grub work within the chroot + +[ 10.0.7 ] + + * Enable os-prober /after/ grub has been installed. + +[ 12.0.6 ] + + * Enable os-prober + [ 12.0.5 ] * Update sources.list to include non-free-firmware and backports diff -Nru calamares-settings-debian-12.0.5/debian/changelog calamares-settings-debian-12.0.8/debian/changelog --- calamares-settings-debian-12.0.5/debian/changelog 2023-04-04 09:51:03.0 +0200 +++ calamares-settings-debian-12.0.8/debian/changelog 2023-04-26 14:25:34.0 +0200 @@ -1,3 +1,17 @@ +calamares-settings-debian (12.0.8-1) unstable; urgency=medium + + * New upstream release +- Make grub changes in the correct place (within the chroot) + + -- Jonathan Carter Wed, 26 Apr 2023 14:25:34 +0200 + +calamares-settings-debian (12.0.7-1) unstable; urgency=medium + + * New upstream release +- Re-enable os-prober + + -- Jonathan Carter Wed, 26 Apr 2023 13:43:01 +0200 + calamares-settings-debian (12.0.5-2) unstable; urgency=medium * Depend on pkexec (Closes: #1033930) diff -Nru calamares-settings-debian-12.0.5/scripts/bootloader-config calamares-settings-debian-12.0.8/scripts/bootloader-config --- calamares-settings-debian-12.0.5/scripts/bootloader-config 2023-03-06 19:22:24.0 +0200 +++ calamares-settings-debian-12.0.8/scripts/bootloader-config 2023-04-26 14:23:37.0 +0200 @@ -19,3 +19,7 @@ echo " * install grub... (bios)" DEBIAN_FRONTEND=noninteractive chroot $CHROOT apt-get -y install grub-pc cryptsetup keyutils fi + +# Re-enable os-prober: +sed -i "s/#GRUB_DISABLE_OS_PROBER=false/# OS_PROBER re-enabled by Debian Calamares installation:\nGRUB_DISABLE_OS_PROBER=false/g" $CHROOT/etc/default/grub +chroot $CHROOT /usr/sbin/update-grub """ -Jonathan unblock calamares-settings-debian/12.0.8-1
Bug#1034607: xfce4-screensaver vs light-locker
Package: task-desktop-xfce Version: 3.72 Severity: normal Request to allow xfce4-screensaver at least as an alternative to light-locker. -- System Information: Debian Release: 12.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-7-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1033932: unblock: calamares-settings-debian/10.0.5-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: calamares-settings-deb...@packages.debian.org
Control: affects -1 + src:calamares-settings-debian
Please unblock package calamares-settings-debian
This addresses serious bug #1033930. At least on the KDE live image, pkexec
is no longer supplied by default. There may be other images that are affected
too.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
Debdiff:
"""
diff -Nru calamares-settings-debian-12.0.5/debian/changelog
calamares-settings-debian-12.0.5/debian/changelog
--- calamares-settings-debian-12.0.5/debian/changelog 2023-03-06
19:24:55.0 +0200
+++ calamares-settings-debian-12.0.5/debian/changelog 2023-04-04
09:51:03.0 +0200
@@ -1,3 +1,9 @@
+calamares-settings-debian (12.0.5-2) unstable; urgency=medium
+
+ * Depend on pkexec (Closes: #1033930)
+
+ -- Jonathan Carter Tue, 04 Apr 2023 09:51:03 +0200
+
calamares-settings-debian (12.0.5-1) unstable; urgency=medium
* New upstream release
diff -Nru calamares-settings-debian-12.0.5/debian/control
calamares-settings-debian-12.0.5/debian/control
--- calamares-settings-debian-12.0.5/debian/control 2022-05-09
12:00:25.0 +0200
+++ calamares-settings-debian-12.0.5/debian/control 2023-04-04
09:51:00.0 +0200
@@ -14,6 +14,7 @@
Depends: calamares,
cryptsetup,
keyutils,
+ pkexec,
qml-module-qtquick-window2,
qml-module-qtquick2,
${misc:Depends}
"""
unblock calamares-settings-debian/10.0.5-2
thanks,
-Jonathan
Bug#1033930: calamares-settings-debian: needs dependency on pkexec (which is no longer provided on KDE iso images)
Package: calamares-settings-debian Severity: important During testing of the RC1 live images, it was found that Calamares doesn't start on the KDE images. This was due to a missing pkexec, which was previously supplied on the KDE plasma desktop image. On the Debian configuration for Calamares, we should depend on pkexec. -- System Information: Debian Release: 12.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-7-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), LANGUAGE=en_ZA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages calamares-settings-debian depends on: pn calamares ii cryptsetup 2:2.6.1-3 ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 pn keyutils ii qml-module-qtquick-window2 5.15.8+dfsg-3 ii qml-module-qtquick2 5.15.8+dfsg-3 calamares-settings-debian recommends no packages. calamares-settings-debian suggests no packages.
Bug#1033227: unblock: live-tasks-non-free-firmware/12.0.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: live-tasks-non-free-firmw...@packages.debian.org Control: affects -1 + src:live-tasks-non-free-firmware Please unblock package live-tasks-non-free-firmware This is provides meta-packages on live systems to install non-free firmware packages on those systems. Sorry for it being so late, it depended on the firmware section itself existing and being populated. The package only provides the metapackages, for convenience, I'm including the control file below: """ Source: live-tasks-non-free-firmware Maintainer: Live Systems Maintainers Uploaders: Jonathan Carter Section: non-free-firmware/metapackages Priority: optional Build-Depends: debhelper-compat (= 13) Standards-Version: 4.6.2 Vcs-Browser: https://salsa.debian.org/live-team/live-tasks-non-free-firmware Vcs-Git: https://salsa.debian.org/live-team/live-tasks-non-free-firmware.git Rules-Requires-Root: no Package: live-task-non-free-firmware-pc Architecture: all Recommends: amd64-microcode, bluez-firmware, firmware-amd-graphics, firmware-atheros, firmware-brcm80211, firmware-intel-sound, firmware-ipw2x00, firmware-iwlwifi, firmware-linux, firmware-linux-nonfree, firmware-realtek, firmware-sof-signed, intel-microcode Suggests: vrms Description: selection of oft-used non-free-firmware shipped on live systems Provides non-free-firmware packages for Debian live systems. . Its dependencies, along with this package itself, is safe to remove, provided that your device does not depend on them in order to function. Package: live-task-non-free-firmware-server Architecture: all Recommends: firmware-bnx2, firmware-bnx2x, firmware-cavium, firmware-myricom, firmware-netronome, firmware-netxen, firmware-qlogic Suggests: vrms Description: provides firmware for server network and storage devices Provides non-free firmware packages for Debian live systems. . This package installs firmware packages for server devices. . Its dependencies, along with this package itself, is safe to remove, provided that your device does not depend on them in order to function. """ unblock live-tasks-non-free-firmware/12.0.1 thanks, -Jonathan
Bug#1033009: unblock: calamares-settings-debian/12.0.5-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: calamares-settings-deb...@packages.debian.org, Please alloq calamares-settings-debian (12.0.5-1) to migrate to testing, it contains the correct artwork for bookworm Control: affects -1 + src:calamares-settings-debian Please unblock package calamares-settings-debian It contains the correct artwork for bookworm. unblock calamares-settings-debian/12.0.5-1
Bug#1032867: suggests wx3.0-doc
Package: python3-wxgtk4.0 Version: 4.2.0+dfsg-2 Severity: minor This package still suggests: wx3.0-doc, perhaps wx3.2-doc is now intended? Severity: minor as you can obviously install it yourself, but given the 4.0/3.2 sort of confusion with wxWidgets and wxPython, it's worth fixing. -- System Information: Debian Release: 12.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-6-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-wxgtk4.0 depends on: ii libc6 2.36-8 ii libgcc-s1 12.2.0-14 ii libstdc++612.2.0-14 ii libwxbase3.2-13.2.2+dfsg-2 ii libwxgtk-gl3.2-1 3.2.2+dfsg-2 ii libwxgtk3.2-1 3.2.2+dfsg-2 ii python3 3.11.2-1 ii python3-numpy 1:1.24.2-1 ii python3-pil 9.4.0-1.1+b1 ii python3-six 1.16.0-4 python3-wxgtk4.0 recommends no packages. Versions of packages python3-wxgtk4.0 suggests: ii wx3.0-doc 3.0.5.1+dfsg-5 -- no debconf information
Bug#1032412: desktop-base: plymouth theme does not show any messages, affects: luks, live
Package: desktop-base Version: 12.0.5 Severity: important The latest plymouth theme for Debian 12 doesn't show any messages/prompts/fields. The consequences of this is that when you boot up, you don't see the prompt to decrypt your disk, so it appears that the boot process has frozen (until you press escape and see the console luks prompt). On live systems, when you reboot/shutdown, the user is prompted to remove the live media and press enter, but since this message is now not visibile, it appears that the system has frozen (until the user pressess enter). Marking as important, since this is quite a big regression. -Jonathan -- System Information: Debian Release: 12.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-3-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), LANGUAGE=en_ZA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages desktop-base depends on: ii fonts-quicksand 0.2016-2.1 ii librsvg2-common 2.54.5+dfsg-1 Versions of packages desktop-base recommends: ii plymouth-label 22.02.122-3 Versions of packages desktop-base suggests: pn gnome | kde-standard | xfce4 | wmaker -- no debconf information
Bug#1031734: ibus-braille-preferences crashes when run
Package: ibus-braille
Version: 0.3-7
Severity: important
Upon running ibus-braille-preferences, I get this error:
```
aki:~ $ ibus-braille-preferences
/usr/share/ibus-braille-preferences/main.py:24: PyGIWarning: Gtk was imported
without specifying a version first. Use gi.require_version('Gtk', '4.0') before
import to ensure that the right version gets loaded.
from gi.repository import Gtk
/usr/share/ibus-braille-preferences/main.py:26: PyGIWarning: IBus was imported
without specifying a version first. Use gi.require_version('IBus', '1.0')
before import to ensure that the right version gets loaded.
from gi.repository import IBus
Traceback (most recent call last):
File "/usr/share/ibus-braille-preferences/main.py", line 265, in
ibus_sharada_braille_preferences()
File "/usr/share/ibus-braille-preferences/main.py", line 36, in __init__
self.guibuilder.add_from_file("/usr/share/ibus-braille-preferences/ui.glade")
gi.repository.GLib.GError: gtk-builder-error-quark:
/usr/share/ibus-braille-preferences/ui.glade:75:52 Invalid property:
GtkBox.border_width (11)
```
I suspect PyGIWarning is the clue: This probably requires GTK+ 3.x, not
4.x, but it doesn't specify what it needs. Seems line 26 is also going
to cause a potential problem. I suspect judicious use of the following
three lines added to a couple source files will fix it:
```python
from gi import require_version
require_version('Gtk', '3.0')
require_version('IBus', '1.0')
```
At least, that was all it took to get the preferences applet to run.
Didn't test the abbreviation or language editor with similar patches.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ibus-braille depends on:
ii gir1.2-ibus-1.0 1.5.27-4
ii gir1.2-pango-1.0 1.50.12+ds-1
ii python3 3.11.1-3
ii python3-espeak0.5-5+b1
ii python3-gi3.42.2-3+b1
ii python3-louis 3.24.0-1
Versions of packages ibus-braille recommends:
ii python3-speechd 0.11.4-2
ibus-braille suggests no packages.
-- no debconf information
Bug#1024457: apt changelog failure
I don't know that it raises the priority to "serious", but by way of reason this one kind of needs to be fixed: apt's behavior has changed quite substantially over the past couple of decades or so. What version first supported each one? That's what the changelog is for, and arguably it ought to be somewhere you can get at it easily as an end user. The instructions for where to get it lead to themselves. I'd put this one in a should vs. must category for fixes, though I understand time is a somewhat limited commodity. Joseph
Bug#1023992: Please build Corsair Commander Pro module
Package: src:linux Version: 6.0.8-1 Severity: normal Request building CONFIG_SENSORS_CORSAIR_CPRO module: /boot/config-6.0.0-2-amd64:# CONFIG_SENSORS_CORSAIR_CPRO is not set /boot/config-6.0.0-3-amd64:# CONFIG_SENSORS_CORSAIR_CPRO is not set /boot/config-6.0.0-4-amd64:# CONFIG_SENSORS_CORSAIR_CPRO is not set This module provides hwmon functions for my CPU cooler. Thanks! -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: ASUS product_name: System Product Name product_version: System Version chassis_vendor: Default string chassis_version: Default string bios_vendor: American Megatrends Inc. bios_version: 4204 board_vendor: ASUSTeK COMPUTER INC. board_name: TUF GAMING X570-PRO WIFI II board_version: Rev X.0x ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480] Subsystem: ASUSTeK Computer Inc. Starship/Matisse Root Complex [1043:87c0] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] (prog-if 00 [Normal decode]) Subsystem: ASUSTeK Computer Inc. Starship/Matisse GPP Bridge [1043:87c0] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] DeviceName: Onboard IGD Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) Subsystem: ASUSTeK Computer Inc. FCH SMBus Controller [1043:87c0] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: nvme Kernel modules: nvme 02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream [1022:57ad] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 03:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a3] (prog-if 00 [Normal decode]) Subsystem: ASUSTeK Computer Inc. Matisse PCIe GPP Bridge [1043:87c0] Control: I/O+ Mem+ BusMaster+ S
Bug#1023979: ITP: python3-simpleobsws -- simple obs-websocket library in Python for people who just want JSON output
Package: wnpp Severity: wishlist Owner: Jonathan Carter X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: python3-simpleobsws Version : 1.3.1 Upstream Author : IRLToolkit Inc. * URL : https://github.com/IRLToolkit/simpleobsws * License : Expat Programming Lang: Python Description : simple obs-websocket library in Python for people who just want JSON output This software provides an asynchronous client for Python to control OBS via it's websocket gateway. I plan to maintain this package within the Debian Python team.
Bug#1023964: obs-studio version 28.0.1+dfsg1-3 is somewhat flakey, please upgrade to new upstream release
Package: obs-studio Version: 28.0.1+dfsg1-3 Severity: important Dear Maintainer, obs-studio version 28.0.1+dfsg1-3 (in testing/unstable) has some severe stability issues: * It drops frames * UI gets choppy * Preview modes get disabled when switching windows without it being possibly to enable again * Choppy audio recording I tried the latest version via flatpak and it's a lot better, please consider upgrading to the latest available release in Debian. -Jonathan -- System Information: Debian Release: bookworm/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-3-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), LANGUAGE=en_ZA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages obs-studio depends on: ii libavcodec59 7:5.1.2-1 ii libavdevice59 7:5.1.2-1 ii libavformat59 7:5.1.2-1 ii libavutil577:5.1.2-1 ii libc6 2.36-4 ii libcurl3-gnutls7.86.0-1 ii libfontconfig1 2.13.1-4.5 ii libfreetype6 2.12.1+dfsg-3 ii libgcc-s1 12.2.0-9 ii libjansson42.14-2 ii libluajit-5.1-22.1.0~beta3+git20220320+dfsg-4.1 ii libmbedcrypto7 2.28.1-1 ii libmbedtls14 2.28.1-1 ii libmbedx509-1 2.28.1-1 ii libobs028.0.1+dfsg1-3 ii libpci31:3.8.0-1 ii libpulse0 16.1+dfsg1-2+b1 ii libpython3.10 3.10.8-3 ii libqt5core5a 5.15.6+dfsg-2+b1 ii libqt5gui5 5.15.6+dfsg-2+b1 ii libqt5network5 5.15.6+dfsg-2+b1 ii libqt5svg5 5.15.6-2 ii libqt5widgets5 5.15.6+dfsg-2+b1 ii libqt5xml5 5.15.6+dfsg-2+b1 ii librist4 0.2.7+dfsg-1 ii libspeexdsp1 1.2.1-1 ii libsrt1.5-openssl 1.5.1-1 ii libstdc++6 12.2.0-9 ii libswscale67:5.1.2-1 ii libudev1 252.1-1 ii libv4l-0 1.22.1-5+b1 ii libx11-6 2:1.8.1-2 ii libx264-1642:0.164.3095+gitbaee400-2+b1 ii libxcb-composite0 1.15-1 ii libxcb-randr0 1.15-1 ii libxcb-shm01.15-1 ii libxcb-xfixes0 1.15-1 ii libxcb-xinerama0 1.15-1 ii libxcb11.15-1 ii python33.10.6-2 ii python3.10 3.10.8-3 Versions of packages obs-studio recommends: ii obs-plugins 28.0.1+dfsg1-3 Versions of packages obs-studio suggests: ii policykit-1122-1 pn v4l2loopback-dkms -- no debconf information
Bug#1023584: gnome-shell-extension-no-annoyance: please package v2 of this extension
Hi Andres, since it's been removed from Debian, I think it will be best if you convert the bug into an ITP and package it. For my purposes the DnD feature in Gnome works quite well and also gets rids of the distractions. I guess the extension allows some notifications but blocks some others?
Bug#778849: Is "wishlist" appropriate for this?
I have yet to investigate intrigeri's suggestions from 2017, however I would suggest that this is something that needs to be upgraded from wishlist in 2022, and here's the reason simply enough: root@aki:~# nvme smart-log /dev/nvme0 Smart Log for NVME device:nvme0 namespace-id: [..] unsafe_shutdowns: 106 [..] num_err_log_entries : 284 [..] root@aki:~# nvme smart-log /dev/nvme1 Smart Log for NVME device:nvme1 namespace-id: [..] unsafe_shutdowns: 121 [..] num_err_log_entries : 291 [..] Given that the frequency and number of SMART errors are deemed an indicator of drive health, that's bad. Also, improper shutdown on NVMe devices could be particularly problematic because they have caches and wear leveling and cleanup cycles that could happen any time the drive is "running" until a shutdown command is issued and responded to. There might actually be some risk of data corruption/loss. (I doubt it with commodity consumer SSDs, but Debian isn't just run on those.) For a few weeks, we tried on #debian to sort out the cause of the above errors. We thought NVMe drive quirk Linux doesn't support? Maybe Linux is issuing the shutdown command and not waiting long enough? There's Google bait suggesting that's a problem, and there's some BS factoids in dpkg I should remove the next time I connect to OFTC describing the "solution" which I've since discovered doesn't work. This was hard to test because obviously no logger is running at this point of the shutdown process. The root cause of the problem isn't an unknown quirk, it's that I have LVM on LUKS. (See what I did there?) Connected a drive with an unencrypted Debian system on it that mounted my main installation's /boot and even the LUKS/LVM root somewhere and never got a single unsafe shutdown despite multiple reboots/shutdowns. Because that temp install's root was not on LVM on LUKS backing. Dracut is a suboptimal solution. In part because after three days of trying to get it to boot my system, I've yet to see it do so, and because while there's lots of documentation for it, it's for other distributions, it's wrong, it's obsolete, or it's misleading. Including one rantthrough from 2017 that offers a profanity-laden survey of most of the others and why they don't work for Debian systems or at all. As far as I can tell you either need to significantly modify grub or switch to systemd-boot or set up Dracut to generate an EFI executable blob using files that aren't available on a Debian system or throw up my hands and go use Fedora until I understand Dracut enough to try and use it on Debian. Or something. Again: What sparse documentation exists is spotty, inconsistent, and at least five years out of date. Dracut is not how Debian does things, just like OpenRC and rEFInd are not how Debian does things. That's all there if you want to set it up, but you're not going to find many Debian resources on using it. I think unsafe shutdowns of NVMe devices is actually a bug. And I think it could cause data loss or corruption on more advnaced hardware than I'm using. There's a few options for addressing it and most of them become problems beyond initramfs-tools' scope. But this seven year old bug might be the path of least resistance. Joseph
Bug#1022103: Recent sgdisk problem in Debian (#1022103)
Hey Rod Thanks for all your previous help with gdisk, I was wondering if you could again look at another odd problem we've come across. When I uploaded gptfdisk 1.0.9 to Debian, it worked just fine, but something changed in Debian recently that now causes sgdisk to output the following: """ sgdisk --backup=/tmp/gdisk.bin /dev/sda Problem opening >�WV for reading! Error is 84. """ I suspected it might be something transient or an unannounced library transition, but when attempting a simple package rebuild, I then hit that again while the tests was running. Do you think you might be able to take a look at it? Might be easier for you to find the problem than me, but I'll poke at it too. Debian bug is at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022103 thanks and keep well! -Jonathan
Bug#1022103: gdisk: sgdisk produces only errors
On 2022/10/20 12:20, Uladzimir Bely wrote: From my investigations, the problem appeared after upgrading `libpopt0`. Previously there was a symlink `libpopt.so.0 => libpopt.so.0.0.1` and sgdisk worked well; now it's a `libpopt.so.0 => libpopt.so.0.0.1` and sgdisk fails. Most probably, `gdisk` package (that haven't get upgrade recently) should be simply rebuilt agains new version of `libpopt0` library. I just did a rebuild in pbuilder, doesn't seem that it did the trick, package building fails while doing tests for sgdisk, so this needs some more investigation. -Jonathan
Bug#1020942: debian-live: Reconsideration of Calamares installer on the next stable of Bookworm
Hi On 2022/09/29 08:52, Green wrote: Calamares installer should act properly to NOT install unneeded large amounts of locales by default; on the contrary other distribution's installer like in Fedora or MX Linux behave quite properly. I agree, this is among a few other issues, my #1 issue with Calamares on our live media right now. For what it's worth, debian-installer exhibits the same behaviour on our live media. If this problem is not easily solved, I would like to propose to replace the present calamares with Gazelle-installer developed by MX dev, instead. It seems that Gazelle-installer is quite a nice installer without such a problem. I took a look at it again, it solves /some/ of Calamares's problems, but it also brings in new ones. I think it's fine (and even great) if someone packages gazelle-installer for Debian, but since we're edging closer and closer to freeze date, I don't think we're likely to switch to it for Bookworm. By Trixie, I hope to have a much better long-term solution in place. -Jonathan
Bug#1020740: cpu-x needs to be recompiled against current libpci
Package: cpu-x Version: 4.3.1-1 Severity: important X-Debbugs-Cc: Mike Gabriel Cc to Mike Martin as Martin's email address no longer works because he no longer works for Canonical: https://www.omgubuntu.co.uk/2021/02/martin-wimpress-ubuntu-desktop-lead-leaving-canonical If there's another email address to reach him at, I don't know it. When I run cpu-x, messages about the wrong version of libpci being used are printed: tjcarter@aki:~$ cpu-x CPU-X:core.c:674: pci_access is not properly initialized: it is a common issue when CPU-X was built with a lower libpci version. Check that libpci 3.7.0 library is present on your system. Otherwise, please rebuild CPU-X. No kernel driver in use for graphic card at path (null) Your GPU user mode driver is unknown: 4.6 (Compatibility Profile) Mesa 22.2.0-rc3 The message even describes how to fix it: Recompile against the current libpci version. I did so, and: tjcarter@aki:~/Source/cpu-x/cpu-x-4.3.1$ obj-x86_64-linux-gnu/output/bin/cpu-x --dump There is no platform with OpenCL support (CL_PLATFORM_NOT_FOUND_KHR) >> CPU << * Processor * Vendor: AMD Code Name: Ryzen 7 (Matisse) : : Swap: 10.24 GiB / 65.00 GiB >> Graphics << * Card 0 * Vendor: AMD Driver: amdgpu UMD Version: Mesa 22.2.0-rc3 : Perhaps libpci needs to be tightened up to ensure that programs like cpu-x get rebuilt? It appears the ABI has changed incompatibly without bumping the soname, and this happens often enough to warrant an explanation of how to fix it in the downstream program. (That's gotta be frustrating for the devs!) -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cpu-x depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii libc62.34-8 ii libcairo21.16.0-6 ii libcpuid15 0.5.1+repack1-1+b1 ii libgdk-pixbuf-2.0-0 2.42.9+dfsg-1 ii libgl1 1.5.0-1 ii libglfw3 3.3.8-1 ii libglib2.0-0 2.74.0-1 ii libgtk-3-0 3.24.34-3 ii libncursesw6 6.3+20220423-2 ii libpango-1.0-0 1.50.10+ds-1 ii libpangocairo-1.0-0 1.50.10+ds-1 ii libpci3 1:3.8.0-1 ii libprocps8 2:3.3.17-7+b1 ii libtinfo66.3+20220423-2 ii procps 2:3.3.17-7+b1 cpu-x recommends no packages. cpu-x suggests no packages. -- no debconf information
Bug#1017380: RFP: rust-mimalloc -- drop-in global allocator wrapper around the mimalloc allocator
Package: wnpp Severity: wishlist X-Debbugs-Cc: j...@debian.org * Package name: rust-mimalloc Version : 0.1.29 Upstream Author : Octavian Oncescu * URL : https://docs.rs/mimalloc/latest/mimalloc/ * License : Expat Programming Lang: Rust Description : A drop-in global allocator wrapper around the mimalloc allocator Please consider packaging mimalloc for Rust. It's a drop-in global allocator wrapper around the mimalloc allocator. Mimalloc is a general purpose, performance oriented allocator built by Microsoft. This is a required dependency for python-rtoml (which is in turn a new dependency for bundlewrap, which is a package I maintain in the Python team), unfortunately I don't have the time at present to learn Rust packaging, so if someone else can take this, that would be appreciated.
Bug#1016947: RM: gnubik -- ROM; gtk-2 only, no longer maintained
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: j...@debian.org Please remove gnubik It is gtk-2 only, and no longer maintained upstream.
Bug#1014316: Unexpected behavior at login prompt
Package: kmscon Version: 9.0.0-1+b1 Severity: minor I recently wound up with an ulltrawide monitor that is effectively a 4k screen with a haircut at 1600 lines … and I'm legally blind. So let me say that I greatly appreciate this package and the ease with which I specified a custom DPI to get readable fonts at the console—thank you for packaging it. I also appreciate the standard getty fallback. The other distribution thus far that seems to have kmscon as an option is arch (because of course it does) and … they describe configuring a specific tty for getty in case kmscon fails. An automatic fallback seems more elegant. That said, it behaves a bit strangely prior to logging in, and these things cause minor usability issues. Chief among these is that backspace doesn't work. My password is deliberately not short (as in xkcd 936 not short), and I sometimes mistype it. I've learned that the backspace key does not work at this login prompt. It also doesn't display /etc/issue which might be a symptom of the same issue, being a different login process than is typically used by Debian at the console? There might be a workaround, in that case, to run the more traditional login process under kmscon, but I haven't really researched that yet and that wouldn't change the default anyway, so a report is still warranted IMO. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kmscon depends on: ii libc6 2.33-7 ii libdrm22.4.110-1 ii libegl11.4.0-1 ii libgbm122.0.5-1 ii libgles2 1.4.0-1 ii libglib2.0-0 2.72.3-1 ii libpango-1.0-0 1.50.7+ds-1 ii libpangoft2-1.0-0 1.50.7+ds-1 ii libpixman-1-0 0.40.0-1 ii libsystemd0251.2-7 ii libtsm44.0.2-0.3 ii libudev1 251.2-7 ii libxkbcommon0 1.4.0-1 kmscon recommends no packages. kmscon suggests no packages. -- no debconf information
Bug#1014130: RM: gnome-shell-extension-draw-on-your-screen -- ROM; RC buggy, no longer maintained upstream
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: j...@debian.org Dear FTP team Unfortunately, gnome-shell-extension-draw-on-your-screen is no longer maintained upstream, and has been incompatible with the last two majort gnome-shell versions. So I believe the time has come to remove it from Debian. thanks, -Jonathan
Bug#1013309: Confirmed: happens on Debian
: Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for doc-base (0.11.1) ... Processing 2 changed doc-base files, 2 added doc-base files... Processing triggers for mate-menus (1.26.0-3) ... Processing triggers for libc-bin (2.33-7) ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for dbus (1.14.0-1) ... Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for libvlc-bin:amd64 (3.0.17.4-4) ... Segmentation fault WARNING: Regenerating VLC plugin cache failed. Please run '/usr/lib/x86_64-linux-gnu/vlc/vlc-cache-gen /usr/lib/x86_64-linux-gnu/vlc/plugins' manually. Press Return to continue, 'q' followed by Return to quit. tjcarter@aki:~$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux bookworm/sid Release:unstable Codename: sid tjcarter@aki:~$ sudo /usr/lib/x86_64-linux-gnu/vlc/vlc-cache-gen /usr/lib/x86_64-linux-gnu/vlc/plugins Segmentation fault Happens on Debian too. Joseph
Bug#1012533: ftp.debian.org: Please consider a firmware component for bookworm
Hi Ansgar On 2022/06/09 09:54, Ansgar wrote: I really don't like adding anything with a slash. Having updates/main instead of main on security.d.o already caused lots of cornercases and we now got (partly) rid of that. Just name it non-free-firmware. If ftp team can avoid the slash, then all the better. So, I'm asking the FTP team to please consider implementing this. > So we should not wait for a GR proposing a different solution? I don't think it's worth blocking on a GR, and I think implementing this could simplify a GR on the larger firmware issues if it becomes clear that it's necessary to have a GR, but I'd like to know where Steve stands on that too. -Jonathan
Bug#1012533: ftp.debian.org: Please consider a firmware component for bookworm
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: j...@debian.org Dear FTP team Recently, Steve McIntyre initiated a discussion[1] on debian-devel on the future of firmware in Debian, and how we want to address it as a project. There are many viewpoints on this, but, it seems that we have some general concensus that if we make an image with firmware on it more prominent to our users, then it would be ideal to include only the firmware on such an image, rather than enabling the entire non-free by default, which may lead to users inadvertently installing non-free software on their computer (which is the current status-quo on our non-free firmware-enabled images). Paul's suggestion[2] of copying out firmare to non-free/firmware seems to make a tremendous amount of sense. This will allow us to generate images that have only firmware enabled for non-free packages by default, improving the current status quo, and, it wouldn't require a GR. Additionally, I think Paul's suggestion of starting with a package selection of packages that starts with firmware-* or that puts files in /lib/firmware, along with the cpu microcode packages, is a good starting point of what should be included in there. So, I'm asking the FTP team to please consider implementing this. Ideally, reasonably soon, since we're about half a year away from entering the initial stages of the freeze period, and having this in place sooner, rather than later, would aid in making sure that image generation and other parts that may depend on this could also have some kinks ironed out well ahead of the release. Thanks, -Jonathan [1] https://lists.debian.org/msgid-search/20220419002746.gt14...@tack.einval.com [2] https://lists.debian.org/msgid-search/56b88c450a464743f84a2f451d20d554d81c3546.ca...@debian.org
Bug#1011631: ITP: python3-dmm -- distribution management modules/toolkit
Package: wnpp Severity: wishlist Owner: Jonathan Carter X-Debbugs-Cc: debian-de...@lists.debian.org, j...@debian.org * Package name: python3-dmm Version : 0.0.1 Upstream Author : Jonathan Carter * URL : https://salsa.debian.org/jcc/distribution-management-modules * License : ISC Programming Lang: Python Description : distribution management modules/toolkit Modules and toolkit that makes taking care of Linux distribution tasks easier. Its initial set of modules allow you to configure tools like. apt, grub, squashfs (among others) and actions from these modules can be stringed together using recipes (which are yaml files).
Bug#989085: Description suggestion
Suggest something like… Description: Micro-compositor for game scaling Gamescope wraps your games to give them scaling and fullscreen options. It provides a Wayland compositor to your games, but gamescope runs under both Wayland and X.org. . Your game sees a virtual display at the resolution you specified. You see a scaled view in a window or fullscreen. This is useful when either the game or your system do not permit running the game at native window/screen sizes. You can also use integer scaling to keep your pixels sharp and pixelated. I think this should resolve any confusion as to whether or not a person wants to install this. Joseph
Bug#1005212: Calamares installer fails at partitioning disks
Hi, can you please shed some more details on what your partitioning looked like? How did you set up your partitions, did you intend or specify for /dev/sda9 to be used, or was it the auto-partitioner? I'll need some more information on how to re-produce this bug in order to file it upstream or to figure out whether it's a debian-specific issue. thanks!
Bug#1008664: RM: gnome-shell-extension-disconnect-wifi -- ROM; package no longer needed
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: j...@debian.org Please remove gnome-shell-extension-disconnect-wifi It's now possible to switch off wifi from the gnome panel by default.
