This in reference to [this question](https://unix.stackexchange.com/q/758547/150047) . Many thanks to user Marcus Müller for providing the silver bullet for getting Emacs 29 from Debian backports. I've done this already, and profited. However, one thing remains: the Emacs 28 documentation still lingers. I'm assuming I need to do sudo apt install emacs-common-non-dfsg/bookworm-backports, but this gives me a "referred to by another package" message. Perhaps this is a mistake from the Debian side (the backport author simply forgot to include the package)? Hopefully I can get the ball rolling from any insight into this matter.

I have a development machine running Debian 11, which is currently our standard environement for equipment hosts. I use VNC (TigerVNC server) to access it remotely from my work computer. The problem is that TigerVNC that comes with Debian 11 has a very annoying bug , that interferes with my work. The bug has been long fixed, but there is no official backport and backports for Debian 11 are EOLed to my knowledge. So the only way to get the fix is to backport TigerVNC manually. I tried to follow the backporting guide by Faheem Mitha , because it appears to be the most suitable method for this case, which requires Debian-specific configuration and build. I manage to get up to Step 4: debuild -uc -us dpkg-buildpackage -us -uc -ui dpkg-buildpackage: info: source package tigervnc dpkg-buildpackage: info: source version 1.12.0+dfsg-8~bpo11+1 dpkg-buildpackage: info: source distribution bullseye-backports dpkg-buildpackage: info: source changed by dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 dpkg-source: info: using options from tigervnc-1.12.0+dfsg/debian/source/options: --single-debian-patch --create-empty-orig dpkg-checkbuilddeps: error: Unmet build dependencies: libxft-dev libxcursor-dev libxrandr-dev libxdamage-dev libwrap0-dev xorg-server-source (>= 2:21) xserver-xorg-dev appstream quilt bison flex x11proto-dev (>= 2021.5) libxcvt-dev libxfont-dev (>= 1:2.0.1) libxkbfile-dev (>= 1:0.99.1) libpciaccess-dev (>= 0.12.901) libgcrypt-dev libudev-dev (>= 151-3) libselinux1-dev (>= 2.0.80) libaudit-dev libdrm-dev (>= 2.4.107-5~) mesa-common-dev libunwind-dev libxmuu-dev (>= 1:0.99.1) libxrender-dev (>= 1:0.9.0) libxi-dev (>= 2:1.8) libxpm-dev (>= 1:3.5.3) libxaw7-dev (>= 1:0.99.1) libxmu-dev (>= 1:0.99.1) libxtst-dev (>= 1:0.99.1) libxres-dev (>= 1:0.99.1) libxfixes-dev (>= 1:3.0.0) libxv-dev libxinerama-dev libxshmfence-dev (>= 1.1) libepoxy-dev libegl-dev (>= 1.3.2) libgbm-dev (>= 10.2) libbsd-dev libdbus-1-dev (>= 1.0) libsystemd-dev dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.) debuild: fatal error at line 1182: dpkg-buildpackage -us -uc -ui failed sudo apt-get build-dep tigervnc-standalone-server=1.12.0+dfsg-8 Reading package lists... Done Picking 'tigervnc' as source package instead of 'tigervnc-standalone-server' Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: builddeps:tigervnc : Depends: xorg-server-source (>= 2:21) but 2:1.20.11-1+deb11u14 is to be installed Depends: x11proto-dev (>= 2021.5) but 2020.1-1 is to be installed Depends: libxcvt-dev but it is not installable Depends: libdrm-dev (>= 2.4.107-5~) but 2.4.104-1 is to be installed Depends: libxi-dev (>= 2:1.8) but 2:1.7.10-1 is to be installed E: Unable to correct problems, you have held broken packages. However, I don't understand from the guide what exactly I am supposed to do about unmet dependencies. Am I supposed to lower the required version in debian/control? And in particular, how do I handle libxcvt-dev that is marked uninstallable?

I use Kubuntu 24.10 Minimal, I was trying to get the libreoffice backport from oracular-backports by inputting the following command: sudo apt-get install -t oracular-backports libreoffice However, doing so resulted in the following error: E: The value 'oracular-backports' is invalid for APT::Default-Release as such a release is not available in the sources I followed this article , specifically the second option of manually installing backports, I even made sure my release name was oracular by inputting the following: lsb_release -cs sure enough, the output was oracular, have I done something wrong? EDIT: Someone suggested to add the contents of cat /etc/apt/sources.list /etc/apt/sources.list.d/* | grep -v '^#', so here it goes: deb [signed-by=/etc/apt/keyrings/packages.mozilla.org.asc] https://packages.mozilla.org/apt mozilla main Types: deb URIs: http://archive.ubuntu.com/ubuntu Suites: oracular oracular-updates oracular-backports Components: main universe restricted multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://security.ubuntu.com/ubuntu/ Suites: oracular-security Components: main universe restricted multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg deb [signed-by=/usr/share/keyrings/waydroid.gpg] https://repo.waydro.id/ oracular main Looking at it, I might have to remove some 3rd party repos

I need to install a newer version of libfmt on Debian 11. This is for CI/CD, and since fmt can be used header-only, I figure it should be ok. What's the best way to do this, with the least chance of breaking something? Should I add a newer repository to sources and use pinning to hold-back other packages? Should I use an ubuntu ppa? Should I try to upload a newer version of the debian package to a PPA?

I'm often following [SimpleBackportCreation](https://wiki.debian.org/SimpleBackportCreation) to create custom backports for various packages that don't exist in stable branch. One of the steps is to install build-deps with sudo mk-build-deps --install --remove command. The question is, once the backport is installed, do I need to keep build-deps packages installed, or is it safe to purge them once custom backport is installed? I primarily want to save on some space but secondary reason is that updating a backport might uninstall/upgrade previous build-deps from previous version but the build for the new backport version might fail, so I'm wondering if in that case, now removed build-deps packages will affect old backport initially made and already installed. --- Bottom line, can I purge *-build-deps?

I've got a *situation* that has come about just yesterday after an apt full-upgrade. It *seems* the apps that are affected are apps that I had previously installed from debian-backports. Here's the rundown with all the history I could muster: #### 1. Modify /etc/apt/sources.list to add bookworm-backports; o/a 15 Aug 2024: About 2.5 months ago, I concluded that I needed the backports versions of pipewire and wireplumber. To make this happen, I modified my /etc/apt/sources.list file to add backports:

$ cat /etc/apt/sources.list
deb http://deb.debian.org/debian  bookworm main contrib non-free non-free-firmware
deb http://deb.debian.org/debian-security/  bookworm-security main contrib non-free non-free-firmware
deb http://deb.debian.org/debian  bookworm-updates main contrib non-free non-free-firmware
# Uncomment deb-src lines below then 'apt-get update' to enable 'apt-get source'
#deb-src http://deb.debian.org/debian  bookworm main contrib non-free non-free-firmware
#deb-src http://deb.debian.org/debian-security/  bookworm-security main contrib non-free non-free-firmware
#deb-src http://deb.debian.org/debian  bookworm-updates main contrib non-free non-free-firmware
deb http://deb.debian.org/debian  bookworm-backports main contrib non-free

No changes were made to /etc/apt/sources.list.d/raspi.list:

$ cat /etc/apt/sources.list.d/raspi.list
deb http://archive.raspberrypi.com/debian/  bookworm main
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://archive.raspberrypi.com/debian/  bookworm main

#### 2. Install pipewire et. al. from bookworm-backports; o/a 15 Aug 2024:

$ sudo apt install -t bookworm-backports pipewire pipewire-audio-client-libraries libspa-0.2-bluetooth 
...
$ sudo reboot

Afterwards, the pipewire & wireplumber versions (from backports) installed on my system were:

$ pipewire --version
pipewire
Compiled with libpipewire 1.2.1
Linked with libpipewire 1.2.1 

$ wireplumber --version
wireplumber
Compiled with libwireplumber 0.4.17
Linked with libwireplumber 0.4.17

#### 3. Fast forward to 9 Oct, 2024 after completion of testing This system had not been upgraded in two months as I was running a test on the apps that I'm now having trouble with. Here's what I saw yesterday: Note bookworm-backports in the list below:

$ sudo apt update
Hit:1 http://deb.debian.org/debian  bookworm InRelease
Get:2 http://deb.debian.org/debian-security  bookworm-security InRelease [48.0 kB]
Get:3 http://deb.debian.org/debian  bookworm-updates InRelease [55.4 kB]
Get:4 http://deb.debian.org/debian  bookworm-backports InRelease [59.0 kB]
Get:5 http://archive.raspberrypi.com/debian  bookworm InRelease [39.0 kB]
Get:6 http://deb.debian.org/debian-security  bookworm-security/main armhf Packages [181 kB]
Get:7 http://deb.debian.org/debian-security  bookworm-security/main arm64 Packages [185 kB]
Get:8 http://deb.debian.org/debian-security  bookworm-security/main Translation-en [114 kB]
Get:9 http://deb.debian.org/debian  bookworm-backports/main arm64 Packages [249 kB]
Get:10 http://deb.debian.org/debian  bookworm-backports/main armhf Packages [250 kB]
Get:11 http://deb.debian.org/debian  bookworm-backports/main Translation-en [210 kB]
Get:12 http://deb.debian.org/debian  bookworm-backports/contrib arm64 Packages [4,964 B]
Get:13 http://deb.debian.org/debian  bookworm-backports/contrib armhf Packages [4,740 B]
Get:14 http://deb.debian.org/debian  bookworm-backports/non-free arm64 Packages [6,864 B]
Get:15 http://deb.debian.org/debian  bookworm-backports/non-free armhf Packages [1,516 B]
Get:16 http://archive.raspberrypi.com/debian  bookworm/main armhf Packages [515 kB]
Get:17 http://archive.raspberrypi.com/debian  bookworm/main arm64 Packages [485 kB]
Fetched 2,409 kB in 4s (614 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
59 packages can be upgraded. Run 'apt list --upgradable' to see them.

I've marked (*) the 12 entries that are coming from backports:

apt list --upgradable
Listing... Done
base-files/stable 12.4+deb12u7 arm64 [upgradable from: 12.4+deb12u6]
curl/stable 7.88.1-10+deb12u7 arm64 [upgradable from: 7.88.1-10+deb12u6]
git-man/stable-security,stable-security 1:2.39.5-0+deb12u1 all [upgradable from: 1:2.39.2-1.1]
git/stable-security 1:2.39.5-0+deb12u1 arm64 [upgradable from: 1:2.39.2-1.1]
initramfs-tools-core/stable,stable 0.142+deb12u1 all [upgradable from: 0.142]
initramfs-tools/stable,stable 0.142+deb12u1 all [upgradable from: 0.142]
libc-bin/stable 2.36-9+rpt2+deb12u8 arm64 [upgradable from: 2.36-9+rpt2+deb12u7]
libc-dev-bin/stable 2.36-9+rpt2+deb12u8 arm64 [upgradable from: 2.36-9+rpt2+deb12u7]
libc-devtools/stable 2.36-9+rpt2+deb12u8 arm64 [upgradable from: 2.36-9+rpt2+deb12u7]
libc-l10n/stable,stable 2.36-9+rpt2+deb12u8 all [upgradable from: 2.36-9+rpt2+deb12u7]
libc6-dbg/stable 2.36-9+rpt2+deb12u8 arm64 [upgradable from: 2.36-9+rpt2+deb12u7]
libc6-dev/stable 2.36-9+rpt2+deb12u8 arm64 [upgradable from: 2.36-9+rpt2+deb12u7]
libc6/stable 2.36-9+rpt2+deb12u8 arm64 [upgradable from: 2.36-9+rpt2+deb12u7]
libcamera-ipa/stable 0.3.2+rpt20240927-1 arm64 [upgradable from: 0.3.0+rpt20240617-1]
libcamera0.3/stable 0.3.2+rpt20240927-1 arm64 [upgradable from: 0.3.0+rpt20240617-1]
libcurl3-gnutls/stable 7.88.1-10+deb12u7 arm64 [upgradable from: 7.88.1-10+deb12u6]
libcurl4/stable 7.88.1-10+deb12u7 arm64 [upgradable from: 7.88.1-10+deb12u6]
libexpat1/stable-security 2.5.0-1+deb12u1 arm64 [upgradable from: 2.5.0-1]
libpam-systemd/stable 252.30-1~deb12u2 arm64 [upgradable from: 252.26-1~deb12u2]
* libpipewire-0.3-0/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
* libpipewire-0.3-common/stable-backports,stable-backports 1.2.4-1~bpo12+1 all [upgradable from: 1.2.1-1~bpo12+1]
* libpipewire-0.3-modules/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
libpisp-common/stable,stable 1.0.7-1 all [upgradable from: 1.0.6-1]
libpisp1/stable 1.0.7-1 arm64 [upgradable from: 1.0.6-1]
* libspa-0.2-bluetooth/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
* libspa-0.2-modules/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
libssl3/stable 3.0.14-1~deb12u2+rpt1 arm64 [upgradable from: 3.0.13-1~deb12u1+rpt1]
libsystemd-shared/stable 252.30-1~deb12u2 arm64 [upgradable from: 252.26-1~deb12u2]
libsystemd0/stable 252.30-1~deb12u2 arm64 [upgradable from: 252.26-1~deb12u2]
libudev1/stable 252.30-1~deb12u2 arm64 [upgradable from: 252.26-1~deb12u2]
linux-headers-rpi-2712/stable 1:6.6.51-1+rpt3 arm64 [upgradable from: 1:6.6.31-1+rpt1]
linux-headers-rpi-v8/stable 1:6.6.51-1+rpt3 arm64 [upgradable from: 1:6.6.31-1+rpt1]
linux-image-rpi-2712/stable 1:6.6.51-1+rpt3 arm64 [upgradable from: 1:6.6.31-1+rpt1]
linux-image-rpi-v8/stable 1:6.6.51-1+rpt3 arm64 [upgradable from: 1:6.6.31-1+rpt1]
linux-libc-dev/stable,stable 1:6.6.51-1+rpt3 all [upgradable from: 1:6.6.31-1+rpt1]
locales/stable,stable 2.36-9+rpt2+deb12u8 all [upgradable from: 2.36-9+rpt2+deb12u7]
openssl/stable 3.0.14-1~deb12u2+rpt1 arm64 [upgradable from: 3.0.13-1~deb12u1+rpt1]
* pipewire-alsa/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
* pipewire-audio-client-libraries/stable-backports,stable-backports 1.2.4-1~bpo12+1 all [upgradable from: 1.2.1-1~bpo12+1]
* pipewire-bin/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
* pipewire-jack/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
* pipewire-pulse/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
* pipewire/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
python3-gpiozero/stable,stable 2.0.1-0+rpt1 all [upgradable from: 2.0-1]
raspberrypi-sys-mods/stable 20240911 arm64 [upgradable from: 20240807]
raspi-firmware/stable,stable 1:1.20240924-1 all [upgradable from: 1:1.20240529-1]
raspi-utils-core/stable 20240903-1 arm64 [upgradable from: 20240402-4]
raspi-utils-dt/stable 20240903-1 arm64 [upgradable from: 20240402-4]
raspi-utils-eeprom/stable 20240903-1 arm64 [upgradable from: 20240402-4]
raspi-utils-otp/stable,stable 20240903-1 all [upgradable from: 20240402-4]
raspi-utils/stable,stable 20240903-1 all [upgradable from: 20240402-4]
raspinfo/stable,stable 20240903-1 all [upgradable from: 20240402-4]
rpi-eeprom/stable,stable 26.0-1 all [upgradable from: 24.0-1]
rpicam-apps-lite/stable 1.5.2-2 arm64 [upgradable from: 1.5.0-2]
systemd-sysv/stable 252.30-1~deb12u2 arm64 [upgradable from: 252.26-1~deb12u2]
systemd-timesyncd/stable 252.30-1~deb12u2 arm64 [upgradable from: 252.26-1~deb12u2]
systemd/stable 252.30-1~deb12u2 arm64 [upgradable from: 252.26-1~deb12u2]
udev/stable 252.30-1~deb12u2 arm64 [upgradable from: 252.26-1~deb12u2]
* wireplumber/stable-backports 0.5.6-1~bpo12+1 arm64 [upgradable from: 0.4.17-1~bpo12+1]

And so I did an upgrade on the entire list; this appeared to complete *normally*, but *some items escaped my attention* (not watching the screen during the upgrade) until the "wheels came off":

$ sudo apt -y full-upgrade
...

The following package was automatically installed and is no longer required:
  libwireplumber-0.4-0
Use 'sudo apt autoremove' to remove it.
The following NEW packages will be installed:
  libwireplumber-0.5-0 linux-headers-6.6.51+rpt-common-rpi linux-headers-6.6.51+rpt-rpi-2712 linux-headers-6.6.51+rpt-rpi-v8
  linux-image-6.6.51+rpt-rpi-2712 linux-image-6.6.51+rpt-rpi-v8 linux-kbuild-6.6.51+rpt
The following packages will be upgraded:
  base-files curl git git-man initramfs-tools initramfs-tools-core libc-bin libc-dev-bin libc-devtools libc-l10n libc6 libc6-dbg libc6-dev
  libcamera-ipa libcamera0.3 libcurl3-gnutls libcurl4 libexpat1 libpam-systemd libpipewire-0.3-0 libpipewire-0.3-common libpipewire-0.3-modules
  libpisp-common libpisp1 libspa-0.2-bluetooth libspa-0.2-modules libssl3 libsystemd-shared libsystemd0 libudev1 linux-headers-rpi-2712
  linux-headers-rpi-v8 linux-image-rpi-2712 linux-image-rpi-v8 linux-libc-dev locales openssl pipewire pipewire-alsa
  pipewire-audio-client-libraries pipewire-bin pipewire-jack pipewire-pulse python3-gpiozero raspberrypi-sys-mods raspi-firmware raspi-utils
  raspi-utils-core raspi-utils-dt raspi-utils-eeprom raspi-utils-otp raspinfo rpi-eeprom rpicam-apps-lite systemd systemd-sysv systemd-timesyncd
  udev wireplumber
59 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.

...

apt-listchanges: Reading changelogs...
apt-listchanges: News
---------------------

wireplumber (0.5.1-1) experimental; urgency=medium

  WirePlumber 0.5 was released with a new configuration system.
  The new system is based on JSON instead of Lua which makes WirePlumber >= 0.5
  incompatible with Lua conf files written for WirePlumber 0.4.
  .
  If only the default configuration (e.g the configuration shipped with the
  Debian package) is used, then there is nothing to do.
  .
  If you use custom configuration files, you will have to manually update them
  by following the migration guide. No automatic migration of old configuration
  files is performed.
  .
  This guide is available at (after having installed "wireplumber-doc"):
    /usr/share/doc/wireplumber/html/daemon/configuration/migration.html
  or
    https://pipewire.pages.freedesktop.org/wireplumber/daemon/configuration/migration.html 

 -- Dylan Aïssi   Sun, 31 Mar 2024 14:44:46 +0200

...

$ sudo reboot
...

#### 4. After the upgrade I discover "the wheels have come off"; pipewire no longer works at all; no Bluetooth sound! Just to confirm what I could already tell, I checked Bluetooth status w/ systemctl

$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
     Active: active (running) since Wed 2024-10-09 22:29:30 UTC; 1h 6min ago
       Docs: man:bluetoothd(8)
   Main PID: 507 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 404)
        CPU: 196ms
     CGroup: /system.slice/bluetooth.service
             └─507 /usr/libexec/bluetooth/bluetoothd

Oct 09 22:29:30 rpi2w bluetoothd: Starting SDP server
Oct 09 22:29:30 rpi2w bluetoothd: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Oct 09 22:29:30 rpi2w bluetoothd: src/plugin.c:plugin_init() Failed to init vcp plugin
Oct 09 22:29:30 rpi2w bluetoothd: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Oct 09 22:29:30 rpi2w bluetoothd: src/plugin.c:plugin_init() Failed to init mcp plugin
Oct 09 22:29:30 rpi2w bluetoothd: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Oct 09 22:29:30 rpi2w bluetoothd: src/plugin.c:plugin_init() Failed to init bap plugin
Oct 09 22:29:30 rpi2w bluetoothd: Bluetooth management interface 1.22 initialized
Oct 09 22:29:31 rpi2w bluetoothd: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Oct 09 22:29:31 rpi2w bluetoothd: sap-server: Operation not permitted (1)

$

bluetoothctl was able to connect with my speaker, but nothing - no sound. #### 5. Restore system **from** raw image file created o/a 16 Aug 2024 This "brought my system back" to the same state it was immediately **after** installing pipewire et. al. (when it worked well!). So - I have a fully functional system again at this point; 9 Oct, 2024. #### 6. Begin incremental upgrades; 9 Oct, 2024 Through a process of trial-and-error, I began an "incremental" upgrade, using sudo apt-get install --only-upgrade X Y Z etc. After each upgrade I checked that Bluetooth was still working. After I whittled the list of un-installed packages down to the following, Bluetooth was still working:

$ apt list --upgradable
Listing... Done

libpipewire-0.3-common/stable-backports,stable-backports 1.2.4-1~bpo12+1 all [upgradable from: 1.2.1-1~bpo12+1]
libpipewire-0.3-modules/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
libspa-0.2-bluetooth/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
libspa-0.2-modules/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
pipewire-alsa/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
pipewire-audio-client-libraries/stable-backports,stable-backports 1.2.4-1~bpo12+1 all [upgradable from: 1.2.1-1~bpo12+1]
pipewire-bin/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
pipewire-jack/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
pipewire-pulse/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
pipewire/stable-backports 1.2.4-1~bpo12+1 arm64 [upgradable from: 1.2.1-1~bpo12+1]
wireplumber/stable-backports 0.5.6-1~bpo12+1 arm64 [upgradable from: 0.4.17-1~bpo12+1]

#### 7. pipewire et. al. are apparently *solely* responsible for the Bluetooth malfunction. I guess this may be "no surprise" to many, but I felt I needed to establish as specifically as possible the source of the problem. Here's my question: How did I *screw this up*? I've never used backports previously, and I **assumed** that when the regular channel "caught up" with backports that apt would see that everything was merged/installed without incident. Obviously, that's not what happened here. What do I need to do to fix this?

I'm using the method on the link below to create a custom Debian backport, ex. for packages that are otherwise not yet backported but exist in testing branch: https://wiki.debian.org/SimpleBackportCreation Now I would like to undo installed backport package however simply running sudo apt purge is not enough because I see some packages have been installed that survive the purge. (I see them in application menu and can run them) Question is how to identify all the extra packages that were installed to be able to purge them as well? I still have build directory that was used to build the backport. If I run sudo less /var/log/apt/history.log the log will show only the backport but will not show those extra packages that were installed. The specific package that I currently want to purge as well as dependencies is crow-translate: https://packages.debian.org/trixie/crow-translate The extra packages in this specific case that I see in application menu are: - QT 5 Assistant - QT 5 Designer - QT 5 Linguist But I believe there are more that are not visible in application menu.

I know there are a few Questions here which ask the same question I appear to be asking. I have tried those suggestions (https://unix.stackexchange.com/a/439342/286615) & (https://unix.stackexchange.com/a/151371/286615) , but they do not work in this case. Here's what has happened:

pi@raspberrypi0w:~ $ sudo apt -t bullseye-backports install udev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  libudev1
The following packages will be upgraded:
  libudev1 udev
2 upgraded, 0 newly installed, 0 to remove and 35 not upgraded.
Need to get 1,654 kB of archives.
After this operation, 511 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://deb.debian.org/debian  bullseye-backports/main armhf udev armhf 252.5-2~bpo11+1 [1,554 kB]
Get:2 http://deb.debian.org/debian  bullseye-backports/main armhf libudev1 armhf 252.5-2~bpo11+1 [100 kB]
Fetched 1,654 kB in 1s (1,267 kB/s)
Reading changelogs... Done
(Reading database ... 43648 files and directories currently installed.)
Preparing to unpack .../udev_252.5-2~bpo11+1_armhf.deb ...
Unpacking udev (252.5-2~bpo11+1) over (247.3-7+rpi1+deb11u2) ...
Preparing to unpack .../libudev1_252.5-2~bpo11+1_armhf.deb ...
Unpacking libudev1:armhf (252.5-2~bpo11+1) over (247.3-7+rpi1+deb11u2) ...
Setting up libudev1:armhf (252.5-2~bpo11+1) ...
Setting up udev (252.5-2~bpo11+1) ...
Segmentation fault
Job for systemd-udevd.service failed because a fatal signal was delivered to the control process.
See "systemctl status systemd-udevd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript udev, action "restart" failed.
● systemd-udevd.service - Rule-based Manager for Device Events and Files
     Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static)
     Active: activating (start) since Tue 2024-04-09 07:36:27 UTC; 130ms ago
TriggeredBy: ● systemd-udevd-control.socket
             ● systemd-udevd-kernel.socket
       Docs: man:systemd-udevd.service(8)
             man:udev(7)
   Main PID: 8773 ((md-udevd))
      Tasks: 1
        CPU: 45ms
     CGroup: /system.slice/systemd-udevd.service
             └─8773 (md-udevd)

Apr 09 07:36:28 raspberrypi0w systemd: Stopped Rule-based Manager for Device Events and Files.
Apr 09 07:36:28 raspberrypi0w systemd: Starting Rule-based Manager for Device Events and Files...
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Main process exited, code=killed, status=11/SEGV
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Failed with result 'signal'.
Apr 09 07:36:28 raspberrypi0w systemd: Failed to start Rule-based Manager for Device Events and Files.
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Scheduled restart job, restart counter is at 5.
Apr 09 07:36:28 raspberrypi0w systemd: Stopped Rule-based Manager for Device Events and Files.
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Start request repeated too quickly.
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Failed with result 'signal'.
Apr 09 07:36:28 raspberrypi0w systemd: Failed to start Rule-based Manager for Device Events and Files.
dpkg: error processing package udev (--configure):
 installed udev package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u8) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for initramfs-tools (0.140) ...
Errors were encountered while processing:
 udev
E: Sub-process /usr/bin/dpkg returned an error code (1)

The attempted "reversion" wasn't very interesting:

pi@raspberrypi0w:~ $ apt install ${udev}/bullseye
Illegal instruction

I attempted a few other "reversions":

pi@raspberrypi0w:~ $ sudo apt install udev
Illegal instruction
pi@raspberrypi0w:~ $ sudo apt-get install udev/stable
Illegal instruction
pi@raspberrypi0w:~ $ sudo apt-get install udev/old-stable
Illegal instruction

A 'segmentation fault' - sounds serious :). I was unsure what this meant; i.e. did the system automatically reject the udev upgrade & revert automatically? - or have I stepped in it? I waited a few minutes & tried this:

$ systemctl status systemd-udevd.service
● systemd-udevd.service - Rule-based Manager for Device Events and Files
     Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static)
     Active: failed (Result: signal) since Tue 2024-04-09 07:36:28 UTC; 28min ago
TriggeredBy: ● systemd-udevd-control.socket
             ● systemd-udevd-kernel.socket
       Docs: man:systemd-udevd.service(8)
             man:udev(7)
    Process: 8776 ExecStart=/lib/systemd/systemd-udevd (code=killed, signal=SEGV)
   Main PID: 8776 (code=killed, signal=SEGV)
        CPU: 199ms

Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Scheduled restart job, restart counter is at 5.
Apr 09 07:36:28 raspberrypi0w systemd: Stopped Rule-based Manager for Device Events and Files.
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Start request repeated too quickly.
Apr 09 07:36:28 raspberrypi0w systemd: systemd-udevd.service: Failed with result 'signal'.
Apr 09 07:36:28 raspberrypi0w systemd: Failed to start Rule-based Manager for Device Events and Files.

I have a good (image) backup from last night, so if I've killed my OS I can recover. However, I'd prefer to fix this without resort to the backup - if that's possible. What should I do?

I've searched unsuccessfully for a *method* to **list** all of the upgrades available from Debian's backports (specifically bullseye-backports): * I've added deb http://deb.debian.org/debian bullseye-backports main contrib non-free to /etc/apt/sources.list. * I've run sudo apt update successfully * I've run sudo apt list --upgradeable bullseye-backports with an "empty" result * I've run sudo apt list --upgradeable -t bullseye-backports; got an error * I've run sudo apt -t bullseye-backports upgrade; I get a list of NEW packages to be installed, and a list of EXISTING packages to be upgraded, and a [Y/n] option to proceed with the entire lot. Is there no way to simply ***list*** the upgrade-able packages from bullseye-backports?

Before dear community marks this question as duplicate please known that I've done site search and figured out there is no equivalent duplicate, for instance this [link](https://unix.stackexchange.com/questions/516664/debian-stretch-not-getting-package-from-stretch-backports) is not duplicate I have followed the following instructions: - https://wiki.debian.org/Backports - https://backports.debian.org/Instructions According to these instructions step No.1 is to update /etc/apt/sources.list by adding the following line: - deb http://deb.debian.org/debian bookworm-backports main contrib non-free When this step is done we need up update index by running sudo apt update From this point on we have two options: 1. Explicitly install a package from backports, for example - apt install -t bookworm-backports 2. Implicitly install a package from backports - apt install /bookworm-backports There is a significant difference between those 2 methods! The first method will install package from backports but will also pull in all it's dependencides also from backports including their dpenedencies and so on which results in "bloated" installation of a package. The second method is cleaner, better and recommended by debian because unlike first method it will reuse dependencies (from main, not from backports) and will pull in only the main package being installed that is from backports. In other words second method will reuse dependencies that are alaready insalled on system without downloading them. However under certain circumstances if that's not possible it will pull dependencies from backports (in rare scenarios though) The problem I'm having is that first method with -t options always works while the second method never works at all. I want to know why that is and how can I make the second method work? Here are two examples that are reproducible for you to test:

sudo apt install wine/bookworm-backports
sudo apt install passwordsafe/bookworm-backports

Here is the output from first example: > sudo apt install wine/bookworm-backports Reading package lists... Done Building dependency tree... Done Reading state information... Done Package wine is a virtual package provided by: wine 8.0~repack-4 You should explicitly select one to install. E: Release 'bookworm-backports' for 'wine' was not found As you can see bookworm-backports was not found! However if you run with -t option you can confirm this is false: sudo apt install wine -t bookworm-backports Which will work just fine and offer you to install the package. So the question is very simple, why doesn't second method (without the -t option) not work and what do I need to do to make it work, do I do something wrong? --- For additional information I'm using Debian 12 (bookworm) And my sources.list looks like this: deb https://deb.debian.org/debian/ bookworm main deb-src https://deb.debian.org/debian/ bookworm main deb http://security.debian.org/debian-security bookworm-security main deb-src http://security.debian.org/debian-security bookworm-security main deb https://deb.debian.org/debian/ bookworm-updates main deb-src https://deb.debian.org/debian/ bookworm-updates main deb https://deb.debian.org/debian/ bookworm-backports main deb-src https://deb.debian.org/debian/ bookworm-backports main

Given this discussion: https://github.com/DNSCrypt/dnscrypt-proxy/discussions/2410 It seems that **dnscrypt-proxy** has a dependency called powerman used only for testing and not useful in the main pagackage that made it unable to compile and it was not fixed before the last freeze of ***debian 12 bookworm***. The end result of having the package dnscrypt-proxy not present in debian 12 !!! --- For my config I need dnscrypt-proxy package. **The remaining options are:** - Install it from http://deb.debian.org/debian/pool/main/d/dnscrypt-proxy/ however that would be a static installation, hence making it not updated in case of security fixes. - Otherwise because it was fixed after debian12 release it is possible to pull it from debian **sid**. (I searched and it seems that isn't available from backports) --- **What is the best practice that allows me to not break the debian installation integrating that only package from sid ? Should I use apt pinning ?** Bard suggested me also this syntax for *sources.list*: deb http://deb.debian.org/debian/sid main/dnscrypt-proxy but it clearly doesn't work.

On Debian Stretch some packages are available only on stretch-backports-sloppy. What is the stretch-backports-sloppy repository used for? What is the deference between sloppy and the regular …-backports?

I'm making a bash script that copies files from one USB drive to other multiple drives. One oldschool machine running Xubuntu dedicated for the job detects 30 devices with no problem. It has USB 2.0 ports only. While another modern machine running Linux Mint doesn't detect more than 16 of these drives at a time. It has USB 3.0 ports only. After I connect more than 16 drives, the new ones stop to show up in lsblk. What could be the cause? EDIT: As fduff pointed out, I checked dmesg after connecting the 17th USB drive, this is what it shows: [ 531.519845] usb 3-9.3.2.6: new high-speed USB device number 46 using xhci_hcd [ 531.974582] usb 3-9.3.2.6: New USB device found, idVendor=abcd, idProduct=1234 [ 531.974585] usb 3-9.3.2.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 531.974586] usb 3-9.3.2.6: Product: UDisk [ 531.974587] usb 3-9.3.2.6: Manufacturer: General [ 531.974588] usb 3-9.3.2.6: SerialNumber: Љ [ 531.975337] usb 3-9.3.2.6: Not enough host controller resources for new device state. [ 531.975340] usb 3-9.3.2.6: can't set config #1, error -12 This makes it look like a hardware limitation, but the number of allowed USB devices is not constant. Now for example I can't connect more than 15 USB drives (the 16th gets error -12), before I was also able once to connect about 20 devices, and they got all discovered properly. I tried using a different USB port to spread the usage across multiple USB controllers, but no luck. **My hardware specs:** MB: ASRock Z97 Extreme6 CPU: Intel Core i5-4690K GPU: MSI GeForce GTX 960 2GB RAM: HyperX Fury Black 8GB [2x4GB 1600MHz DDR3 CL10 DIMM] PSU: Chieftec GPS-500A8 [500W] Display: 2x AOC I2276VWM [IPS, 1920x1080] HDD: WD Blue 3TB I'm also using a 28-port Manhattan USB hub: https://www.amazon.com/Manhattan-Port-USB-Hub-161718/dp/B0074024XU A low-end dying PC running Xubuntu from LiveCD (on a USB drive) was able to detect 29 devices (30 counting the LiveCD drive) and perform file transfers - even though Windows XP that it had installed on HDD at some point failed to detect the 28-port hub at all. That PC now is being looked at by a repair service, because it died (I bet on PSU or MB). Still - it worked, and the shiny new one isn't.

im trying to install backports in my kali linux but im getting an error while using the code line " make list-defconfigs".screenshot I have done both apt update and upgrade and search everywhere but i cant seem to understand why this is happening. none of the make cammands are working.

I am running Debian Bullseye and I want to install ffmpeg 4.4.1, which looks to be available in sid : So I have added the backports repo :

# apt-cache policy
Package files:
...
 500 http://mirrors.ocf.berkeley.edu/debian  bullseye/main amd64 Packages
     release v=11.2,o=Debian,a=stable,n=bullseye,l=Debian,c=main,b=amd64
     origin mirrors.ocf.berkeley.edu
 100 http://deb.debian.org/debian  bullseye-backports/main amd64 Packages
     release o=Debian Backports,a=bullseye-backports,n=bullseye-backports,l=Debian Backports,c=main,b=amd64
     origin deb.debian.org
...

# apt-get install -t bullseye-backports ffmpeg
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
ffmpeg is already the newest version (7:4.3.3-0+deb11u1).
0 upgraded, 0 newly installed, 0 to remove and 33 not upgraded.

apt-cache show ffmpeg only shows one entry, which is for ffmpeg 4.3 in the main stable repository. Any advice?

I have been using proprietary NVIDIA drivers for my GTX 1650s graphics card with Debian 10. I wish to install nvidia-driver from buster-backports however I am encountering errors. First, I removed the proprietary drivers with "sudo ./NVIDIA-Linux-x86_64-470.94.run --uninstall". Rather than rebooting into the console, I then ran "sudo apt -t buster-backports install nvidia-driver". During the installation a notice was printed advising about a mismatch of the kernel module and at the end of the installation, the following was printed:

Error! Bad return status for module build on kernel: 5.15.12s1avl2-lowlatency (x86_64)
Consult /var/lib/dkms/nvidia-current/460.73.01/build/make.log for more information.
dpkg: error processing package nvidia-kernel-dkms (--configure):
 installed nvidia-kernel-dkms package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver:
 nvidia-driver depends on nvidia-kernel-dkms (= 460.73.01-1~bpo10+1) | nvidia-kernel-460.73.01; however:
  Package nvidia-kernel-dkms is not configured yet.
  Package nvidia-kernel-460.73.01 is not installed.
  Package nvidia-kernel-dkms which provides nvidia-kernel-460.73.01 is not configured yet.

dpkg: error processing package nvidia-driver (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 nvidia-kernel-dkms
 nvidia-driver
E: Sub-process /usr/bin/dpkg returned an error code (1)

Can someone please help? My machine was not rebooted and is still with X running. Should I reboot into safe mode, remove the modules nvidia, nvidia_drm and nvidia_modeset with "sudo modprobe -r" and then attempt to install again?

I wasn't able to view any non-english characters in chrome. It just appeared as squares. When I accidentally ranapt-get -t stretch-backports upgrade It somehow got fixed. Now I renistalled the debian and would like to get only that specific package from backports. What might be the exact package? **Kernel version version:** 4.19.0-0.bpo.2-amd64 (backports)
**Chrome version:** 72.0.3626.119

I'm trying to get the most recent version of Git installed onto my Debian Buster machine, and I'm running into trouble. The most recent version of Git on stable is 2.20. I found that the testing branch has the right version, but I'm not having any success with backports. I've added

deb http://deb.debian.org/debian/  buster-backports main contrib
deb-src http://deb.debian.org/debian/  buster-backports main contrib

to /etc/apt/sources.list and done sudo apt-get update, but every time I run sudo apt-get -t buster-backports install git I end up with 2.20 again. I've also tried using apt-get to remove git and then install it, but no luck. Any advice? Thanks!

I can't fix the startup issue I'm facing since I updated my Debian (bullseye) to backports distribution in order to get the **Kernel 5.14** As per my researching it seems to be something related to the framebuffer and nvidia adapters (GeForce RTX 3050 in my case) I tried the steps described in this other post with no success. Here are few information about my hardware and configuration that might help someone to understand what might be wrong.

$ ls -la /boot/
total 128344
drwxr-xr-x  4 root root     4096 Dec 18 09:57 .
drwxr-xr-x 19 root root     4096 Dec 18 08:14 ..
-rw-r--r--  1 root root   236055 Sep 30 15:36 config-5.10.0-9-amd64
-rw-r--r--  1 root root   243590 Oct 10 07:33 config-5.14.0-0.bpo.2-amd64
drwx------  4 root root     4096 Dec 31  1969 efi
drwxr-xr-x  6 root root     4096 Dec 19 07:47 grub
-rw-r--r--  1 root root 41722190 Dec 16 17:03 initrd.img-5.10.0-9-amd64
-rw-r--r--  1 root root 75123714 Dec 18 09:57 initrd.img-5.14.0-0.bpo.2-amd64
-rw-r--r--  1 root root       83 Sep 30 15:36 System.map-5.10.0-9-amd64
-rw-r--r--  1 root root       83 Oct 10 07:33 System.map-5.14.0-0.bpo.2-amd64
-rw-r--r--  1 root root  6833568 Sep 30 15:36 vmlinuz-5.10.0-9-amd64
-rw-r--r--  1 root root  7225472 Oct 10 07:33 vmlinuz-5.14.0-0.bpo.2-amd64

$ cat /etc/default/grub
GRUB_DEFAULT="Advanced options for Debian GNU/Linux>Debian GNU/Linux, with Linux 5.10.0-9-amd64"
GRUB_TIMEOUT="15"
GRUB_DISTRIBUTOR="lsb_release -i -s 2> /dev/null || echo Debian"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash vga=791"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL="console"

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE="1280x1024x16"
GRUB_GFXPAYLOAD_LINUX="keep"

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID="true"

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

GRUB_SAVEDEFAULT="false"

$ lspci -v | egrep -i vga
01:00.0 VGA compatible controller: NVIDIA Corporation Device 25e2 (rev a1) (prog-if 00 [VGA controller])

$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
   1920x1080     77.00*

I'm trying to backport libnanomsg-dev from jessie to squeeze. And dget says: $ dget -x http://ftp.de.debian.org/debian/pool/main/n/nanomsg/nanomsg_0.4~beta+dfsg-3.dsc dget: retrieving http://ftp.de.debian.org/debian/pool/main/n/nanomsg/nanomsg_0.4~beta+dfsg-3.dsc % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2016 100 2016 0 0 47558 0 --:--:-- --:--:-- --:--:-- 96000 dget: using existing nanomsg_0.4~beta+dfsg.orig.tar.gz dget: using existing nanomsg_0.4~beta+dfsg-3.debian.tar.xz nanomsg_0.4~beta+dfsg-3.dsc: dscverify: nanomsg_0.4~beta+dfsg-3.dsc failed signature check: gpg: Signature made Fri 29 Aug 2014 09:49:58 PM EEST using RSA key ID 864CC8BF gpg: Can't check signature: public key not found Validation FAILED!! As far as I can tell, I've got to install jessie's keyring somehow. But how do I do that?