Unable to install blueman in Debian 10 stable: Depends: python3 (< 3.8) but 3.8.2-3 is to be installed
Hi, I'm running Debian 10 stable, and after installing, when I try to install blueman I get the following error:
Code:
The following information may help to resolve the situation: Any help? Thanks |
Do you have a FrankenDebian system? The python3 package in Buster is 3.7. If apt is trying to install 3.8.2 then your /etc/apt/sources.list or a file in /etc/apt/sources.list.d would seem to be pointing to a different repository for some reason. If so, you will almost certainly break your system even worse than it already is.
|
Quote:
Code:
root@haswell:~# apt-get -s install blueman |
Yes, I have blueman installed on my Buster system, and it installed without issues. But the python3 version is 3.7. Sid has 3.8. So my first guess is that the OP's system has at least some Sid references. Running Sid is fine, and I do, but on a separate machine. Mixing Stable and Sid on one system is not optimal.
|
Now that you guys mention it, a couple of days ago I enabled the buster-backports repository to install a package that wasn't working with the default repositories (I think it was tor-browser), but I removed it since. If I installed python3.7, shouldn't blueman work with that version? Is it safe to do an apt-get purge python3.8 and just leave the 3.7?
|
Blueman will work with 3.7, but if you have backports in sources.list without pinning, apt will keep trying to install 3.8. Either remove the backports repository or pin its packages to a lower priority. The Debian Wiki has an explanation of how to do that. You can't purge 3.8 if it isn't installed.
|
I have both python3.8 and python3.7 installed. I've also removed the backports repository and after an apt-get update the issue is still happening. Can I remove python3.8 without breaking Debian?
|
I don't see how it's possible for you to have both 3.7 and 3.8 installed. You wouldn't get the error about 3.8 to be installed. What is the output of
Code:
apt-cache policy python3 |
The output is:
Code:
python3: Code:
dpkg -s python3.7 |
Well, you hava 3.8 installed. I suggest purging 3.8, first checking what else is going to be removed. You have several packages from backports installed, and I really don't know what will happen when you remove python3. Run the apt command, and you should get a prompt to continue or abort. Read the list carefully and decide how you want to proceed. I think it should be fine, but no guarantees.
|
After removing python3.8, I still cant install blueman. Now I get the following message:
Code:
Reading package lists... Done Code:
Reading package lists... Done Could all these issues be generated just for using buster-backports? I used sid for 3 years before going back to stable and never had so much difficulties installing a packet. |
After removing python3.8, you need to reinstall 3.7, I suspect. You can also use aptitude to do the blueman install, and it should pull in any dependencies.
|
If you use backports, you need to do the pinning. You need to make sure only specific packages from backports get installed when you really need them, not every possible package every update. Yes, all those issues can be generated just by using backports, if it is used indiscriminately. The Debian wiki explains how to add backports successfully.
|
I use the backports myself and python3 version 3.8 is not there in it.
Code:
root@haswell:~# apt update Code:
root@haswell:~# alias acp Code:
root@haswell:~# apt-cache policy linux-image-amd64 Code:
root@haswell:~# acp gir1.2-gtk-3.0 Try this for your install line for the package. Code:
root@haswell:~# apt -s install blueman python3-gi gir1.2-gtk-3.0 gir1.2-gdkpixbuf-2.0 gir1.2-glib-2.0 gir1.2-pango-1.0 gir1.2-notify-0.7 python3-gi-cairo gir1.2-appindicator3-0.1 |
I would be interested in seeing the OP's sources.list and the contents of files in sources.list.d.
|
All times are GMT -5. The time now is 08:14 PM. |