Error installing updates

Hello guys

Just finally got round to updating my Rpi3, just getting some errors and a bit stuck…

Think Ive got a similar issue in that I may have used packages that conflict with those on OSMC? Like on this thread… Error installing: rpb-userland-osmc (1.9.0-1) on latest update - #24 by sam_nazarko

Tried diverting JustBoomDigi but didnt seem to work.

I know Ive not got the “cleanest” osmc with some customisations, but Ive always managed to get it to update… cant imagine having to do a clean rebuild- it would be most painful!

thanks for your help…

http://pasted.co/fb1a1c33

snips from the log:

Unpacking rbp-userland-osmc (2.3.1-1) over (1.7.0-1) …
dpkg: error processing archive /var/cache/apt/archives/rbp-userland-osmc_2.3.1-1_armhf.deb (–unpack):
trying to overwrite ‘/usr/bin/raspi-config’, which is also in package raspi-config 20161207
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

Preparing to unpack …/rbp2-device-osmc_1.4.0_armhf.deb …
Unpacking rbp2-device-osmc (1.4.0) over (1.3.3) …
dpkg: error processing archive /var/cache/apt/archives/rbp2-device-osmc_1.4.0_armhf.deb (–unpack):
trying to overwrite ‘/usr/share/alsa/cards/JustBoomDigi.conf’, which is also in package libasound2-data 1.0.28-1+rpi2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

dpkg: error processing archive /var/cache/apt/archives/rbp-userland-osmc_2.3.1-1_armhf.deb (–unpack):
trying to overwrite ‘/usr/bin/raspi-config’, which is also in package raspi-config 20170503
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for libc-bin (2.19-18+deb8u9) …
Errors were encountered while processing:
/var/cache/apt/archives/rbp-userland-osmc_2.3.1-1_armhf.deb

Well you may want to start by removing all the conflicting packages:
raspi-config 20161207
libasound2-data 1.0.28-1+rpi2
raspi-config 20170503

Also for future posting please use the paste.osmc.io

righto cheers…
apt-get --purge remove raspi-config ? etc

osmc@osmc:~$ sudo apt-get --purge remove raspi-config
Reading package lists… Done
Building dependency tree
Reading state information… Done
You might want to run ‘apt-get -f install’ to correct these:
The following packages have unmet dependencies:
rbp-userland-dev-osmc : Depends: rbp-userland-osmc (= 2.3.1-1) but 1.7.0-1 is to be installed
E: Unmet dependencies. Try ‘apt-get -f install’ with no packages (or specify a solution).

upgrade rbp-userland-osmc somehow?

Give that a try but broken dependencies are a pain

yea gave that a go… still no bananas.
EDIT: seems the offending package was raspi-config… removed the sucker, everything else seemed to come good :slight_smile:
sudo dpkg -P raspi-config

only got this lot now, which doesnt look too serious…??

W: GPG error: http://mirrordirector.raspbian.org jessie InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 9165938D90FDDD2E

That error is some issue with that repo. Seek support for this from the maintainers there. It has nothing to do with OSMC or it’s included repos.

You added the Raspbian repo but not the key. My OSMC will fail updates if key is not valid for security reasons

1 Like

Tried apt-get -f install but got an error. I’ve been Kodi-less for too long now…

login as: osmc
osmc@192.168.1.15’s password:

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Jun 21 19:50:38 2017 from achandra-lap
osmc@osmc:~$ sudo apt-get -f install
Reading package lists… Done
Building dependency tree
Reading state information… Done
Correcting dependencies… Done
The following packages were automatically installed and are no longer required:
rbp2-image-4.4.27-7-osmc rbp2-image-4.4.27-9-osmc
Use ‘apt-get autoremove’ to remove them.
The following extra packages will be installed:
rbp-userland-osmc
The following packages will be upgraded:
rbp-userland-osmc
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
6 not fully installed or removed.
Need to get 0 B/1195 kB of archives.
After this operation, 17.4 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up debian-archive-keyring (2017.5~deb8u1) …
Removing obsolete conffile /etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg …
Removing obsolete conffile /etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg …
(Reading database … 78766 files and directories currently installed.)
Preparing to unpack …/rbp-userland-osmc_2.3.1-1_armhf.deb …
Unpacking rbp-userland-osmc (2.3.1-1) over (2.2.0-1) …
dpkg: error processing archive /var/cache/apt/archives/rbp-userland-osmc_2.3.1-1_armhf.deb (–unpack):
trying to overwrite ‘/usr/bin/raspi-config’, which is also in package raspi-config 20160527
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for libc-bin (2.19-18+deb8u10) …
Errors were encountered while processing:
/var/cache/apt/archives/rbp-userland-osmc_2.3.1-1_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
osmc@osmc:~$

Tried this too ;(

osmc@osmc:~$ sudo apt-get install --reinstall rbp-userland-osmc
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
rbp2-image-4.4.27-7-osmc rbp2-image-4.4.27-9-osmc
Use ‘apt-get autoremove’ to remove them.
The following packages will be upgraded:
rbp-userland-osmc
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
5 not fully installed or removed.
Need to get 0 B/1195 kB of archives.
After this operation, 17.4 kB of additional disk space will be used.
(Reading database … 78766 files and directories currently installed.)
Preparing to unpack …/rbp-userland-osmc_2.3.1-1_armhf.deb …
Unpacking rbp-userland-osmc (2.3.1-1) over (2.2.0-1) …
dpkg: error processing archive /var/cache/apt/archives/rbp-userland-osmc_2.3.1-1_armhf.deb (–unpack):
trying to overwrite ‘/usr/bin/raspi-config’, which is also in package raspi-config 20160527
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for libc-bin (2.19-18+deb8u10) …
Errors were encountered while processing:
/var/cache/apt/archives/rbp-userland-osmc_2.3.1-1_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
osmc@osmc:~$

Run dpkg -l | grep raspi-config

Looks like you still have (at least) one version installed.

Reinstall. You’ve borked your system by installing packages that are not supported.

i’ve also had problems on updating my system, but solved it like so:
dpkg -l | grep "<package name>". If the package that causes the problem it’s still listed, uninstall it with dpkg like so: sudo dpkg -r <package name> and purge it’s config files using sudo dpkg -P <package name> . Hope this helps.

1 Like

Just reporting back mines all sorted…
All nicely updated/upgraded to latest.
it did complain about that source again as follows:
W: GPG error: http://archive.raspberrypi.org jessie InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY

but a quick google to add the key back and now clean as a whistle! :slight_smile:

Take note of the 16 digit key and place it into the following statement.

gpg --keyserver keys.gnupg.net --recv-key x0x0x0x0x0x0x0x0
gpg -a --export x0x0x0x0x0x0x0x0 | sudo apt-key add -

sudo apt-get update && sudo apt-get dist-upgrade

cheers

I don’t believe we add this source, so not sure if it’s an OSMC issue, or if it will benefit other users.

Sam

Yea, I would’ve added this source to add customisations/packages. One of the reasons I and I expect a number of other OSMC users chose OSMC, is due to its flexibility and possibility of running other stuff other than OSMC in tandem on my Pi3. So believe it would benefit others who like me would have additional stuff running on top of OSMC.
Im not running anything too silly; just RetrOSMC, measureIT solar/power monitoring and Squeezebox server.

Appreciate the help even though your within your rights of course to tell us custom users to bugger off!

That’s fine – just make sure you keep that repository up to date (URL and key) as we don’t manage it for you.