[Solved] Broken packages

[hippy]

Pi 3B (non-plus), Buster, doing my regular update ...

Code: Select all

pi@Pi3B:~ $ uname -a
Linux Pi3B 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux
pi@Pi3B:~ $ sudo apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease                  
Hit:3 http://packages.microsoft.com/repos/vscode stable InRelease             
Reading package lists... Done
pi@Pi3B:~ $ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree       
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:
 vlc-bin : Depends: libvlc-bin (= 3.0.8-0+deb10u1+rpt1) but 3.0.8-0+deb10u1+rpt7 is to be installed
 vlc-plugin-skins2 : Depends: vlc-plugin-qt (= 3.0.8-0+deb10u1+rpt7) but 3.0.8-0+deb10u1+rpt1 is to be installed
E: Broken packages
pi@Pi3B:~ $ 

'sudo apt-get purge vlc', 'autoremove', 'update', 'upgrade', 'autoremove', 'install vlc' seems to have resolved the issue.

[HawaiianPi]

Several people have been running into this problem for the last day or so, while others have had no trouble (including me). Try a full-upgrade.

Code: Select all

sudo apt update && sudo apt full-upgrade -y

If that doesn't help, then try a reinstall.

Code: Select all

sudo apt update && sudo apt install --reinstall vlc -y

[hippy]

Never realised quite how fast this forum moves; those reports from the past few days are all way down on page 13+ of my unread posts view.

And a bit embarrassing - I seem to have had the exact same problem almost a year ago ...

https://www.raspberrypi.org/forums/view ... p?t=234274

[LTolledo]

When I updated and upgraded yesterday (01/12/2020) did not encounter this problem....
and I browsed what packages that will be upgraded.... and sure enough VLC was one of those

hmmm.... seems I got a screen cap of that:

latest_update-upgrade.jpg (106.65 KiB) Viewed 13093 times

[hippy]

When I updated and upgraded yesterday (01/12/2020) did not encounter this problem....

It does seem somewhat random as to whether one is affected or not, both this time and last year, and seems to be the same for others.

[pcmanbob]

When I updated and upgraded yesterday (01/12/2020) did not encounter this problem....

It does seem somewhat random as to whether one is affected or not, both this time and last year, and seems to be the same for others.

As I said in the anther thread I wonder if its because people are not always using full-upgrade which is now the recommended command , as it pulls in all the dependences as well, were as upgrade does not.

So you end up with a mixture of dependences some old some new which is causing the problem,

and by doing the reinstall as suggested by HawaiianPi all the dependences are updated to the current versions.

[hippy]

As I said in the anther thread I wonder if its because people are not always using full-upgrade which is now the recommended command

I wasn't even aware that "full-upgrade" was the recommended command.

It might say that in some documentation somewhere but I don't recall any announcement to that effect. I will admit I don't regularly and repeatedly read all the official documentation on the off-chance something may have changed but I doubt anyone else does either.

Seems MagPi might not have got the memo either as they are still using "update" then "upgrade".

Issue 88 did indicate "full-upgrade" in one place, but "upgrade" in another.

Added : Got the same broken package error when trying to update my Pi Zero W a few minutes ago. 'sudo apt-get full-upgrade' however did work.

[LTolledo]

I wasn't even aware that "full-upgrade" was the recommended command.

AFAIK this has been circulating around other forum topics
a few short months after RPi4B's release
something about Chromium? (or was it another package, corrections welcome)
from then on the "full-upgrade" procedure was highly recommended by RPF engineers
been using this procedure ever since...

[pcmanbob]

I think it was also recommended to fix the file manager problem as well,

its actually now the recommended use in the official docs

https://www.raspberrypi.org/documentati ... pdating.md

First, update your system's package list by entering the following command:

sudo apt update

Next, upgrade all your installed packages to their latest versions with the following command:

sudo apt full-upgrade

Note that full-upgrade is used in preference to a simple upgrade, as it also picks up any dependency changes that may have been made.

But I don't remember there ever being an official announcement about the change , just picked it up from this forum ,
in the past I used use dist-upgrade as I always have on my Linux X86 PC's

[hippy]

in the past I used use dist-upgrade as I always have on my Linux X86 PC's

I tend to use "upgrade" so I get to see what's "held back" so I'm aware of more major changes, then "dist-upgrade" when anything has been. "full-upgrade" now appended to that sequence.

[ShiftPlusOne]

dist-upgrade isn't a documented feature of apt. I believe it just runs full-upgrade. No need to do both.

[hippy]

dist-upgrade isn't a documented feature of apt. I believe it just runs full-upgrade. No need to do both.

I haven't yet got out of the habit of using 'apt-get', having had 'apt-get update && apt-get upgrade' drummed into me and using that for 8 years. 'full-upgrade' appears to work with 'apt-get'.

[pcmanbob]

Just to clarify my previous post.

old command I used was sudo apt-get dist-upgrade

which was replaced when raspbian changed to using just apt, sudo apt full-upgrade

I think you can still use the old command if you use apt-get which I do when including commands in scripts

I think apt is more interactive than apt-get and so is the recommended option for command line use.

[rpdom]

Just to clarify my previous post.

old command I used was sudo apt-get dist-upgrade

which was replaced when raspbian changed to using just apt, sudo apt full-upgrade

I think you can still use the old command if you use apt-get which I do when including commands in scripts

I think apt is more interactive than apt-get and so is the recommended option for command line use.

You can use apt or apt-get, whichever you prefer. apt is more "user friendly". Both will now accept dist-upgrade and full-upgrade to do the same thing.

[JandaAndy]

Hi. I'm new to the forum!

I had the same problem and this worked for me, I hope this helps someone else:

Code: Select all

sudo apt-get update
sudo apt-get upgrade
sudo apt update && sudo apt full-upgrade -y
sudo apt autoremove
sudo reboot now

Cheers
-A