Fix for: Update Manager "fails" because of Librewolf

[tkn]

If you have Librewolf installed there is a chance that around this time the Update Manager will "fail" to update Librewolf.

Using sudo apt update from the commandline gives more information:

If you encounter this:

E: Repository 'https://repo.librewolf.net librewolf InRelease' changed its 'Origin' value from 'LibreWolf Software Repository' to 'Staging LibreWolf Software Repository'
N: Repository 'https://repo.librewolf.net librewolf InRelease' changed its 'Suite' value from 'LibreWolf Software Repository' to 'Staging LibreWolf Software Repository'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N]

Press 'y' to accept these changes.
Usually the 'staging' repository is a bit more experimental than the 'stable' repository but I guess the people behind Librewolf had their reasons.

Now you can update as usual again.

(The same happened in Debian Trixie, see: #2075 - Debian Trixie with extrepo: Repository 'https://repo.librewolf.net librewolf InRelease' changed its 'Origin' value from 'LibreWolf Software Repository' to 'Staging LibreWolf Software Repository' - librewolf/issues - Codeberg.org )

In case you have a totally different error, like update warnings because librewolf gpg key expiration, read this:

Update warnings because librewolf gpg key expired

If you just updated and you got an error like Err:2 https://deb.librewolf.net jammy InRelease The following signatures were invalid: EXPKEYSIG D29FBD5F93C0CFC3 Malte Jürgens [email protected] [...] W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.librewolf.net jammy InRelease: The following signatures were invalid: EXPKEYSIG D29FBD5F93C0CFC3 Malte Jürgens ma…

[tkn]

It happend again today but the other way around.
Apply the same solution af before to accept the changes.

The reason for this change to 'staging' and back is, according to the devs, this:

This was unfortunately a server side misconfiguration for a short amount of time. Everything should work as expected now again. But for anyone still experiencing this, it is "safe" to accept this label change. From my research, you can do so by running:

sudo apt-get --allow-releaseinfo-change update

In other words: The first repochange was an accident, so they changed it back now.