I noticed today that an attempt to update my Librewolf Debian-based template ends up throwing GPG signature errors and aborting the update process altogether.
The reason is this: https://librewolf.net/debian-migration/, in short Librewolf has transitioned to use the "extrepo" Debian construct:
The extrepo tool is used to manage external repositories in Debian. Before extrepo, users who wished to use software not packaged for Debian had to manually write the apt configuration files, run an unsigned script as root, or install an unsigned .deb package that contained all the configuration on their system. None of these methods were very secure.
Extrepo remedies this by way of a metadata repository for external package repositories. The user can search the list of metadata repositories by way of "extrepo search", and manage them through "extrepo enable", "extrepo disable", or "extrepo update".
(from here)
This change is actually making the creation and maintenance of a librewolf template even easier than before.
To update, I started:
qvm-console-dispvm --autostart <Librewolf_Template>
performed the cleanup steps (only librewolf.sources was present for me, plus a .gpg key in another folder than the ones listed).
To switch to the extrepo repository, "extrepo" has to be to be told about the need to use a proxy by running:
sudo -i
https_proxy=http://127.0.0.1:8082 extrepo enable librewolf
Then I powered off the Librewolf template (sudo poweroff) and back in business! Updates run normally.