Forum

dist-upgrade lists the following.....


Does it look safe to continue and try it ???

Nope, then do what i did

Just manually install the held packages manually until you covered them all.

(14th Sep, 2015 09:24 PM)CurlyMo Wrote: [ -> ]Nope, then do what i did

Just manually install the held packages manually until you covered them all.

Xbian won't have any of it

I tried to upgrade again using xbian-config

I'm getting the same problems: kodi starts at boot then abort
doing service xbmc restart solves the problem till next boot

I have the following error:

Configurazione di watchdog (5.14-3)...
/run/udev or .udevdb or .udev presence implies active udev. Aborting MAKEDEV invocation.
/run/udev or .udevdb or .udev presence implies active udev. Aborting MAKEDEV invocation.
update-rc.d: /etc/init.d/watchdog: file does not exist
dpkg: errore nell'elaborare il pacchetto watchdog (--configure):
il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
Si sono verificati degli errori nell'elaborazione:
watchdog

And I have the systemd error "Failed to start user service: Unknown unit: user@1000.service"

That's a different issue and for clarity I suggest you open a new thread about it.

Hi again,

Thanks CurlyMo, the trick with installing the held back packages worked, could install some at the time, not all but eventually everything was installed and lastly the xbian-update would install.

M

Thats funny i only have 3 packages to update (one that is kept back)


Raps Pi 1 B, tried right now but did not give the ok to proceed...

after installing xbian-package-repo you are advised to apt-get update again to refresh repositories
then you will have hundreds of updates...

(15th Sep, 2015 01:21 AM)Fabio72 Wrote: [ -> ]after installing xbian-package-repo you are advised to apt-get update again to refresh repositories
then you will have hundreds of updates...

that makes sense... is it safe to update right now or should i wait?

I'd wait if I were you!

(15th Sep, 2015 03:25 AM)Skywatch Wrote: [ -> ]I'd wait if I were you!

That was what i was thinking... last time i rushed to update i ended up to re-install and configure my 2 Pi's...

(15th Sep, 2015 05:09 AM)Exnor Wrote: [ -> ]That was what i was thinking... last time i rushed to update i ended up to re-install and configure my 2 Pi's...

Yup! - Same thing here too

Took me about 4 hours plus to get it all back and running again.

For now, they are all working and doing what they should with only minor issues, so I don't really care that much. But it would be good to test a working upgrade sometime soon. Maybe bleeding edge is not for me afterall!

OK, new update.

I have now upgraded 2x Rpi1 machines and both seem OK (with a minor bug I have reported with log file).

Basically from Xbian-config update and then upgrade all packages *except* xbian-package-xbmc and xbian-update. These were the packages causing the 'dependency' issues so this should work, it did for me.

When it is done you will be able to update libnfs1 (be sure *not* to select xbian-update). When it is done reboot when told to.

Then do xbian-config again, update and then upgrade - Select "update all".
This time there will be 'hundreds' of packages to upgrade. Don't worry about the conflict messages, they don't seem to be a problem!
Go for a beer or to a movie as it takes a loooong time
Reboot and after that you should be back in business. I will try the pi2 this morning and see how that goes.

Note that this does *NOT* work with Rpi2.
Update ends with W: GPG error: http://http.debian.net stable Release: The following
Upgrade complains that E: There are problems and -y was used without --force-yes.

UPDATE - The GPG fix allowed the upgrade to go ahead on Rpi2, but after upgrade no audio output at all.

I tried twice to update, but every time I ended with a problem-full system so I reverted back another time and I'm waiting a bit.

Problems where:
watchdog not installing
Unknown unit: user@1000.service"
kodi not starting at boot
and, at the last try, ssd get disabled and impossible to re-enable

Now my system is up-to-date just before xbian-package-repo (and xbian-update correctly remains at the current version)

(15th Sep, 2015 04:26 PM)Skywatch Wrote: [ -> ]When it is done you will be able to update libnfs1 (be sure *not* to select xbian-update). When it is done reboot when told to.

My xbian-update version is 20150817-0


The system is working fine with nfs root. I never touched libnfs1.
How do I proceed to do a clean upgrade?