Problem with apt update in debian

[binkinator]

how do you execute an executable in msys considering sudo doesn't exist for it? before it came to me that the site for apt update probably didn't exist, I was going to install devkitpro on msys to see if it showed the correct site. however, it said something about it needing to be on the root like it would if you didn't chmod or use sudo on Debian. I did chmod the file too.

Yeah, I didn’t need it. For the odd case where I might I would probably right click and run msys2 as Administrator. Everything is owned by my regular user account. So far I’ve not needed to elevate privileges while working in msys2.

 

[GlueSniffinEd]

I came across this when I updated my server to 22.04. The key management system was changed and the solution is below; worked perfectly for me.

askubuntu /questions/1398344/apt-key-deprecation-warning-when-updating-system

Sorry, it won't let me post a URL, but you should be able to decipher it from above.

Here is my example from the Mono repository after exporting the key: /etc/apt/sources.list.d/mono-official-stable.list

deb [arch=amd64 signed-by=/usr/share/keyrings/mono.gpg] <URL to the repository> stable-focal main

Darned URL lockout for newbie users such as myself.

 

[binkinator]

I came across this when I updated my server to 22.04. The key management system was changed and the solution is below; worked perfectly for me.

askubuntu /questions/1398344/apt-key-deprecation-warning-when-updating-system

Sorry, it won't let me post a URL, but you should be able to decipher it from above.

Nice!

Found it here:

https://askubuntu.com/questions/1398344/apt-key-deprecation-warning-when-updating-system

 

[godreborn]

I no longer have the key issue. it doesn't appear the url exists, because afaik, that's what this error means, so I removed it again with nano:

 

[binkinator]

I no longer have the key issue. it doesn't appear the url exists, because afaik, that's what this error means, so I removed it again with nano:

View attachment 317707

Do you have the original instructions that recommend using apt to install devkitpro products? I’ve never seen them…
(but then again I’m new to the whole devkitpro ecosystem)

 

[godreborn]

Do you have the original instructions that recommend using apt to install devkitpro products? I’ve never seen them…
(but then again I’m new to the whole devkitpro ecosystem)

no, I don't even know how it got there, plus docker doesn't seem to have a bullseye release, so I changed it to eoan. everything works correctly now.

 

[godreborn]

btw, I was able to fix the original key issue by removing the url via nano in the sources.list, then readding it.

 

[godreborn]

@binkinator , something appears to be wrong with devkitpro now, and I have no idea how to fix it:

 

[godreborn]

nm, I had to restart as something didn't reinitialize after coming back from safe mode. it was affecting all three distros I use, so it wasn't a Debian issue. all is fixed now.

 

[godreborn]

I was able to fix the key error by copying the key from ubuntu and injecting it into Debian. I had to remove that bullseye release from sources.list, considering it doesn't contain seemingly any release: