Hello all,
I’m trying to get the newer LTTng 2.13.18 DKMS modules working on my Proxmox VE 8 host (kernel 6.8.12-9-pve), but every attempt trips the pve-apt-hook and wants to remove the proxmox-ve meta-package. Below is what I’ve done so far and the exact errors I see.
- Host: Proxmox VE 8.x
- Kernel: `6.8.12-9-pve` (headers installed)
- Aim: Install `lttng-modules-dkms=2.13.18-1` (from Debian Testing “trixie”) and matching `lttng-tools` without breaking any PVE meta-packages, since the version available in stable `2.13.9` doesn't support kernels >= 6.8
Steps performed:
1. Added Testing (“trixie”) repo:
2. Set up pinning in `/etc/apt/preferences.d/lttng`:
3. Held key PVE packages to prevent removal:
4. Attempted install:
Resulting Error:
Some questions I have are:
1. Has anyone successfully pulled only
2. What would be the correct way to pin or hold packages so that APT will honor the Testing source for LTTng but leave all PVE meta-packages intact?
3. Are there any PVE-specific hooks or configs I should adjust (
P.S.
I’m fairly new to Proxmox. I’ve actually managed to install lttng-dkms successfully on a plain Debian host using exactly the same kernel (6.8.12-9-pve) and pinning approach, but on Proxmox it’s always rebelling via that pve-apt-hook. I’m open to any suggestions on tackling this from a different angle or a completely different approach that allows a dkms install before settling for an install from source.
Thank you in advance for any insights, pointers and suggestions!
I’m trying to get the newer LTTng 2.13.18 DKMS modules working on my Proxmox VE 8 host (kernel 6.8.12-9-pve), but every attempt trips the pve-apt-hook and wants to remove the proxmox-ve meta-package. Below is what I’ve done so far and the exact errors I see.
- Host: Proxmox VE 8.x
- Kernel: `6.8.12-9-pve` (headers installed)
- Aim: Install `lttng-modules-dkms=2.13.18-1` (from Debian Testing “trixie”) and matching `lttng-tools` without breaking any PVE meta-packages, since the version available in stable `2.13.9` doesn't support kernels >= 6.8
Steps performed:
1. Added Testing (“trixie”) repo:
Bash:
cat <<EOF >/etc/apt/sources.list.d/trixie.list
deb [URL]http://deb.debian.org/debian[/URL] testing main contrib non-free
EOF
apt update2. Set up pinning in `/etc/apt/preferences.d/lttng`:
Bash:
Package: lttng-modules-dkms lttng-tools python3-lttng liblttng-ust-dev liburcu-dev libelf-dev uuid-dev zlib1g-dev
Pin: release a=testing
Pin-Priority: 990
Package: *
Pin: release a=bookworm
Pin-Priority: 9003. Held key PVE packages to prevent removal:
Code:
apt-mark hold proxmox-ve pve-manager pve-qemu-kvm qemu-server pve-container lxc-pve4. Attempted install:
Code:
apt install -t testinglttng-modules-dkms=2.13.18-1lttng-tools=2.13.15-2Resulting Error:
Bash:
W: (pve-apt-hook) !! WARNING !!
W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!
...
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (1)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hookSome questions I have are:
1. Has anyone successfully pulled only
lttng-modules-dkms 2.13.18-1 (and matching tools) from Testing without disabling or removing `proxmox-ve`?2. What would be the correct way to pin or hold packages so that APT will honor the Testing source for LTTng but leave all PVE meta-packages intact?
3. Are there any PVE-specific hooks or configs I should adjust (
/usr/share/proxmox-ve/pve-apt-hook itself?) to allow selective upgrades?P.S.
I’m fairly new to Proxmox. I’ve actually managed to install lttng-dkms successfully on a plain Debian host using exactly the same kernel (6.8.12-9-pve) and pinning approach, but on Proxmox it’s always rebelling via that pve-apt-hook. I’m open to any suggestions on tackling this from a different angle or a completely different approach that allows a dkms install before settling for an install from source.
Thank you in advance for any insights, pointers and suggestions!
Last edited: