Posts: 361
Joined: Fri Oct 05, 2012 11:49 am

libraspberrypi-bin libraspberrypi0 raspberrypi-bootloader

Fri Apr 04, 2014 9:31 pm

Hi all, I'm using raspbian jessie, my /etc/sources.list is

Code: Select all

deb jessie main contrib non-free rpi

deb sarge contrib
deb sarge contrib

deb-src jessie main contrib non-free rpi

deb-src sid main contrib non-free
deb-src experimental main contrib non-free
With Webmin I figured out that I have 3 packages that still be from Wheezy

Code: Select all

libraspberrypi-bin	armhf Miscellaneous Raspberry Pi utilities	New version 1.20140319-1	Wheezy
libraspberrypi0	armhf EGL/GLES/OpenVG/etc. libraries for the Raspberry Pi's VideoCore IV	New version 1.20140319-1	Wheezy
raspberrypi-bootloader	armhf Raspberry Pi bootloader	New version 1.20140319-1	Wheezy
Is it fine?

Posts: 741
Joined: Thu Jan 09, 2014 5:38 am
Location: USA

Re: libraspberrypi-bin libraspberrypi0 raspberrypi-bootloade

Sat Apr 05, 2014 2:04 am

To answer your question, no, it probably doesn't matter. But you probably want more of an answer than that.

It probably happened because those packages got held back for some reason. Are they mentioned when you do an apt-get upgrade, in the form of "the following packages will NOT be upgraded" or something to that effect? I suspect they would be. Usually this is either because you have told apt to hold them back from future upgrades, or because upgrading them requires installing new packages or removing conflicting packages, and you never did a dist-upgrade. (apt-get upgrade will never change the install status of a package, whereas apt-get dist-upgrade can do that, in order to resolve changing dependencies beyond version changes.)

If you'd like to bring them up to date, you can either apt-get dist-upgrade, or apt-get install [all 3 package names] and it should update them and install any dependencies.

Edit: Taking a closer look at what those packages are, once they're upgraded you might want to issue a "sudo rpi-update" command. This will bring your firmware up to date. It looks like those packages are related to that, but I would have expected that apt would have fetched the new versions anyway, but just not installed them until that command was issued. I'm probably right about changing dependencies (I'd guess that the library packages that you listed have been replaced with new ones.) so what I wrote above still holds true. I'm just adding this additional suggestion.

Return to “Advanced users”