@stgraber It appears there has been a change in the Incus Repository. I haven’t found anything about this.
Error: Repository 'https://pkgs.zabbly.com/incus/stable noble InRelease' changed its 'Origin' value from '. noble' to 'pkgs.zabbly.com'
Error: Repository 'https://pkgs.zabbly.com/incus/stable noble InRelease' changed its 'Label' value from '. noble' to 'incus-stable'
Yeah, we added some metadata, that should cause a one time prompt.
The one-time update occurred with “apt”.
I had been using nala and it did not take the update.
Ah, that probably should be reported as a bug against that tool.
Those kind of changes can happen during the lifetime of a repository. In fact Debian, I’ve seen Debian change one of its repository fields whenever a point release comes out.
In this case, the change was made so that tools like unattended-upgrade can properly detect the pkgs.zabbly.com repositories. This required adding extra metadata (the origin and label fields).
Same notification provided in Discover in KDE Plasma 5.27.5 running on Bookworm.
I still get it EVERY time I update! Running Debian with kde.
Did you run apt update from the command line or are you using some other tool?
If not apt, then run a manual apt update. It’s a one time prompt but some package managers don’t seem to know to handle it.
Running apt update fixed it. Seems to be a discover bug!
Yeah, I’m being quite specific when saying apt update, apt-get update is an older codebase and doesn’t quite handle that correctly, at least not on all releases.
For what it’s worth, this change revealed an issue with Debian’s unattended upgrades for me, as it didn’t notify me that pkgs.zabbly.com apt updates have been failing since this change. I just happened to notice the error when running on the same machine manually.
Thanks for bringing this one up… I’ve been seeing this too and couldn’t figure out what was causing it. But like you, I use nala not apt.