Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[SOLVED] Before upgrading to Bullseye

If none of the specific sub-forums seem right for your thread, ask here.
Message
Author
User avatar
ticojohn
Posts: 1284
Joined: 2009-08-29 18:10
Location: Costa Rica
Has thanked: 21 times
Been thanked: 44 times

Re: Before upgrading to Bullseye

#21 Post by ticojohn »

Head_on_a_Stick wrote:Kodi in bullseye now uses Python3.

Why don't you post some actual command output instead of vague descriptions? It's less effort for you and less confusing for us.

The actual, verbatim message from APT about the held packages would be a start.
When simulating the full-upgrade to Bullseye I get this:

Code: Select all

The following packages have been kept back:
  libpython2-stdlib python2 python2-minimal
I am not irrational, I'm just quantum probabilistic.

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: Before upgrading to Bullseye

#22 Post by Head_on_a_Stick »

So are those packages also pinned?

Code: Select all

apt policy libpython2-stdlib python2 python2-minimal
deadbang

User avatar
ticojohn
Posts: 1284
Joined: 2009-08-29 18:10
Location: Costa Rica
Has thanked: 21 times
Been thanked: 44 times

Re: Before upgrading to Bullseye

#23 Post by ticojohn »

Head_on_a_Stick wrote:So are those packages also pinned?

Code: Select all

apt policy libpython2-stdlib python2 python2-minimal
No sir, they are not pinned. I'm not sure, but I think the problem might be that there is newer version (Python2.7) and that there may be dependencies that can not be met by the full-upgrade. However, I am but an egg. So I am just making a guess.
I am not irrational, I'm just quantum probabilistic.

User avatar
ticojohn
Posts: 1284
Joined: 2009-08-29 18:10
Location: Costa Rica
Has thanked: 21 times
Been thanked: 44 times

Re: Before upgrading to Bullseye

#24 Post by ticojohn »

After doing quite a bit more research I found this explanation and the way to handle the situation. It sounds reasonable to me but would appreciate an opinion from someone more knowledgeable than me before continuing.

https://itsfoss.com/following-packages- ... kept-back/
I am not irrational, I'm just quantum probabilistic.

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: Before upgrading to Bullseye

#25 Post by Head_on_a_Stick »

Looks reasonable but remember to follow the (draft of the) official guide when upgrading: https://www.debian.org/releases/bullsey ... ng.en.html
deadbang

User avatar
ticojohn
Posts: 1284
Joined: 2009-08-29 18:10
Location: Costa Rica
Has thanked: 21 times
Been thanked: 44 times

Re: Before upgrading to Bullseye

#26 Post by ticojohn »

Head_on_a_Stick wrote:Looks reasonable but remember to follow the (draft of the) official guide when upgrading: https://www.debian.org/releases/bullsey ... ng.en.html
Yes sir! As always I appreciate your guidance. Thanks for the help. I will probable perform the update today or tomorrow. I will post back afterwards.
I am not irrational, I'm just quantum probabilistic.

User avatar
ticojohn
Posts: 1284
Joined: 2009-08-29 18:10
Location: Costa Rica
Has thanked: 21 times
Been thanked: 44 times

Re: Before upgrading to Bullseye

#27 Post by ticojohn »

What a PAIN IN THE BACKSIDE. But I finally got it installed. I'm not sure that I will upgrade any of my other Buster installation. Maybe wait for Bullseye to be released.

Issues:
apt upgrade seemed to work okay.
apt full-upgrade had an error with dpkg
ran apt full-upgrade again and it seemed to work okay, but there were many packages that apparently did not get upgraded.
ended up running apt full-upgrade three (3) times to get everything installed.
the final run on apt full-upgrade even took care of those packages that were kept back

There is a strange side effect. For some reason if I boot directly to Bullseye, selecting in the bios, then restart and select Buster the network fails to connect. I have to shut down and shut off power at the UPS. Restart and select Buster and all is well. I'll look into this issue. After I have had time to look at the problem I may start a new post.

Thanks to all that helped on this. I will mark this post as SOLVED
I am not irrational, I'm just quantum probabilistic.

Post Reply