LibreWolf repo address has changed [Solved]

[mxethernut]

Hm I think this affects anyone with the wolf installed.
What exactly must we do?

Code: Select all

sudo apt update
Hit:1 http://deb.debian.org/debian bookworm-updates InRelease
Hit:2 http://security.debian.org/debian-security bookworm-security InRelease              
Hit:4 http://deb.debian.org/debian bookworm InRelease                                     
Hit:5 http://deb.debian.org/debian bookworm-backports InRelease                           
Hit:6 https://mirror.23m.com/mx-packages/mx/repo bookworm InRelease                       
Hit:7 https://download.onlyoffice.com/repo/debian squeeze InRelease 
Hit:8 https://brave-browser-apt-release.s3.brave.com stable InRelease
Hit:3 https://deb.librewolf.net bookworm InRelease  
Err:3 https://deb.librewolf.net bookworm InRelease
  The following signatures were invalid: EXPKEYSIG D29FBD5F93C0CFC3 Malte Jürgens <maltejur@dismail.de>
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://brave-browser-apt-release.s3.brave.com stable InRelease' doesn't support architecture 'i386'
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 bookworm InRelease: The following signatures were invalid: EXPKEYSIG D29FBD5F93C0CFC3 Malte Jürgens <maltejur@dismail.de>
W: Failed to fetch http://deb.librewolf.net/dists/bookworm/InRelease  The following signatures were invalid: EXPKEYSIG D29FBD5F93C0CFC3 Malte Jürgens <maltejur@dismail.de>
W: Some index files failed to download. They have been ignored, or old ones used instead.

Btw I got this for Brave Browser sinc e day1:

Code: Select all

N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://brave-browser-apt-release.s3.brave.com stable InRelease' doesn't support architecture 'i386'

A little nuance but seeing this everytime is kind of spammy. Is it because this is telling me about its 32-bit version?
Can I get rid of the message w/o uninstalling Brave?

Edit: Editing

Code: Select all

kwrite /etc/apt/sources.list.d/brave-browser-release.list

with

Code: Select all

deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main

as suggested here in last post works fine :) viewtopic.php?p=780811#p780811

[mxethernut]

Hm ok I see we need to follow this
(first line looks scary, don't get the slash wrong or add --no-preserve-root)

1. Remove the old repository from your PC

sudo rm -f \
/etc/apt/sources.list.d/librewolf.sources \
/etc/apt/keyrings/librewolf.gpg \
/etc/apt/preferences.d/librewolf.pref \
/etc/apt/sources.list.d/librewolf.list \
/etc/apt/trusted.gpg.d/librewolf.gpg

2. Add the new repository to your PC

sudo apt update && sudo apt install extrepo -y

sudo extrepo enable librewolf

3. Update LibreWolf (optional)

sudo apt update && sudo apt upgrade librewolf -y

from here https://librewolf.net/debian-migration/

[mxethernut]

oops pls del

[siamhie]

LibreWolf's repo is at it again. When I was checking for updates, LW showed an error.

Code: Select all

╔═[siamhie@flux23]═[18:28  09/10/24]═════════════════════════════════════════[~]
╚═> doas nala upgrade
No Change: http://security.debian.org/debian-security bookworm-security 
InRelease
No Change: http://deb.debian.org/debian bookworm-updates InRelease
No Change: http://deb.debian.org/debian bookworm InRelease
No Change: http://deb.xanmod.org releases InRelease
No Change: http://la.mxrepo.com/mx/repo bookworm InRelease
No Change: https://repo.nordvpn.com/deb/nordvpn/debian stable InRelease
Updated:   https://repo.librewolf.net librewolf InRelease [17 KB]
Fetched 0 Bytes in 0s (0 bytes/s)                                               
Error: Repository 'https://repo.librewolf.net librewolf InRelease' changed its 'Label' value from 'Staging LibreWolf Software Repository' to 'LibreWolf Software Repository'
Error: Repository 'https://repo.librewolf.net librewolf InRelease' changed its 'Origin' value from 'Staging LibreWolf Software Repository' to 'LibreWolf Software Repository'
All packages are up to date.

I went back to the Debian migration page and reran this command.

Code: Select all

sudo apt update && sudo apt upgrade librewolf -y

It will ask if you want to accept the changes (default N), answer y.
It will then proceed to download the newest version (131.0.2-1) and install it.

Code: Select all

╔═[siamhie@flux23]═[18:35  09/10/24]═════════════════════════════════════════[~]
╚═> sudo apt update && sudo apt upgrade librewolf -y
Hit:1 http://deb.debian.org/debian bookworm-updates InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease                          
Hit:3 http://security.debian.org/debian-security bookworm-security InRelease   
Hit:4 http://la.mxrepo.com/mx/repo bookworm InRelease                          
Hit:5 http://deb.xanmod.org releases InRelease                                 
Hit:6 https://repo.nordvpn.com/deb/nordvpn/debian stable InRelease             
Get:7 https://repo.librewolf.net librewolf InRelease [16.9 kB]
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'
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] y
Get:8 https://repo.librewolf.net librewolf/main arm64 Packages [5,644 B]
Get:9 https://repo.librewolf.net librewolf/main amd64 Packages [5,644 B]
Fetched 11.3 kB in 6s (1,980 B/s)     
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  librewolf
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 79.3 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://repo.librewolf.net librewolf/main amd64 librewolf amd64 131.0.2-1 [79.3 MB]
Fetched 79.3 MB in 4s (22.5 MB/s)    
(Reading database ... 355518 files and directories currently installed.)
Preparing to unpack .../librewolf_131.0.2-1_amd64.deb ...
Unpacking librewolf (131.0.2-1) over (131.0-1) ...
Setting up librewolf (131.0.2-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Please wait, creating menu file - stored in /home/siamhie/.fluxbox/submenus/full_menu ...
Menu file created and ready to be used

[davidy]

I just ran 'am -u' in the app manager github ap and it updated librewolf's appimage from 130.x to 131.x. i will say of all the FF derivatives librewolf does feel to be the very best of any of them if for the simple reason is takes the least amount of time to 'make it yours'.

[DukeComposed]

I just ran 'am -u' in the app manager github ap and it updated librewolf's appimage from 130.x to 131.x. i will say of all the FF derivatives librewolf does feel to be the very best of any of them if for the simple reason is takes the least amount of time to 'make it yours'.

Yes, I've been recently told that LibreWolf is a superior browser that is a holy, blameless creature that is divine in every aspect. Those who criticize or disparage the almighty LibreWolf in any way are stupid, idiotic, and implicitly enslaved to Mozilla in mind and wallet alike.

[fehlix]

LibreWolf's repo is at it again. When I was checking for updates, LW showed an error.

Code: Select all

╔═[siamhie@flux23]═[18:28  09/10/24]═════════════════════════════════════════[~]
╚═> doas nala upgrade
Error: Repository 'https://repo.librewolf.net librewolf InRelease' changed its 'Label' value from 'Staging LibreWolf Software Repository' to 'LibreWolf Software Repository'
Error: Repository 'https://repo.librewolf.net librewolf InRelease' changed its 'Origin' value from 'Staging LibreWolf Software Repository' to 'LibreWolf Software Repository'

Yes, that's happens not often but can happen, when repo's do change release info.
Due the apt-secure's default restrictions a manual confirmation would required
to accept the changes, e.g with:

Code: Select all

sudo apt update

No need to reinstall the package itself,
Instead of manually confirmation, updating package list with option to accept the release info
change would be enough:
With apt or apt-get:

Code: Select all

sudo apt update --allow-releaseinfo-change

or with nala

Code: Select all

sudo nala update -o Acquire::AllowReleaseInfoChange=true

[siamhie]

LibreWolf's repo is at it again. When I was checking for updates, LW showed an error.

Code: Select all

╔═[siamhie@flux23]═[18:28  09/10/24]═════════════════════════════════════════[~]
╚═> doas nala upgrade
Error: Repository 'https://repo.librewolf.net librewolf InRelease' changed its 'Label' value from 'Staging LibreWolf Software Repository' to 'LibreWolf Software Repository'
Error: Repository 'https://repo.librewolf.net librewolf InRelease' changed its 'Origin' value from 'Staging LibreWolf Software Repository' to 'LibreWolf Software Repository'

Yes, that's happens not often but can happen, when repo's do change release info.
Due the apt-secure's default restrictions a manual confirmation would required
to accept the changes, e.g with:

Code: Select all

sudo apt update

No need to reinstall the package itself,
Instead of manually confirmation, updating package list with option to accept the release info
change would be enough:
With apt or apt-get:

Code: Select all

sudo apt update --allow-releaseinfo-change

or with nala

Code: Select all

sudo nala update -o Acquire::AllowReleaseInfoChange=true

How is one to know to do that when using the terminal? Maybe LW should have pointed that out on their installation/debian-migration page of the change.

By the way, I just ran my updates on MX-23.4 XFCE VM and had no problems. It's still set to use MX Updater.

lw.jpg

[dolphin_oracle]

looking at the changes they made, I think this was a mistake was made on their end, and then they corrected it.

[fehlix]

Yes, that's happens not often but can happen, when repo's do change release info.
Due the apt-secure's default restrictions a manual confirmation would required
to accept the changes, e.g with:

Code: Select all

sudo apt update

No need to reinstall the package itself,
Instead of manually confirmation, updating package list with option to accept the release info
change would be enough:
With apt or apt-get:

Code: Select all

sudo apt update --allow-releaseinfo-change

or with nala

Code: Select all

sudo nala update -o Acquire::AllowReleaseInfoChange=true

How is one to know to do that when using the terminal? Maybe LW should have pointed that out on their installation/debian-migration page of the change.

I guess, after they changed repo, someone spotted they also needed to adjust the fields Origin and Label within the release file.
Anyone of those early birds who upgrade during that time from changing repo to adjusting/changing the repo-info fields,
had release info field which now changed.
And right, there is no good way to know in advanced.
OTOH, apt-secure is sometime to secure or better over-secure.
B/c the main security is provided by the gpg-repo keys, release-info change confirmation
does not realy add much security to the whole game.
So one could set Acquire::AllowReleaseInfoChange=true within apt- preferences
to accept always release-info change, with the rational
that release-info is signed by the GPG-key and get verified.
Which make the confirmation by the user not really needed, b/c no added security.

By the way, I just ran my updates on MX-23.4 XFCE VM and had no problems. It's still set to use MX Updater.
lw.jpg

You probably changed repo after the releasinfo changed was done on the server already, so nothing to confirm.