Librewolf repository changes, updating the template

Community Guides
1

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

instead of “sudo extrepo enable librewolf” (which fails).

Then I powered off the Librewolf template (sudo poweroff) and back in business! Updates run normally.

9 Likes
2

I’ve moved this to the Community Guides category @barto, let me know if you think that was mistaken :slightly_smiling_face:

2 Likes
3

You were 2 hours ahead :smile: I just wanted to post the same issue. Luckily, your issue and solution was already listed. Thank you :handshake:

3 Likes
4

I tried to setup a new (miminal) librewolf qube and get the following error:

https_proxy=http://127.0.0.1:8082/ http_proxy=http://127.0.0.1:8082/ extrepo enable librewolf

Could not download index YAML file:
500 Can't connect to HTTPS:80 (Temporary failure in name resolution) at /usr/share/perl5/Debian/ExtRepo/Data.pm line 27.

PS: I am using apt-cacher; also tried with http://HTTPS///

1 Like
5

At a glance I didn’t see any difference, but the following thread has a solution marked for exactly this scenario.

2 Likes
6

I was already using extrepo with Librewolf, but am also throwing an error when I update:

E:Repository ‘https://repo.librewolf.net librewolf InRelease’ changed its ‘Origin’ value from ‘Staging LibreWolf Software Repository’ to ‘LibreWolf Software Repository’, E:Repository ‘https://repo.librewolf.net librewolf InRelease’ changed its ‘Label’ value from ‘Staging LibreWolf Software Repository’ to ‘LibreWolf Software Repository’

I tried the following in the root terminal, but afterwards continue to receive the above error in Qubes Update.

https_proxy=http://127.0.0.1:8082 extrepo enable librewolf
https_proxy=http://127.0.0.1:8082 extrepo update librewolf
1 Like
7

Thanks, I will follow up the discussion in this thread since it is not related to update , instead a general issue of getting the external repo added on a new qube.

1 Like
8

don’t copy paste, there is a typo, it should http:// and not http:127…

sudo -i
https_proxy=http:127.0.0.1:8082 extrepo enable librewolf
2 Likes
9

Right! Fixed now.

1 Like
10 
E:Repository 'https://repo.librewolf.net librewolf InRelease' changed its 'Origin' value from 'LibreWolf Software Repository' to 'Staging LibreWolf Software Repository', 
E:Repository 'https://repo.librewolf.net librewolf InRelease' changed its 'Label' value from 'LibreWolf Software Repository' to 'Staging LibreWolf Software Repository'

is what the qubes updater gave me. :frowning:

1 Like
11

I get the same right now.
It may be that some Librewolf maintainer made a wrong (“after many beers”) commit.
I’ll wait till tomorrow before digging any deeper.

3 Likes
12

now it works

2 Likes
13

Security Vulnerability fixed in Firefox 131.0.2, Firefox ESR 128.3.1, Firefox ESR 115.16.1 — Mozilla oh an we should (librewolf has it ready) brb rebooting app vm :slight_smile:

1 Like
14

Indeed… just in time! :smiley:

2 Likes