On 2022-05-22 at 11:42, Amn wrote: > When I 'ap-get update' I get this message: > > "*E: *The repository > 'http://ppa.launchpad.net/pipewire-debian/pipewire-upstream/ubuntu > kinetic Release' does not have a Release file" > > I checked " /etc/apt/sources.list ", but the above link is not there. Is there anything in the directory '/etc/apt/sources.list.d'? Per my understanding, any files in that directory will be read as if their contents were part of /etc/apt/sources.list itself. It's entirely possible that a third-party package may install a file there pointing to a repository where the packagers expect to publish updates to that package. If you've installed one or more packages which does this, then that repository wound up getting taken down or misconfigured, you could see this behavior. > The same happens with : "W: An error occurred during the signature > verification. The repository is not updated and the previous index files > will be used. GPG error: https://packages.microsoft.com/repos/edge > stable InRelease: The following signatures couldn't be verified because > the public key is not available: NO_PUBKEY EB3E94ADBE1229CF" after > installing MS-Edge. For this, you'd need to either remove the repository that was added for updating Edge, or obtain the public key for that repository and configure your system to recognize it (offhand I don't remember how to do that latter, but I think it involves special syntax in the /etc/apt/sources.list* file). -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature