Conflicts in apt between bunsen-meta-all and Proxmox

null-directory · 2023-10-09 00:24:19

I feel like I'm missing something obvious about installing bunsen-meta-all, but it's been years since I've used Debian seriously and am at a bit of a loss.

System currently has Proxmox 8 installed, meaning it's a fresh install of Debian 12 Bookworm aside from a few packages (fish and nvidia-drivers). A post on the Proxmox forums suggests that they provide many/all of the expected items in the Debian firmware-* packages, and the recommendation seemed to be something like "don't worry about those".

There are also missing packages that won't be installed, and seemingly because of newer packages or versions.

Should I install the packages under bunsen-meta-all individually, or should I work to resolve these conflicts?

Console output:

❯ sudo aptitude install bunsen-meta-all -d

<a lot of packages are listed here>

0 packages upgraded, 928 newly installed, 0 to remove and 0 not upgraded.
Need to get 360 MB/870 MB of archives. After unpacking 2,942 MB will be used.
The following packages have unmet dependencies:
 pve-firmware : Conflicts: firmware-amd-graphics but 20230210-5 is to be installed
                Conflicts: firmware-iwlwifi but 20230210-5 is to be installed
                Conflicts: firmware-linux-free but 20200122-1 is to be installed
                Conflicts: firmware-linux-nonfree but 20230210-5 is to be installed
                Conflicts: firmware-misc-nonfree but 20230210-5 is to be installed
                Conflicts: firmware-ralink which is a virtual package, provided by:
                           - firmware-misc-nonfree (20230210-5), but 20230210-5 is to be installed

                Conflicts: firmware-realtek but 20230210-5 is to be installed
 bunsen-meta-all : Depends: fuse3 but it is not going to be installed
                   Depends: gvfs-fuse but it is not installable
                   Depends: ntfs-3g but it is not installable
                   Depends: systemd-timesyncd but it is not going to be installed
The following actions will resolve these dependencies:

     Keep the following packages at their current version:
1)     bunsen-meta-all [Not Installed]
2)     firmware-amd-graphics [Not Installed]
3)     firmware-iwlwifi [Not Installed]
4)     firmware-linux [Not Installed]
5)     firmware-linux-free [Not Installed]
6)     firmware-linux-nonfree [Not Installed]
7)     firmware-misc-nonfree [Not Installed]
8)     firmware-realtek [Not Installed]



Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:

     Remove the following packages:
1)     proxmox-default-kernel [1.0.0 (now, stable)]
2)     proxmox-kernel-6.2 [6.2.16-15 (now)]
3)     proxmox-ve [8.0.2 (now, stable)]
4)     pve-firmware [3.8-2 (now, stable)]
5)     pve-kernel-6.2 [8.0.5 (now, stable)]

     Keep the following packages at their current version:
6)     bunsen-meta-all [Not Installed]



Accept this solution? [Y/n/q/?] q
Abandoning all efforts to resolve these dependencies.
Abort.

If I try to, say, install fuse3 I get the following:

❯ sudo aptitude install fuse3 -d
The following NEW packages will be installed:
  fuse3
The following packages will be REMOVED:
  fuse{a}
0 packages upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B/35.9 kB of archives. After unpacking 30.7 kB will be freed.

I haven't the foggiest what the {a} means on that package name, and honestly not sure how to even search for advice on it.

Any directions or thoughts?

johnraff · 2023-10-09 04:27:04

I don't use aptitude very much. It tries harder than apt to resolve conflicts and offers various ways out, but as you've found, it's output might be hard to understand.

First off, let's check your apt repositories. Could you install inxi (it's part of BL anyway), run

inxi -r

and post the result?

Anyway, looking at aptitude's output above, there seem to be conflicts with eg pve-firmware. Is that a Proxmox package?
BL's bunsen-meta-all depends only on standard Debian packages so there should be no problem installing it, unless the Proxmox 8 install is not in fact pure Debian 8.

#1 2023-10-09 00:24:19

Conflicts in apt between bunsen-meta-all and Proxmox

#2 2023-10-09 04:27:04

Re: Conflicts in apt between bunsen-meta-all and Proxmox

Board footer