Forum

You have to redirect output into a file


for example. On my Pi3/4 devel installation I have 1033 packages installed

Here's my output...... Hope it helps.

(7th Nov, 2019 07:26 PM)Skywatch Wrote: [ -> ]Here's my output...... Hope it helps.

Thanks, we will see

Did it. Some packages could not be installed


Distribution upgrade finished without serious issues [1], and system comes up as expected.

So, one or a couple of those old packages breaks your upgrade. You should get rid of them

If this is your Raspbian based installation for Pi2, you have to replace raspbian-archive-keyring with debian-archive-keyring before upgrade. This is VERY important

[1] lcdproc reported error but did not brake the upgrade process


but a sudo apt-get install -f && sudo apt-get install --reinstall xbian-update
did it

(7th Nov, 2019 10:05 AM)Nachteule Wrote: [ -> ]You have to redirect output into a file

Terminal

sudo dpkg -l | awk '/^ii/{print $2}' > /tmp/installed-packages.txt

for example. On my Pi3/4 devel installation I have 1033 packages installed

Well this is my list of packages on pastebin

(8th Nov, 2019 05:41 AM)jakenl Wrote: [ -> ]

(7th Nov, 2019 10:05 AM)Nachteule Wrote: [ -> ]You have to redirect output into a file

Terminal

sudo dpkg -l | awk '/^ii/{print $2}' > /tmp/installed-packages.txt

for example. On my Pi3/4 devel installation I have 1033 packages installed

Well this is my list of packages on pastebin

Looks good. Will see tomorrow what I can do

So, the update did not finished without error, that f.... nginx breaks installation

The maintenance script checks if server can be (re-)started sucessfully, but if it does not start, installation breaks with an error.

HOW STUPID IS THAT !



I modified that stupid maintenance script /var/lib/dpkg/info/nginx-full.postinst (see below, look for '''MODIFIED!!!) and now nginx stops complaining error


Finally, we have to run sudo apt-get install --reinstall xbian-update before we can reboot system and everything is fine


Btw: The package list has some differences, but I don't believe that this is a problem

Should I copy paste that modified script and than run the upgrade again? Finishing it with the xbian update reinstall?

(8th Nov, 2019 08:37 AM)jakenl Wrote: [ -> ]Should I copy paste that modified script and than run the upgrade again? Finishing it with the xbian update reinstall?

No, you have to modify the upgraded nginx file. That means, you have to run the upgrade procedure until it fails, then modify the script, run sudo apt-get install -f and sudo apt-get install --reinstall xbian-update before reboot
Maybe running a sudo apt-get upgrade could be useful, but was not necessary here

I finally got it sorted, with your help I got it solved!

I also had PHP7.3-curl not cooperating anymore after the upgrade to Buster, turned out that I should have updated this as well:

etc/apt/sources.list.d/php.list

update line to:

deb https://packages.sury.org/php/ buster main

(10th Nov, 2019 12:23 AM)jakenl Wrote: [ -> ]I finally got it sorted, with your help I got it solved!

I also had PHP7.3-curl not cooperating anymore after the upgrade to Buster, turned out that I should have updated this as well:

etc/apt/sources.list.d/php.list

update line to:

deb https://packages.sury.org/php/ buster main

Thats fine

I suspected that you had a separate repository for PHP

(7th Nov, 2019 10:55 PM)Nachteule Wrote: [ -> ]Did it. Some packages could not be installed

Thank you for taking the time to look into this. It is a mystery to me where all those packages came from as this is the simplist Xbian build I have with just fan and dac added.

I'll look into it more tomorrow I hope and see what I can turn up.

As to the solution, well I may just leave things as they are for a while longer afterall. It's working as it is and as I said I have no 'need' to upgrade.

(10th Nov, 2019 05:45 AM)Skywatch Wrote: [ -> ]As to the solution, well I may just leave things as they are for a while longer afterall. It's working as it is and as I said I have no 'need' to upgrade.

You're right. There no need for upgrade.

But you should keep in mind, that Kodi v19 will never be available for Stretch

(10th Nov, 2019 06:33 AM)Nachteule Wrote: [ -> ]You're right. There no need for upgrade.

But you should keep in mind, that Kodi v19 will never be available for Stretch

At this very moment I am trying it on the pi3 xbian build (the one with the sql db on it) so will see how it goes.

I do think I found where I went wrong with this though

In /etc/apt/sources.list.d/xbian.list I had changed rpi2-stretch to rpi2-buster, but didn't chage armv7l-stretch
to armv7l-buster, so no wonder it got it's knickers in a twist!

Maybe I'll try the first one again when I get time.

---

After trying again as above I get to this point and select YES.

x Restart services during package upgrades without asking? x
x x
x x
tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqu
x < Yes > < No > x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj

Then this happens and the ssh connection is disconnected...... Is this right

Restarting services possibly affected by the upgrade:
smbd: restarting...done.
openbsd-inetd: restarting...

---

Both reporting version as buster now, but I am getting this....

xbian@cinema2 ~ $ sudo apt-get install --reinstall xbian-update
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

I already wanrned: DO NOT start dist-upgrade inside of a ssh connection!

You have to run dpkg -- .... whatever (forgot the right command)

Sorry, to much red wine drunken today at the celebration of the first birthday of my grandchildren.

You have to run command: sudo dpkg --configure -a
for continuing installation process