purism@pureos:~$ sudo apt update
Get:1 https://repo.pureos.net/pureos byzantium InRelease [8737 B]
Get:2 https://repo.pureos.net/pureos byzantium-updates InRelease [4740 B]
Get:3 https://repo.pureos.net/pureos byzantium-security InRelease [4743 B]
E: Repository 'https://repo.pureos.net/pureos byzantium InRelease' changed its 'Label' value from 'None' to 'PureOS 10.x (byzantium)'
E: Repository 'https://repo.pureos.net/pureos byzantium InRelease' changed its 'Codename' value from 'None' to ''
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N]
I don’t think I have seen this before. Is it safe to answer “y” to this? The default is “N” and then apt update fails.
After I answered “Y”, then I ran: $ sudo apt update
and 1 package was available for upgrade. 1 package can be upgraded. Run 'apt list --upgradable' to see it.
$ apt list --upgradable
Listing... Done
libjava3d-java/byzantium 1.5.2+dfsg-17 all [upgradable from: 1.5.2+dfsg-16]
N: There is 1 additional version. Please use the '-a' switch to see it
$ apt list --upgradable -a
Listing... Done
libjava3d-java/byzantium 1.5.2+dfsg-17 all [upgradable from: 1.5.2+dfsg-16]
libjava3d-java/now 1.5.2+dfsg-16 all [installed,upgradable to: 1.5.2+dfsg-17]
$
It wouldn’t upgrade:
$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
$
Not being an apt guru, I ran Synaptic. It said this:
The following packages have unresolvable dependencies. Make sure that all required repositories are added and enabled in the preferences.
libjava3d-java:
Depends: libjava3d-jni (>=1.5.2+dfsg-17) but 1.5.2+dfsg-16+b1 is to be installed
Is this caused by “The PureOS infrastructure is being upgraded”?
The label has been changed to the old value now, so no prompt should happen anymore (unless you already accepted the changed value, in which case you’ll be prompted to change it back).
Note that debug, landing and octarine repositories (which are all disabled by default) still have a changed label and there are no plans to revert them to older ones.
No, doesn’t seem related. Both packages exist in version 1.5.2+dfsg-17 in the repository and both are installable on my phone.
What did not work for you? The only “gotcha” I notice is that apt prompts the user for confirmation and proceeds with the change while apt-get does not.
I was prompted to change it back, which I did. Then last night I did an apt update, and there where 19 more packages available for upgrade, in addition to the problematic libjava3d-java . Everything upgraded fine, so I’ll agree that the system “fixed itself”.
I forgot to mention all this time that this PureOS 10 issue was on my Librem 15v4. No issues on my Librem 5.
I have a friend with a Librem mini still on PureOS 9, and finally he wants to upgrade to PureOS 10 because Signal Desktop needs it. Would you say that the PureOS repo is now stable and ready for him to do a full system upgrade?
PureOS 10 (byzantium) has been a preferred stable* version for about 1.5 year now, based on Debian Bullseye which has been stable for almost 2 years. All PureOS 9 (amber) users are advised to upgrade - on phones, laptops, servers and minis.
* Not technically stable in a Debian sense since we keep updating some phone-related packages, but the base system is kept stable otherwise
Thanks, yes, I upgraded to PureOS 10 (byzantium) on the Librem 15v4 a year ago, and the Librem 5 & 14 both came with it installed.
When I said “stable” I did not mean “stable” in the Debian sense (Debian testing, stable, oldstable, etc.) I am referring to the repo infrastructure changes that started this thread and that might have caused my now-resolved update issue. I had some problems when I upgraded from PureOS 9 to 10, so I don’t want to add to those any problems caused by any still-in-progress changes to the repo. I want my friend’s upgrade to go smoothly.
I decided to accept manually the changes, and got the output as shown below, is that normal?
$ sudo apt update
Hit:1 http://debug.mirrors.debian.org/debian-debug bullseye-debug InRelease
Get:2 https://download.docker.com/linux/debian bullseye InRelease [43.3 kB]
Get:3 https://repo.pureos.net/pureos byzantium InRelease [8733 B]
Get:4 https://repo.pureos.net/pureos byzantium-updates InRelease [4745 B]
Get:5 https://repo.pureos.net/pureos byzantium-security InRelease [4746 B]
Ign:6 https://repo.pureos.net/pureos-debug byzantium-debug InRelease
Get:7 https://repo.pureos.net/pureos-debug landing-debug InRelease [3497 B]
Err:8 https://repo.pureos.net/pureos-debug byzantium-debug Release
404 Not Found [IP: 138.201.228.45 443]
E: Repository 'https://repo.pureos.net/pureos-debug landing-debug InRelease' changed its 'Label' value from 'PureOS Debug' to 'Development Suite (Debug Symbols)'
E: Repository 'https://repo.pureos.net/pureos-debug landing-debug InRelease' changed its 'Codename' value from 'None' to ''
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y
Ign:9 https://repo.pureos.net/pureos-debug landing-debug/main Translation-en
Get:9 https://repo.pureos.net/pureos-debug landing-debug/main Translation-en [452 B]
Reading package lists... Done
E: The repository 'https://repo.pureos.net/pureos-debug byzantium-debug Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
