Hey all, i am running Raspberry Pi3 and decided to upgrade the system to Debian stretch. The update process was working until I ran into this error
dpkg: error processing package rbp2-device-osmc (--remove):
subprocess installed pre-removal script returned error exit status 1
Errors were encountered while processing:
rbp2-device-osmc
E: Sub-process /usr/bin/dpkg returned an error code (1)
I have tried the suggested
apt --fix-broken install
To no avail
WARNING: You have tried to remove a package that is essential to OSMC's operation.
To undo these changes, run 'sudo apt-get -f install'.
The OSMC wont run now and the install wont finish. I am in a paradox. Any help please.
We need to see grab-logs -a
First you should have waited till at least this is released for testing.
Well secondly you may want to tell how you did that? I hope you edited all repositories correctly.
Also to let you know we already had members to update successfully to stretch
Last question why do you write “Rasbian” into the title?
1 Like
Debian Stretch isn’t officially supported yet.
If you have the package rbp2-device-osmc you should have upgraded to Debian not Raspbian.
You should reinstall OSMC
Well it is debian, just decyphering the hardware, sorry. How do I go about reinstalling OSMC? Seems any attempt to remove this file fails.
This is my source
deb http://ftp.debian.org/debian stretch main contrib non-free
deb http://ftp.debian.org/debian/ stretch-updates main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free
deb http://apt.osmc.tv stretch main
deb http://ftp.debian.org/debian stretch-backports main contrib non-free
You can reinstall OSMC from osmc.tv/downloads.
stretch-backports isn’t a good idea when we haven’t fully verified
stretch yet.
thanks, I meant to comment that out.
As for the re-install i am working on backing up the system since i use the same pi for a nextcloud instance.
Thanks and sorry for being late https://paste.osmc.tv/exobawahus
As already mentioned, you’ll need to reinstall OSMC.
The following bit is “interesting”:
e[1mdpkg:e[0m error processing package rbp2-device-osmc (--remove):
subprocess installed pre-removal script returned error exit status 1
e[1mdpkg:e[0m libconfuse0:armhf: dependency problems, but removing anyway as you requested:
udisks-glue depends on libconfuse0 (>= 2.5).
Removing libconfuse0:armhf (2.7-5) ...
e[1mdpkg:e[0m rbp2-mediacenter-osmc: dependency problems, but removing anyway as you requested:
rbp2-device-osmc depends on rbp2-mediacenter-osmc; however:
Package rbp2-mediacenter-osmc is to be removed.
Removing rbp2-mediacenter-osmc (17.3.0-6) ...
e[1mdpkg:e[0m diskmount-osmc: dependency problems, but removing anyway as you requested:
rbp2-device-osmc depends on diskmount-osmc.
Removing diskmount-osmc (1.4.4) ...
Removing 'diversion of /etc/udisks-glue.conf to /etc/udisks-glue.conf.distributed by diskmount-osmc'
Removing 'diversion of /sbin/mount.exfat-fuse to /sbin/mount.exfat-fuse.distributed by diskmount-osmc'
Removing 'diversion of /lib/udev/rules.d/60-cdrom_id.rules to /lib/udev/rules.d/60-cdrom_id.rules.distributed by diskmount-osmc'
Removing udisks-glue (1.3.5-1) ...
Upgrading to stretch totally hosed OSMC. “Interesting” and just a bit scary.
Probably using udisks2 now
If that’s the case we can buIld it downstream.
At least we are not using new polkits which use JavaScript for rules…
Correct. Only udisks2 (version: 2.1.8-1) is now available in stretch. udisks-glue also no longer exists in stretch; perhaps its function has been incorporated into udisks2.
I’ve not followed it closely but udisks2 has attracted some criticism and doesn’t seem to be backward compatible with v1.
udisks2 is not what we want, so we’ll build udisks1 and distribute that in OSMC.
Since Q4 2015 we have planned to do away with udisks, but a clarification of requirements is needed. It’s quite limiting and hacky.
I suspect next Debian (10) will feature updated PolKit which will be painful.