Update to 20.13 not arrived

Is’t the actual version of FreedomBox 20.13? My one is still 20.12.2 and I suspect something is wrong. Some days ago i used a snapshot for a rollback and in the list of snapshots is a message: will be used at next boot… can this have an effect on the updates?
Freedombox works normally except problems with Matrix Synapse/Coturn since the transition from Riot to Element.
I tried a update manually and got some errors:

sudo apt-get upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
The following packages have been kept back:
matrix-synapse
The following packages will be upgraded:
ca-certificates
1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 158 kB of archives.
After this operation, 3072 B disk space will be freed.
Do you want to continue? [Y/n]
Get:1 http://deb.debian.org/debian stable-updates/main armhf ca-certificates all 20200601~deb10u1 [158 kB]
Fetched 158 kB in 0s (664 kB/s)
Failed to set locale. Fix your system.
Failed to set locale. Fix your system.
quota not working (qgroup not set)
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = “de_DE.UTF-8”
are supported and installed on your system.
perl: warning: Falling back to the standard locale (“C”).
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Preconfiguring packages …
(Reading database … 107430 files and directories currently installed.)
Preparing to unpack …/ca-certificates_20200601~deb10u1_all.deb …
Unpacking ca-certificates (20200601~deb10u1) over (20190110) …
Setting up ca-certificates (20200601~deb10u1) …
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Updating certificates in /etc/ssl/certs…
13 added, 15 removed; done.
Processing triggers for ca-certificates (20200601~deb10u1) …
Updating certificates in /etc/ssl/certs…
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d…
done.
Failed to set locale. Fix your system.
Failed to set locale. Fix your system.
quota not working (qgroup not set)
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = “de_DE.UTF-8”
are supported and installed on your system.
perl: warning: Falling back to the standard locale (“C”).
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = “de_DE.UTF-8”
are supported and installed on your system.
perl: warning: Falling back to the standard locale (“C”).
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = “de_DE.UTF-8”
are supported and installed on your system.
perl: warning: Falling back to the standard locale (“C”).
Scanning processes…
Scanning linux images…

Running kernel seems to be up-to-date.

Failed to check for processor microcode upgrades.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

Maybe i have to reinstall the Freedombox?

FreedomBox is plugged into a router
I bought my kit July 2019
The version of FreedomBox 20.12.1.

It’s not due to the snapshots. FreedomBox 20.13 is in the Debian NEW queue: https://ftp-master.debian.org/new/freedombox_20.13.html. From here, it needs to be manually approved, before it will flow in as an update.

And couldn’t it be possible for users to toggle a switch to install these NEW queue packages? (To test backports on their stable freedombox field-configurations, before they are officially released.)

Then that would sound like a much better solution for “field tested backports: default delay for installing new feature packages”.

Hi James,
could you tell me the status of 20.13?
So far I still have 20.12.1 running on my two freedomboxes and when I run a manual update it shows no updates are available.
I am just wondering if something is wrong in my setup or if its just the delay expected for the 20.13 release.

Thanks Chris

Yes, 20.13 was still in the NEW queue until a few days ago, when it was rejected.

Next upload will be 20.14.

2 Likes