Please manually run some new sysadmin commands - AND/OR - change the following file(s) before your next apt update in order to avoid accidentally upgrading from Debian 12 to Debian 13:
$ sudo sed -i 's/ stable / bookworm /g' /etc/apt/sources.list.d/archive_uri-http_ftp_debian_org_debian-bookworm.list
$ sudo sed -i 's/ stable / bookworm /g' /etc/apt/sources.list.d/archive_uri-http_ftp_debian_org_debian_-bookworm.list
$ sudo sed -i 's/ stable / bookworm /g' /etc/apt/sources.list
Note that file names may differ slightly depending on your mirrors.
Then to double-check that you are in the clear:
$ apt-add-repository -L | grep stable
…should return nothing.
Running FreePBX 17 on Debian 13 is not supported – please refer to our FreePBX Versions topic for more details on future release schedules.
17 system on Vultr created using the sangoma script in July of 2024:
root@FreePBX17:/etc/apt/sources.list.d# sudo sed -i 's/stable/bookworm/g' /etc/apt/sources.list.d/archive_uri-http_ftp_debian_org_debian-bookworm.list
sed: can't read /etc/apt/sources.list.d/archive_uri-http_ftp_debian_org_debian-bookworm.list: No such file or directory
Curious what you did yesterday… but understand that fixing the issue is more of a concern right now.
Most Debian ISO images come with Rescue mode – you should be able to boot up with that, mount your drives, then manually back-up your data to another USB drive.
After that, it depends. You might be able to fix, or, you might have to reinstall. If you have another hard drive, then it might be easiest to get back up and running with a fresh install on that, followed by re-attaching the old drive – or the backup USB – in order to restore your data on to the new disk.
I thought the whole point of this Debian stuff was to keep everything up to date and modern with upstream management of updates? So FreePBX Users would always be able to roll with “stable”?
The debian team released RC1 in July, When a company platforms itself on a product it seems reasonable that all of this should have been in progress since Alpha 1 (December) allowing these things to be worked through. Especially since 13 is an LTS. In any case the time to discover and start working on an issue for the platform that can always be up to date was 6 months ago and not 2 days post stable release.
$ sudo sed -i 's/stable/bookworm/g' /etc/apt/sources.list
Thank you for posting that BTW – we are looking at more generic fixes using native Debian apt repository management tooling, probably as part of a sysadmin module update.
root@freepbx:~# cat /etc/*-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@freepbx:~# cat /etc/apt/sources.list
deb https://deb.debian.org/debian bookworm main contrib non-free non-free-firmwa re
deb-src https://deb.debian.org/debian bookworm main contrib non-free non-free-fi rmware
deb https://deb.debian.org/debian-security/ bookworm-security main contrib non-f ree non-free-firmware
deb-src https://deb.debian.org/debian-security/ bookworm-security main contrib n on-free non-free-firmware
deb https://deb.debian.org/debian bookworm-updates main contrib non-free non-fre e-firmware
deb-src https://deb.debian.org/debian bookworm-updates main contrib non-free non -free-firmware
# deb https://deb.debian.org/debian bookworm-backports main contrib non-free non -free-firmware
# deb-src https://deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware
deb https://debian.mirror.constant.com bookworm main contrib non-free non-free-f irmware
deb-src https://debian.mirror.constant.com bookworm main contrib non-free non-fr ee-firmware
Can someone please tell me exactly what we should be looking for in the above output please as $ grep -nir stable /etc/apt does not return “nothing” after sed -i ‘s/stable/bookworm/g’ /etc/apt/sources.list.d/archive_uri-http_ftp_debian_org_debian-bookworm.list, and I am not comfortable throwing commands around on dozens of deployments when I don’t know whether this is having a positive impact, or perhaps needs an underscore here or there. Really? See not “nothing” below:
root@freepbx:~# grep -nir stable /etc/apt
/etc/apt/apt.conf.d/50unattended-upgrades:9:// a,archive,suite (eg, "stable")
/etc/apt/apt.conf.d/50unattended-upgrades:26: // archives (e.g. from testing to stable and later oldstable).
/etc/apt/apt.conf.d/50unattended-upgrades:38: // new stable).
/etc/apt/apt.conf.d/50unattended-upgrades:39:// "o=Debian,a=stable";
/etc/apt/apt.conf.d/50unattended-upgrades:40:// "o=Debian,a=stable-updates";
Something that sounds as serious and widespread as this needs to be communicated much better.
Understanding that unattended-upgrades is not OOBE with FreePBX 17 Distro but trying to help… those lines you pasted look to be // commented out. However, pausing unattended-upgrades and/or any other updates via third-party orchestration tools – e.g. ansible, puppet, etc. – might be worth considering until the (potentially manual) change from ‘stable’ to ‘bookworm’ repos is confirmed.
This is a standard install from the official Sangoma repo done a few hours ago to test the issue. My point here is that the advice probably shouldn’t say “should return nothing”. Perhaps instead, it might return something, but don’t worry unless you see this: xxx. It needs to be made clearer as to whether we can sit on this and wait for Sangoma, or not.
Why was the Debian repo being re-defined anyway? The premise is that FreePBX is already installed upon Debian Bookworm. Why does the installer script add this?
If you are doing this to add the non-free and non-free-firmware components isn’t that accomplished using apt-add-repository -c non-free -c non-free-firmware ??
Are you about to update FreePBX 17 ? 
