-
What Grafana version and what operating system are you using?
v10.4.3 on Debian bookworm (stable), and soon v11.0.0 also on Debian bookworm (stable). -
What are you trying to achieve?
Get unattended-upgrades working reliably for Grafana -
How are you trying to achieve it?
Using the Release distribution meta-data e.g. https://apt.grafana.com/dist/stable/Release -
What happened?
apt-cache policy
shows the meta-data in the Grafana repo Release haso=.
alsol=.
andn=stable
- confirmed by checking the Release file content. -
What did you expect to happen?
I would have expected the meta-data to be something like:o=Grafana
- Origin: Grafanan=bookworm
- Codename: bookworml=Grafana-Labs
- Label: Grafana-Labs
The MySQL community has a good example at: https://repo.mysql.com/apt/debian/dists/bookworm/Release
- Did you follow any online instructions? If so, what is the URL?
I note that current instructions have switched the repo source from https://packages.grafana.com/oss/deb
to https://apt.grafana.com
- so I have done this, and the same meta is in the Release file.
Debian carefully distinguished between Suite: stable and Codename: bookworm - later this year, stable will be switched to trixie which will have a different toolchain etc.
This is really an FYI - I can get unattended-upgrade
working, but I don’t know where to report the unconfigured meta for the Grafana apt repo.