If I grok this correctly, you should be using deb822 sources. This would make sense, given the mention of sources.list.d. I’d probably adapt your legacy sources list for the ubuntu.sources there. Architecture: amd64 should solve it.
I will add: this does seem like a separate, but related topic from the initial one. You might want to:
report on the results of the original topic and mark the solution to close it if appropriate
@wxl I get what you mean about a separate issue. However, this current issue is an extension of the initial issue. I am going to submit this as a bug. The is the first since Ubuntu 4.10 I am personally dealing with an issue such as this. Placing the variable [arch=amd64] does work until I run the next update && upgrade line command.
I will update after I receive a reply from the Ubuntu Bug site.
I think maybe what I said didn’t make sense. Ubuntu is now using a different format of apt sources. That variable you’re using is for the old format. I haven’t really tested what it’s like to try to make old formats work with the new system, but I can imagine it’s got quirks like this. Just adapt to the new format as I suggested and I suspect the problem will go away.
The error message is the result of 24.04.01 can not validate the GPG signature for the listed repository because the repository does not have the correct public key.
The warning is none gone. What I going to do is wait a couple of days to update and upgrade to see if the error reappears. Back in the day I remember experience these types of issues with Ubuntu Server but not for Ubuntu Desktop
I’ll point out there that there’s some suggestion that the upgrader should take care of this for you. Why that didn’t happen is another question. That might be worth a bug report.
@wxl this all began when I accidentally clicked to upgrade the distro from 22.04.X to 24.04.1 and it has been nightmarish since. Interesting enough, I did write I was going to wait for a couple of days to update && upgrade. I issue the command earlier and since yesterday there are no issues.
What I see is repository files were once stored in /etc/apt/sources.list and since the distro upgrade it is now /etc/apt/sources.list.d. all the files now end with .d. I will review the suggested url.
This is the case however many vendor apps are not aware of the new apt-sources locations. Would one experience the same issues had a fresh installation occurred?
@wxl this is the very first time I experienced an issue like this since Ubuntu 4.10. I am clear in understanding how the cloud and now AI has forced many changes for us all globally if one elects to use community (free) open-source apps, desktop and server operating systems. I am going to monitor this issue for a few more days. Today I learned what AFAIK means.
None of this has to do with the cloud or AI. What it has to do is a very recent change to the format of the sources. That is why you never experienced it before.