- Joined
- Jun 7, 2023
- Messages
- 3
- Reaction score
- 0
Today we have tried to update the PBX to v20.
We received an error concerning azure linux repository packages.microsoft.com.
We received a strange call to this repository about "https://packages.microsoft.com/debian/10/prod bullseye main" that returned 404.
This repository does not exist. The right repository should be "https://packages.microsoft.com/debian/11/prod bullseye main".
What's the problem??
The problem is a bug (two) in the upgrade script by 3CX because MS repos use the distro version (in digit XX) inside the path of the repos.
In the raw 553 you can find "/bin/sed -i s/buster/bullseye/g /etc/apt/sources.list.d/*".
This is correct for all repo apart for microsoft one that needs the version number to change too (in path).
I correct the first bug with a new raw after that with "/bin/sed -i s/10/11/g /etc/apt/sources.list.d/*".
The second bug regards the update of the OS from 11 to 12. Here we are at raw 1168, the switch from bullseye to bookworm "/bin/sed -i s/bullseye/bookworm/g /etc/apt/sources.list.d/*".
We have to insert a new line to change also the digit in path from 11 to 12 in order to avoid 404 "/bin/sed -i s/11/12/g /etc/apt/sources.list.d/*".
Clearly, you have to execute the script from console because every time you launch it from GUI it downloads a new one and overwrites the existant.
You can download also the script from internet, modify it and execute it from /tmp dir of the VM.
We successfully upgraded our PBX in Azure without recreate VM.
Hoping it could help you,
bye bye,
Graziano.
We received an error concerning azure linux repository packages.microsoft.com.
We received a strange call to this repository about "https://packages.microsoft.com/debian/10/prod bullseye main" that returned 404.
This repository does not exist. The right repository should be "https://packages.microsoft.com/debian/11/prod bullseye main".
What's the problem??
The problem is a bug (two) in the upgrade script by 3CX because MS repos use the distro version (in digit XX) inside the path of the repos.
In the raw 553 you can find "/bin/sed -i s/buster/bullseye/g /etc/apt/sources.list.d/*".
This is correct for all repo apart for microsoft one that needs the version number to change too (in path).
I correct the first bug with a new raw after that with "/bin/sed -i s/10/11/g /etc/apt/sources.list.d/*".
The second bug regards the update of the OS from 11 to 12. Here we are at raw 1168, the switch from bullseye to bookworm "/bin/sed -i s/bullseye/bookworm/g /etc/apt/sources.list.d/*".
We have to insert a new line to change also the digit in path from 11 to 12 in order to avoid 404 "/bin/sed -i s/11/12/g /etc/apt/sources.list.d/*".
Clearly, you have to execute the script from console because every time you launch it from GUI it downloads a new one and overwrites the existant.
You can download also the script from internet, modify it and execute it from /tmp dir of the VM.
We successfully upgraded our PBX in Azure without recreate VM.
Hoping it could help you,
bye bye,
Graziano.
