You are not logged in.

#1 2019-07-05 08:18:46

earlybird
ほやほや
Registered: 2015-12-16
Posts: 710
Website

Workaround needed for updating new Helium installs

We asked our users to update their bunsen-keyring package before June 2019 due to our old PGP key expiring by this date. This is necessary to continue securely accessing our repositories. I overlooked however that we would also need to refresh our current install ISOs since they also contain the PGP key --- which didn't happen. This is why new installs will fail to update their packages from our repos since their key is expired. This doesn't break the installation however, please just follow the instructions below to manually download and install the updated bunsen-keyring package to work around the issue:

Execute the following sequence of commands. wget should not report any certificate errors:

cd ~
wget -O bunsen-keyring.deb https://eu.pkg.bunsenlabs.org/debian/pool/main/b/bunsen-keyring/bunsen-keyring_2019.01.19%2Bbl9-2_all.deb
sudo dpkg -i bunsen-keyring.deb
sudo apt-get update

After this, your BL installation will be able to function normally.

Offline

#2 2019-07-05 10:05:52

Hematot
Member
Registered: 2019-07-05
Posts: 5

Re: Workaround needed for updating new Helium installs

As a linux newbie (a couple of years with one Mint computer) and a completely fresh user of Bunsenlabs I immediately ran into trouble with apt update due to the problem you describe.
(The bl-welcome script that starts at first boot failed with its very first step.)
I finally solved it half way a couple of days ago following the instructions on the BL main website's page https://www.bunsenlabs.org/repositories.html which I believe is very much like your solution here.
(That is the part under the page's header "Keyring package")

However, on that page the instructions goes on and says how to download and verify a signing key (under header "Manual setup").
I can only guess that this key is for making sure that the system is downloading files from a safe place, is able to decrypt correctly and whatnot.

But after quite a few tries I have not yet managed to get it to work.
The part:

wget https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc

seems to work fine. The last piece of the response I received was: ‘BunsenLabs-RELEASE.asc’ saved [5864/5864]
I've not been so lucky with the part:

gpg --fingerprint BunsenLabs-RELEASE.asc

The reply should apparently be, or contain, a fingerprint: (3172 4784 0522 7490 BBB7 43E6 A067 3F72 FE62 D9C5), otherwise I have the wrong key.

But the respose I get is: gpg: error reading key: No public key

So I can't get any further into my BL testing, I guess that there is not much use to update/upgrade with the wrong or non-existing key.
I've tried to get the installation to work on two different computers, same result.
After reading your post I hope that this "key" problem is related to the "keyring" problem and that you might have a solution, but please let me know if I posted this in the wrong place.

Sorry that there is a lot of assuming, guessing and seeming here. That's a linux newbie for you... wink

Anway, I'm totally stuck and any help would be much appreciated.
/Hematot

Offline

#3 2019-07-05 12:22:31

Huldalumi
Member
From: Finland
Registered: 2019-05-15
Posts: 14

Re: Workaround needed for updating new Helium installs

hope this helps it worked for me
bunsunlabs web page repositories
Helium    helium    deb http://pkg.bunsenlabs.org/debian helium main    ⬛
then pick Helium and scroll down until you find

bunsen-keyringmisc
Version: 2019.01.19+bl9-2 (20/01/2019)
Description: BunsenLabs GnuPG archive key
Depends: gpgv
Recommends: gnupg
Maintainer: Jens John
Homepage: https://www.bunsenlabs.org
Source: https://eu.pkg.bunsenlabs.org/debian/po … en-keyring
Architecture    Size    SHA-1
all    11 kB    e262b5928a312ddcb5edbf5f0210e11ae41fba92

then down loaded open with gdebi and it went to the right file then i ran Bl-welcome and everything worked fine

i hope this helps i'm a noob to linux hope its clear for you


yeah,well, thats just like, your opinion man
The Dude

Offline

#4 2019-07-05 14:33:55

Hematot
Member
Registered: 2019-07-05
Posts: 5

Re: Workaround needed for updating new Helium installs

Thanks Huldalumi,
Yes that part worked for me too.
That is the "Keyring package" section of the setup according to BL's Repository page.
(https://www.bunsenlabs.org/repositories.html)
After that it was possible to do a an "apt update" without errors.

However, the next step, the "Manual setup" part in the setup instructions is to "Fetch and verify the repository’s signing key" by these two commands:

wget https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc
gpg --fingerprint BunsenLabs-RELEASE.asc

This fails for me.

The response to the first line doesn't report any errors:

--2019-07-05 12:01:24--  https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc
Resolving ddl.bunsenlabs.org (ddl.bunsenlabs.org)... 78.47.156.207, 2a01:4f8:c17:2c09::2
Connecting to ddl.bunsenlabs.org (ddl.bunsenlabs.org)|78.47.156.207|:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://kelaino.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc [following]
--2019-07-05 12:01:24--  https://kelaino.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc
Resolving kelaino.bunsenlabs.org (kelaino.bunsenlabs.org)... 78.47.156.207, 2a01:4f8:c17:2c09::2
Connecting to kelaino.bunsenlabs.org (kelaino.bunsenlabs.org)|78.47.156.207|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5864 (5.7K) [application/pgp-keys]
Saving to: ‘BunsenLabs-RELEASE.asc.2’

BunsenLabs-RELEASE 100%[==============>]   5.73K  --.-KB/s    in 0s      

2019-07-05 12:01:24 (54.7 MB/s) - ‘BunsenLabs-RELEASE.asc.2’ saved [5864/5864]

But the response to the second line is not a fingerprint as the instruction says, but instead the message

gpg: error reading key: No public key

Huldalumi, what what is your response if you execute this:

gpg --fingerprint BunsenLabs-RELEASE.asc

Last edited by Hematot (2019-07-05 14:35:38)

Offline

#5 2019-07-05 15:26:59

Huldalumi
Member
From: Finland
Registered: 2019-05-15
Posts: 14

Re: Workaround needed for updating new Helium installs

I get the same error I will get back to if I solve the problem or if you solve perhaps you could tell me
or maybe i'll wait for it to be fixed on the web page and reinstall it!

Last edited by Huldalumi (2019-07-05 15:35:46)


yeah,well, thats just like, your opinion man
The Dude

Offline

#6 2019-07-05 15:56:25

Hematot
Member
Registered: 2019-07-05
Posts: 5

Re: Workaround needed for updating new Helium installs

Hopefully OP or someone else that know how this works can help us.
Otherwise, just as you say, we'll just have to do an install from scratch when the new ISO is uploaded.

Offline

#7 2019-07-05 16:55:01

hhh
Meep!
Registered: 2015-09-17
Posts: 8,046
Website

Re: Workaround needed for updating new Helium installs

@twoion is preparing updated Helium ISOs, stay tuned.

Offline

#8 2019-07-09 18:05:02

twoion
ほやほや
Registered: 2015-08-10
Posts: 2,459

Re: Workaround needed for updating new Helium installs

Huldalumi wrote:

I get the same error I will get back to if I solve the problem or if you solve perhaps you could tell me
or maybe i'll wait for it to be fixed on the web page and reinstall it!

You're right; the method listed may have stopped working a more or less long time ago (maybe 4-5 years ago?), or if I made a mistake by writing it down it may have never worked as written.

The issue is that GPG's command line interface is impossible to figure out with extra help and the results differ across gpg versions (most notably gpg2 vs gpg1). I have amended the passage with a seemingly more portable workaround to the problem since all alternative sources I found now on the internet didn't work either.

---

To conclude this issue, we have released ISOs that have been fixed (announcement).


What can you see / On the horizon?

Offline

#9 2019-07-10 16:42:37

Hematot
Member
Registered: 2019-07-05
Posts: 5

Re: Workaround needed for updating new Helium installs

Thank you very much twoion and team,
Appreciate all your efforts!

I'll try your updated instructions and then I guess I'll do a reinstall with the new ISO just to be sure. smile

Offline

#10 2019-07-15 21:21:11

jjanderson5
Member
Registered: 2016-05-10
Posts: 65

Re: Workaround needed for updating new Helium installs

IGNORE THIS!!!

Dumb error on my part.

Jim A.

Last edited by jjanderson5 (2019-07-15 21:23:34)

Offline

#11 2019-07-16 16:46:29

Hematot
Member
Registered: 2019-07-05
Posts: 5

Re: Workaround needed for updating new Helium installs

twoion wrote:

I have amended the passage with a seemingly more portable workaround to the problem...

Feedback on your new instructions twoion:
Got the correct fingerprint after changing

gpg --homedir "$tmpdir" --import /tmp/BunsenLabs-RELEASE.asc &>/dev/null

to

gpg --homedir "$tmpdir" --import BunsenLabs-RELEASE.asc &>/dev/null

(the path to the downloaded .asc file is wrong).

The output from this command was a bit disturbing but I assume that it is because we're not looking at the "real" key.

Once again, thanks guys!

Offline

Board footer

Powered by FluxBB