Apt-get dist-upgrade

Help and Support Raspberry Pi
1

Hi there,

I saw some stuff here about a theme, settings app and Alpha 3, so I thought lets upgrade :smile:

It seems that it doesn’t seem to work correct: http://paste.osmc.io/nujitarumo.vhdl
Any that could help me out, what went wrong?

Thnx in advance!

2

I just tried it and it looks like it worked but there are no updates to get.

osmc@osmc:~$ sudo apt-get dist-upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
osmc@osmc:~$

3

Just did a ‘sudo apt-get upgrade’ … that gave me all kind of permission errors:

Preparing to unpack .../rbp-bootloader-osmc_1.0-3_armhf.deb ...
Unpacking rbp-bootloader-osmc (1.0-3) over (1.0-2) ...
dpkg: error processing archive /var/cache/apt/archives/rbp-bootloader-osmc_1.0-3_armhf.deb (--unpack):
 unable to make backup link of `./boot/LICENCE.broadcom' before installing new version: Operation not permitted
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/rbp-bootloader-osmc_1.0-3_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Since all the permissions seems to be correct, I deleted the files it needed to upgrade.
That left me with all updated, except ‘mediacenter-addon-osmc’.
I upgraded that with ‘sudo apt-get upgrade mediacenter-addon-osmc’ and that worked perfectly.

Now I only have 1 left:

root@osmc:/home/osmc# sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree        
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  armv7-splash-osmc
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1208 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
4

Both give me the same output, maybe I have the latest build (proposed -Alpha 3)

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
osmc@osmc:~$ sudo apt-get upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
osmc@osmc:~$ sudo apt-get dist-upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
osmc@osmc:~$

5

Yup, think so as well … I now only need to know if I need 'armv7-splash-osmc’instead of ‘rbp-splash-osmc’.
And if so … where did it go wrong :confused:

6

You don’t want this package on Pi

Will fix soon

7

Wrong dependency?

8

It will be fixed soon

9

Hi all, just got the very same error with the April update right now, bootloader not installing because of 4 files in boot, which I renamed 1 by 1 with ‘.old’ at the end, and right after everything installed without problem. The 4 files have been reinstalled during the update, seem to be identical to the .old. Strange, no? Anyone with the same issue?
PS my boot is correctly mounted :slight_smile:

Grabbed a log just in case: https://paste.osmc.tv/egalaqumop

10

This thread is three and a half years old.

I doubt the issue is related.

11

Thanks for your answer Sam, had seen that yet the symptoms and the solution were exactly the same, that’s why I thought I’d report it for potential future ‘similar’ issues.
had found the thread with copy-paste of the whole error message in Google.

12

For information, same issue again with August update, the very same 4 files. Appear when trying to update bootloader. Same solution = rename with .old at the end (delete would also possibly do the trick)

13

It’s an anomaly so specific that it only occurs in your system in 4 years. I would backup your config and reimage if I were you. Why won’t you tell us which 4 files you are renaming? That seems like useful info to me.

14

I would if I really had to. But as it still works and does quite a lot of stuff, I don’t want to spend hours setting it up again unless I have to.

The 4 files are all in boot:

  • LICENCE.broadcom
  • bootcode.bin
  • fixup_x.dat
  • start_x.elf

Happened so far only twice, ok in 2018 whereas @Theetjuh had it in 2015 with an alpha release, but still it was the very same issue and solution.

15

Hi there

just happened again with Oct’18 update. Same symptoms, same solution. Perhaps linked to the update of rbp-bootloader-osmc package?

16

This is probably the best advice.

17

You are the only person that seems to be affected. This indicates a problem with your system, not with OSMC itself. A reinstall is your solution.