severusseptimius / lxqt-1.1-debian

GNU General Public License v2.0
6 stars 2 forks source link

Issues in Debian 11 bullseye #2

Open stefonarch opened 2 years ago

stefonarch commented 2 years ago

Fresh WM, updated, nothing removed first:


The following packages have unmet dependencies:
 libfm-qt11 : Depends: libc6 (>= 2.33) but 2.31-13+deb11u3 is to be installed
              Depends: libstdc++6 (>= 11) but 10.2.1-6 is to be installed
 libqtermwidget5-1 : Depends: libc6 (>= 2.33) but 2.31-13+deb11u3 is to be installed
 lximage-qt : Depends: libc6 (>= 2.32) but 2.31-13+deb11u3 is to be installed
 lxqt-archiver : Depends: libc6 (>= 2.33) but 2.31-13+deb11u3 is to be installed
                 Depends: libstdc++6 (>= 11) but 10.2.1-6 is to be installed
                 Recommends: zip but it is not going to be installed
 lxqt-panel : Depends: libstatgrab10 (>= 0.92.1) but 0.92-2 is to be installed
 lxqt-runner : Depends: libmuparser2v5 (>= 2.3.3) but 2.2.6.1+dfsg-1 is to be installed
 pavucontrol-qt : Depends: libstdc++6 (>= 11) but 10.2.1-6 is to be installed
 pcmanfm-qt : Depends: libc6 (>= 2.32) but 2.31-13+deb11u3 is to be installed
              Depends: libstdc++6 (>= 11) but 10.2.1-6 is to be installed
 qps : Depends: libc6 (>= 2.33) but 2.31-13+deb11u3 is to be installed
 screengrab : Depends: libx11-xcb1 (>= 2:1.7.5) but 2:1.7.2-1 is to be installed
E: Unable to correct problems, you have held broken packages.

I switched repos to testing and no unmet dependencies anymore. Supporting Bullseye impossible? Not sure if just switching back to bullseye repo after install could create issues.

stefonarch commented 2 years ago

BTW: all packages/apps are working fine :)

Switching the installation to testing:

sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... 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:
 libwacom9 : Depends: libwacom-common (= 2.2.0-1) but 1.8-2 is to be installed
E: Broken packages

sudo apt install libwacom-common && sudo apt upgradeworks fine,

severusseptimius commented 2 years ago

The following packages have unmet dependencies: libwacom9 : Depends: libwacom-common (= 2.2.0-1) but 1.8-2 is to be installed E: Broken packages

About this, it has no relation whatsoever with LXQt. I also had this problem a while back on sid, while trying to update the system.

severusseptimius commented 2 years ago

I switched repos to testing and no unmet dependencies anymore. Supporting Bullseye impossible?

I dont think it is impossible to support Bullseye, but I might have to make another repo for it. Lxqt doesn't need libc6(>=2.33).

Not sure if just switching back to bullseye repo after install could create issues.

This is almost certanly why I didn't see the problems. I installed a fresh debian testing, tried the packages, removed them and switched back to bullseye, and tested again. Switching back to stable is not recommended, to say the least :).

I'll start making packages for bullseye soon.

Thanks again for taking the time to test the packages, and sorry for the lack of thoroughness on my side.

Attigliuzzo commented 2 years ago

Tested on Debian Bookworm, everything runs but i installed manually to remove some broken dependencies and install newer ones.

severusseptimius commented 2 years ago

Tested on Debian Bookworm, everything runs but i installed manually to remove some broken dependencies and install newer ones.

Yes. As I explained in another issue, because debian uses the soname in the package name, upgrading can't be that smooth (especially since the switch from 0.17 to 1.0.0, for example, lxqt-globalkeyes0 became lxqt-globalkeyes1).

Even though I don't like some things about ubuntu, PPAs are much more user-friendly in terms of using unofficial packages...