Page 1 of 1
LibreWolf repo address has changed
Posted: Fri Oct 04, 2024 9:31 pm
by siamhie
Just a heads-up
I was doing my usual check for updates and kept getting GPG signature errors with LibreWolf. I disabled the repo and went about my business and decided to try later.
After I re-enabled the repo and tried again, I got the same message, so I searched The Duck for answers and came across this link from LibreWolf's web page.
The structure of our Debian repository has changed! Existing Debian users (currently possibly encountering errors) should follow our Migration Guide.
Debian Migration Guide
Followed the instructions and now I have a new repo address (last entry).
Code: Select all
inxi -r
Repos:
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://la.mxrepo.com/mx/repo/ bookworm main non-free
2: deb http://la.mxrepo.com/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
1: deb https://repo.nordvpn.com/deb/nordvpn/debian stable main
Active apt repos in: /etc/apt/sources.list.d/xanmod-release.list
1: deb [signed-by=/usr/share/keyrings/xanmod-archive-keyring.gpg] http://deb.xanmod.org releases main
Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources
1: deb [arch=amd64 arm64] https://repo.librewolf.net librewolf main
New users will encounter this message when installing LibreWolf for the first time.
librewolf_install.jpg
Re: LibreWolf repo address has changed
Posted: Fri Oct 04, 2024 10:08 pm
by dolphin_oracle
what happens if you run
a second time
Re: LibreWolf repo address has changed
Posted: Fri Oct 04, 2024 10:33 pm
by siamhie
dolphin_oracle wrote: ↑Fri Oct 04, 2024 10:08 pm
what happens if you run
a second time
Let me try that in my XFCE VM and I'll report back.
*Update: command not found
Code: Select all
siamhie@mxxfce:~
$ sudo extrepo enable librewolf
[sudo] password for siamhie:
sudo: extrepo: command not found
Re: LibreWolf repo address has changed [Solved]
Posted: Fri Oct 04, 2024 10:40 pm
by dolphin_oracle
well you have to install it.
but no matter, it exits gracefully if a repo is already configured.
pushing out updates to mx-packageinstaller-pkglist for mx21 and 23 thanks!
Re: LibreWolf repo address has changed
Posted: Fri Oct 04, 2024 10:42 pm
by towwire
I got this when I ran it again.
Code: Select all
sudo extrepo enable librewolf
[sudo] password for towwire:
Configuration enabled.
Note that configuration for this repository already existed; it was enabled, but not updated.
For updates, see the update command.towwire@mx:~
Re: LibreWolf repo address has changed
Posted: Fri Oct 04, 2024 10:43 pm
by siamhie
I even tried this command and it errors in my VM.
Code: Select all
sudo apt update && sudo apt install extrepo -y
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://deb.debian.org/debian bookworm InRelease
Hit:4 http://la.mxrepo.com/mx/repo bookworm InRelease
Get:5 https://deb.librewolf.net bookworm InRelease [16.7 kB]
Err:5 https://deb.librewolf.net bookworm InRelease
The following signatures were invalid: EXPKEYSIG D29FBD5F93C0CFC3 Malte Jürgens <maltejur@dismail.de>
Reading package lists... Done
W: GPG error: https://deb.librewolf.net bookworm InRelease: The following signatures were invalid: EXPKEYSIG D29FBD5F93C0CFC3 Malte Jürgens <maltejur@dismail.de>
E: The repository 'http://deb.librewolf.net bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
I think you still have to run this command first.
Code: Select all
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
Re: LibreWolf repo address has changed
Posted: Fri Oct 04, 2024 10:44 pm
by dolphin_oracle
yes. mostly why I asked about running the command a second time. but it all good, thanks.
Re: LibreWolf repo address has changed
Posted: Fri Oct 04, 2024 11:38 pm
by siamhie
dolphin_oracle wrote: ↑Fri Oct 04, 2024 10:44 pm
yes. mostly why I asked about running the command a second time. but it all good, thanks.
Even though LibreWolf didn't install the librewolf.list and librewolf.gpg was added to the apt folders.
I've since removed them and will wait until your update comes through and try again in the VM.
Re: LibreWolf repo address has changed
Posted: Fri Oct 04, 2024 11:59 pm
by siamhie
Thank you for that quick fix. Updated package list and LibreWolf installed with no errors.
Re: LibreWolf repo address has changed
Posted: Sat Oct 05, 2024 12:13 am
by sunrat
Thanks for the heads-up. I just followed the commands shown in the Migration Guide link, worked perfectly and took about half a minute.
Re: LibreWolf repo address has changed
Posted: Sat Oct 05, 2024 3:37 am
by 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
Re: LibreWolf repo address has changed
Posted: Sat Oct 05, 2024 3:40 am
by 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/
Re: LibreWolf repo address has changed
Posted: Wed Oct 09, 2024 2:30 pm
by mxethernut
oops pls del
Re: LibreWolf repo address has changed
Posted: Wed Oct 09, 2024 9:50 pm
by 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
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 12:38 am
by 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'.
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 12:57 am
by DukeComposed
davidy wrote: ↑Thu Oct 10, 2024 12:38 am
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.
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 7:48 am
by fehlix
siamhie wrote: ↑Wed Oct 09, 2024 9:50 pm
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:
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
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 8:15 am
by siamhie
fehlix wrote: ↑Thu Oct 10, 2024 7:48 am
siamhie wrote: ↑Wed Oct 09, 2024 9:50 pm
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:
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
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 8:32 am
by dolphin_oracle
looking at the changes they made, I think this was a mistake was made on their end, and then they corrected it.
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 8:39 am
by fehlix
siamhie wrote: ↑Thu Oct 10, 2024 8:15 am
fehlix wrote: ↑Thu Oct 10, 2024 7:48 am
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:
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.
siamhie wrote: ↑Thu Oct 10, 2024 8:15 am
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.
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 8:41 am
by siamhie
dolphin_oracle wrote: ↑Thu Oct 10, 2024 8:32 am
looking at the changes they made, I think this was a mistake was made on their end, and then they corrected it.
So forcing the update manually "sudo apt upgrade librewolf -y" has corrected it on my end?
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 8:48 am
by fehlix
siamhie wrote: ↑Thu Oct 10, 2024 8:41 am
dolphin_oracle wrote: ↑Thu Oct 10, 2024 8:32 am
looking at the changes they made, I think this was a mistake was made on their end, and then they corrected it.
So forcing the update manually "sudo apt upgrade librewolf -y" has corrected it on my end?
Not what I wrote. The release info change confirmation is within the "apt update" part.
Upgrade to newer version of the package can be done but is not related to the already confirmed release info change.
I.E if you had already latest version of librewolf no need to try to upgrade.
The info you got from their page, is probably not explaining good enough what this is about,
and may lead to misinterpretation what needs to be done.
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 9:00 am
by siamhie
fehlix wrote: ↑Thu Oct 10, 2024 8:39 am
siamhie wrote: ↑Thu Oct 10, 2024 8:15 am
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.
I don't mind that Debian bubble wraps us with security in mind.
Even the maintainer of extrepo states that "no warranty is made by the Debian project as to the security or quality of the software in these third-party repositories".
siamhie wrote: ↑Thu Oct 10, 2024 8:15 am
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.
I ran into the same issue in the VM and followed the migration steps. Today all I did was check for updates all was good.
Just seemed my fluxbox install (using the terminal) ran into this information field issue last night.
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 9:13 am
by siamhie
fehlix wrote: ↑Thu Oct 10, 2024 8:48 am
siamhie wrote: ↑Thu Oct 10, 2024 8:41 am
dolphin_oracle wrote: ↑Thu Oct 10, 2024 8:32 am
looking at the changes they made, I think this was a mistake was made on their end, and then they corrected it.
So forcing the update manually "sudo apt upgrade librewolf -y" has corrected it on my end?
Not what I wrote. The release info change confirmation is within the "apt update" part.
Upgrade to newer version of the package can be done but is not related to the already confirmed release info change.
I.E if you had already latest version of librewolf no need to try to upgrade.
The info you got from their page, is probably not explaining good enough what this is about,
and may lead to misinterpretation what needs to be done.
The first time I received that error (last night), I selected N (default) when I ran that command and LW didn't update,
so I reran that command a second time and selected Y and LW updated which is what is probably confusing me.
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 9:24 am
by fehlix
siamhie wrote: ↑Thu Oct 10, 2024 9:13 am
The first time I received that error (last night), I selected N (default) when I ran that command and LW didn't update,
so I reran that command a second time and selected Y and LW updated which is what is probably confusing me.
Yes, if you reject accepting the changes when running the command
The new release file will be ignored and no packages lists updated. Hence nothing to upgrade if there would be a newer version.
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 5:15 pm
by siamhie
fehlix wrote: ↑Thu Oct 10, 2024 9:24 am
siamhie wrote: ↑Thu Oct 10, 2024 9:13 am
The first time I received that error (last night), I selected N (default) when I ran that command and LW didn't update,
so I reran that command a second time and selected Y and LW updated which is what is probably confusing me.
Yes, if you reject accepting the changes when running the command
The new release file will be ignored and no packages lists updated. Hence nothing to upgrade if there would be a newer version.
Common sense caught me when n was capitalized and y was not. I'm just glad everything is working again.
I do have nala set to check for updates when the upgrade command is used instead.
Code: Select all
# Set to false to disable auto updating the package list
# when running the upgrade command
auto_update = true
# Set to true to make full-upgrade the default
full_upgrade = true
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 5:47 pm
by Mauser
I don't know if this is related as I noticed this error that I quickly copied this part of the error before the window closed, "The following signatures were invalid: EXPKEYSIG D29FBD5F93C0CFC3 Malte Jürgens <
maltejur@dismail.de>" but I have updated MX23.4 XFCE already before seeing this thread. Is this a concern or is this to be ignored like some signature issues in the past that mean nothing?
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 7:14 pm
by fehlix
Mauser wrote: ↑Thu Oct 10, 2024 5:47 pm
I don't know if this is related as I noticed this error that I quickly copied this part of the error before the window closed, "The following signatures were invalid: EXPKEYSIG D29FBD5F93C0CFC3 Malte Jürgens <
maltejur@dismail.de>" but I have updated MX23.4 XFCE already before seeing this thread. Is this a concern or is this to be ignored like some signature issues in the past that mean nothing?
It is related.
To fix the issue, you can reinstall librewolf from with MXPI->pop.Apps.->Browser->LibreWolf.
The updated installation routine for librewolf was added recently to MXPI in order to fix the repo-change and the expired key warning issue.
Without the re-installtion with the new repo, you would not get any update of the browser and also the warning would not go away by itself.
Re: LibreWolf repo address has changed
Posted: Thu Oct 10, 2024 8:16 pm
by Mauser
fehlix wrote: ↑Thu Oct 10, 2024 7:14 pm
Mauser wrote: ↑Thu Oct 10, 2024 5:47 pm
I don't know if this is related as I noticed this error that I quickly copied this part of the error before the window closed, "The following signatures were invalid: EXPKEYSIG D29FBD5F93C0CFC3 Malte Jürgens <
maltejur@dismail.de>" but I have updated MX23.4 XFCE already before seeing this thread. Is this a concern or is this to be ignored like some signature issues in the past that mean nothing?
It is related.
To fix the issue, you can reinstall librewolf from with MXPI->pop.Apps.->Browser->LibreWolf.
The updated installation routine for librewolf was added recently to MXPI in order to fix the repo-change and the expired key warning issue.
Without the re-installtion with the new repo, you would not get any update of the browser and also the warning would not go away by itself.
Thank you for the answer. I am glad it wasn't a complicated process.
All is good now.
