Ubuntu apt update generates warning messages

A new warning message started today when trying to update syncthing:

Warning: Skipping acquire of configured file ‘release/binary-amd64/Packages’ as repository ‘https://apt.syncthing.net syncthing InRelease’ doesn’t have the component ‘release’ (component misspelt in sources.list?)

followed by 8 more warnings for all packages… i386, i18n,… but same warning.

I’m guessing you set this up a good long while ago? We used to have a “release” channel, but we renamed it to “stable” in 2017. Replace release with stable in your APT sources.list and you should be better off.

3 Likes

True. That did the trick. Thanks!

3 Likes

Just came here to say the same thing - thanks for the explanation and solution.

FWIW: this only recently broke (today for me), but I suspect it will start hitting various people who have followed external guides for apt setups, like How to Install Syncthing on Ubuntu 22.04 | Atlantic.Net which is generally a better approach than the official https://apt.syncthing.net documentation, which suggests using deprecated apt functionality.

Please do file an update on apt-web/site/index.html at main · syncthing/apt-web · GitHub for whatever the deprecated stuff is. :pray: This seems to change every couple of years.

The guide you linked to seems to be based on how things were a decade ago (using --dearmor on the text format key instead of the .gpg version that exists, release instead of stable), probably lightly updated along the way.

1 Like

fair point - will file something

From my knowledge, it’s the other way around: The guide you linked uses deprecated keyrings, while apt.s.n provides current best practice on how to manage signing keys.

1 Like

Ah, my apologies in that case, I may well have conflated the error logs I was seeing this morning. I’ll try a clean install later and confirm what combination I was seeing

1 Like