Information changes in amber release files

Software PureOS
1

The InRelease files for amber, amber-security & amber-updates have recently been updated. The output of command apt-get update now looks like this:

Get:1 https://repo.pureos.net/pureos amber InRelease [4,731 B]
Get:2 https://repo.pureos.net/pureos amber-security InRelease [4,738 B]
Get:3 https://repo.pureos.net/pureos amber-updates InRelease [4,735 B]
Reading package lists... Done
E: Repository 'https://repo.pureos.net/pureos amber InRelease' changed its 'Label' value from 'None' to 'PureOS 9.x (amber)'
E: Repository 'https://repo.pureos.net/pureos amber InRelease' changed its 'Codename' value from 'amber' to ''
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
E: Repository 'https://repo.pureos.net/pureos amber-security InRelease' changed its 'Label' value from 'None' to 'PureOS 9.x Security Updates'
N: Repository 'https://repo.pureos.net/pureos amber-security InRelease' changed its 'Version' value from '9' to ''
E: Repository 'https://repo.pureos.net/pureos amber-security InRelease' changed its 'Codename' value from 'amber-security' to ''
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
E: Repository 'https://repo.pureos.net/pureos amber-updates InRelease' changed its 'Label' value from 'None' to 'PureOS 9.x Bugfix Updates'
N: Repository 'https://repo.pureos.net/pureos amber-updates InRelease' changed its 'Version' value from '9' to ''
E: Repository 'https://repo.pureos.net/pureos amber-updates InRelease' changed its 'Codename' value from 'amber-updates' to ''
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Could someone please confirm that these changes are intentional and advise on how to go about explicitly accepting them?

2

Apt update says "Repository […] changed its ‘Label’ value from ‘None’ to ‘PureOS 10.x (byzantium)’

3

My sources.list looks like this:

deb https://repo.pureos.net/pureos byzantium main
deb https://repo.pureos.net/pureos byzantium-updates main
deb https://repo.pureos.net/pureos byzantium-security main

deb https://repo.puri.sm/pureos amber main
deb https://repo.pureos.net/pureos/ amber-security main
deb https://repo.pureos.net/pureos/ amber-updates main

Can I simply delete the amber repos or will this cause problems?

4

I would start with lsb_release -c

i.e. in order to confirm which one you are using.

Can you elaborate on the release history of your phone? e.g. started on amber and then manually in-place upgraded? some other possibility?

1 Like
5

I get:

 Codename:	byzantium

No phone, it’s a Librem 13v4. I did start out with amber, then manually switched over to byzantium over a year ago. I did my last update perhaps 3 weeks ago.

6

The link provided by ASwyD2 confirms that the changes are intentional (and nothing to be concerned about).

The way to accept the changes is to run apt update (rather than apt-get update) and answer in the affirmative when prompted.

7

Sorry, my bad - although my answer would have been almost the same anyway.

It looks odd but I am not sure. At a minimum, you do regular backups, right? :wink:

1 Like
8

Turns out that while byzantium repo has been reverted to old values, amber was not. It’s fixed now.

If you’re using byzantium, you shouldn’t have any amber repos in there.

1 Like