Grafana OSS Debian repo changes Origin, Label; is this intended?

Grafana Installation
1

Attempting to do an apt-update, apt is unhappy about changes in the Origin and Label in the InRelease file. Here are the error messages:

E: Repository 'https://packages.grafana.com/oss/deb stable InRelease' changed its 'Origin' value from 'grafana stable' to '. stable'
E: Repository 'https://packages.grafana.com/oss/deb stable InRelease' changed its 'Label' value from 'grafana stable' to '. stable'

This seems to have happened sometime in the last 24 hours or so (sometime on November 1 or 2). It’s an Ubuntu Bionic machine, though this looks like it ought to be a problem independent of the distribution.

Is this change on purpose? I’ve been looking for mention of it on other issues but so far haven’t found anything, and I’d rather not manually tell apt to accept the changes if this is in error.

1 Like
2

Can confirm, I saw this too.

This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.type or paste code here

More, is this expected?

3

Looks like it’s no longer a problem now (as of 20:11 UTC on November 3) – the Origin and Label have returned to their original values. I assume it was a bug that they got changed and that it’s been corrected.

2 Likes
4

Hey!

This happened because we attempted a Linux repository migration, which was ultimately reverted due to other issues. You may encounter this again starting from now.

The new repository has the same GPG key, but this change in the Origin and Label values will be permanent, you may tell apt to accept it.

2 Likes
5

Thanks for confirming, Julien.

6

For me the solution was to execute the following (Ubuntu):

sudo apt-get update --allow-releaseinfo-change

7

Hello,

i am trying to update grafana with apt on debian linux. But i always get this error with “apt upgrade”:

E: Fehlschlag beim Holen von https://apt.grafana.com/pool/main/g/grafana/grafana_9.3.6_amd64.deb 404  Not Found [IP: 146.75.122.217 443]
E: Einige Archive konnten nicht heruntergeladen werden; vielleicht »apt-get update« ausführen oder mit »--fix-missing« probieren?

Can you help me with this issue?

8

What do you have in the Grafana sources.list file as the repository URL?

Antony.

9

In /etc/apt/source.list.d the grafana.list file contains:

deb [signed-by=/usr/share/keyrings/grafana.key] https://apt.grafana.com stable main
10

All I can suggest is “try again after a while” and hope that DNS gives you a
different IP address for that hostname - it will, but I don’t know how long you
might need to wait for your local cache to fetch a new answer.

I see a 600 second timeout on it, so it’ll be a minimum of 10 minutes between
tries before you can expect to see a different address.

Antony.

11

I searched several times for a solution, and I solved it with:

sudo apt install ca-certificates
12

The issue appears to be back? I re-checked the website for the latest apt repository, got the new key, apt update, no change, apt-get update --allow-releaseinfo-change, no change, deleted the /var/lib/apt/lists/apt.grafana.com_dists_stable_InRelease file and apt update, same origin and label of . stable, manually confirmed with curl, curl https://apt.grafana.com/dists/stable/Release, so I think this issue is back?

13

As I can’t edit my original comment, I just want to ask if it is still being fixed, again curling the https://apt.grafana.com/dists/stable/Release, it still shows . stable for origin and label and it says it was updated Jun 2024 (after my original comment) so just wondering what is going on and when it will be resolved?

14

Hey @jordanplayz158again

Can you show your /etc/apt/sources.list.d/grafana.list/grafana.list and the content of /etc/apt/keyrings/grafana.gpg?

15

Here is my /etc/apt/sources.list.d/grafana.list

deb [signed-by=/etc/apt/keyrings/grafana.gpg] https://apt.grafana.com stable main

Here is my /etc/apt/keyrings/grafana.gpg
(cat /etc/apt/keyrings/grafana.gpg | gpg)

pub   rsa3072 2023-08-24 [SC] [expires: 2025-08-23]
      B53AE77BADB630A683046005963FA27710458545
uid           Grafana Labs <engineering@grafana.com>
sub   rsa3072 2023-08-24 [E] [expires: 2025-08-23]
16

I just wanted to make sure you had good things, which is the case (thanks for formatting the gpg).

Can you try to run the command sudo apt-get update --allow-releaseinfo-change=all (with the all option). If it does not work, you can also try to directly make the rep in trusted in the grafana.list file, to bypass the apt signatures check:
might be something like:

echo "deb [trusted=yes] https://packages.grafana.com/oss/deb stable main" | sudo tee /etc/apt/sources.list.d/grafana.list
sudo apt-get update

I’ve never done that myself, so you might need to adjust the command. If it does not work, I assume you can open a GitHub issue as New Bug Report (even if it’s not new) or Feature Request.

Hope that helps
Best regards

17

Yeah, no problem, I did the same thing, checked if the repo or gpg keys changed, that is also why I went the curl route straight to the source, no need to worry about apt or anything interfering, curl is grabbing the latest release file right from the apt server, no caching, etc.

apt-get update --allow-releaseinfo-change=all only true or false is allowed, will use true, no change

I appreciate the suggestion of trusted=yes but I will keep using the GPG key as if the GPG key was invalid, apt update should give an error but it doesn’t and it shouldn’t change anything so long as it is pulling the data.

Yeah, I’ll look for the packaging repo and try to see if I can find the issue in the code

Thanks.

1 Like