issue with BL software installer (Stretch)

Bradypus · 2017-07-16 00:17:29

After the upgrade to Stretch, I was trying to install the Libre Office suite using the installer in the menu and got the message that bunsen-meta-libreoffice was not available.

Then I went to Synaptic (sorry, guys, I'm learning slowly) and, of course, it wasn't there.
then I uncommented the following lines in my sources.list file:

deb http://pkg.bunsenlabs.org/debian bunsen-helium main
deb http://pkg.bunsenlabs.org/debian stretch-backports main

and... well, Synaptic didn't like it:

The repository 'http://pkg.bunsenlabs.org/debian bunsen-helium Release' does not have a Release file. Updating from such a repository can't be done securely, and is therefore disabled by default.See apt-secure(8) manpage for repository creation and user configuration details.The repository 'http://pkg.bunsenlabs.org/debian stretch-backports Release' does not have a Release file.

then I changed those lines to:

deb http://pkg.bunsenlabs.org/debian bunsen-hydrogen main
deb http://pkg.bunsenlabs.org/debian jessie-backports main

and installation proceeded normally, from the Stretch repos.

I think I'm going to leave it like this for now.

Will this be a big problem?

Brad Ypus

damo · 2017-07-16 08:38:51

There are no Helium repos: we are still developing. There is no "recommended" way to upgrade yet, and all the advice in the forums so far is that you do it at your own risk. You seem to have done what is known as a "Fool's Upgrade"!

Head_on_a_Stick · 2017-07-16 10:50:27

Bradypus wrote:

installation proceeded normally, from the Stretch repos.
I think I'm going to leave it like this for now.
Will this be a big problem?

No, that should be fine.

The stretch libreoffice metapackage does seem to be the correct one to install.

The old bunsen-meta-libreoffice metapackage just adds a dependency for libreoffice-gtk which has been replaced by libreoffice-systray & libreoffice-gtk2, it seems.

So you may want to also use:

sudo apt install libreoffice-{systray,gtk2}

@Team: we need to change the dependencies in the bunsen-meta-libreoffice package for Helium.

Last edited by Head_on_a_Stick (2017-07-16 11:55:44)

Bradypus · 2017-07-16 12:01:34

damo wrote:

You seem to have done what is known as a "Fool's Upgrade"!

*LOLOLOL*

Thank you, Damo!

Now, the not-so-clever (AKA stupid) things I do have an official name (and, best of all, my name is not part of it!)

I thought there might not be repos yet, but the line my sources.list was upgrade automatically to:

deb http://pkg.bunsenlabs.org/debian bunsen-helium main

which lead me to think otherwise.

Brad

Head_on_a_Stick · 2017-07-16 12:11:51

Bradypus wrote:

Synaptic didn't like it:

The repository 'http://pkg.bunsenlabs.org/debian bunsen-helium Release' does not have a Release file. Updating from such a repository can't be done securely, and is therefore disabled by default.See apt-secure(8) manpage for repository creation and user configuration details.The repository 'http://pkg.bunsenlabs.org/debian stretch-backports Release' does not have a Release file.

Did you add the key for the new repository?

My guide wrote:

Add the key:
wget -q https://kelaino.bunsenlabs.org/~johnraff/helium-dev.asc -O - | sudo apt-key add -
Then update & upgrade, the new versions should take precedence:
sudo apt update && sudo apt upgrade

That advice is in the final section of the guide:

https://forums.bunsenlabs.org/viewtopic … 382#p53382

It was only added recently so you may have missed it.

Bradypus · 2017-07-16 12:13:44

Head_on_a_Stick wrote:

Bradypus wrote:
installation proceeded normally, from the Stretch repos.
I think I'm going to leave it like this for now.
Will this be a big problem?
No, that should be fine.
The stretch libreoffice metapackage does seem to be the correct one to install.

Thank you, HoaS!

I guess I was lucky.

Head_on_a_Stick wrote:

So you may want to also use:
sudo apt install libreoffice-{systray,gtk2}

I did, and got the following message:

 ~$ libreoffice-systray is already the newest version (1:5.2.7-1).

Could that be due to using the Stretch repo while calling the Hydrogen metapackage? The rest of my sources.list is all Stretch.

Thanks again, Damo and HoaS.

(PS - please believe me, I do look up the answers for these things before asking here and I only ask the thinks I can't solve that way.)

Bradypus · 2017-07-16 12:26:14

Head_on_a_Stick wrote:

Did you add the key for the new repository?
My guide wrote:
Add the key:
wget -q https://kelaino.bunsenlabs.org/~johnraff/helium-dev.asc -O - | sudo apt-key add -
Then update & upgrade, the new versions should take precedence:
sudo apt update && sudo apt upgrade
That advice is in the final section of the guide:
https://forums.bunsenlabs.org/viewtopic … 382#p53382
It was only added recently so you may have missed it.

Yes, I did miss it.

To be fair, only saw this guide after I posted these questions. There are other posts with titles like "upgrading to Stretch" and I followed them (or what I could understand of them). In one of those, someone mentioned following "the notes" or something like that, but there was no reference to what those "notes" might be and I couldn't find them. Now I see the sticky post you mentioned and feel much more like the author of a "fool's upgrade" (*LOL*).

Thanks a bunch. I'll try adding the key for the new repo and switching my sources.list back to it.

Brad

UPDATE:

After adding the key (I just copied the line you posted and ran it, got an 'OK' output, so I think it worked), I tried sudo apt-get update and, after the update was 9mostly) successful, I got the following report:

Reading package lists... Done
W: The repository 'http://pkg.bunsenlabs.org/debian bunsen-helium Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://pkg.bunsenlabs.org/debian stretch-backports Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch http://pkg.bunsenlabs.org/debian/dists/bunsen-helium/main/binary-amd64/Packages  404  Not Found [IP: 78.47.156.207 80]
E: Failed to fetch http://eu.pkg.bunsenlabs.org/debian/dists/bunsen-helium/main/i18n/Translation-en_US  404  Not Found [IP: 78.47.156.207 80]
E: Failed to fetch http://pkg.bunsenlabs.org/debian/dists/stretch-backports/main/binary-amd64/Packages  404  Not Found [IP: 78.47.156.207 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.

So, I guess something went wrong with adding the key...

Last edited by Bradypus (2017-07-16 12:55:43)

Steve · 2017-07-16 12:31:37

Im staying on Jessie and letting the experts figure out that Stretch fella.

New stable vs old stable. Still needs a good 6 months or more to iron out the bugs. From what i read many people are still using Debian 7 with no problems, but in the interests of forging ahead into the future Bunsenlabs in my humble opinion is unique and will go from strength to to strength as will Debian.

johnraff · 2017-07-17 02:41:33

Head_on_a_Stick wrote:

@Team: we need to change the dependencies in the bunsen-meta-libreoffice package for Helium.

Noted - thank you.

johnraff · 2017-07-17 02:45:54

Bradypus wrote:

I thought there might not be repos yet, but the line my sources.list was upgrade automatically to:
deb http://pkg.bunsenlabs.org/debian bunsen-helium main

This repository does not (yet) exist. I don't know how it got into your sources.list. See the guide HoaS posted, and remove the redundant entries.

Naik · 2017-07-17 21:01:38

^^ I just recognised that too:

naik@00010-01100-10100-11000:~$ updatesrc
[...]                                                                                       
Ign:1 http://eu.pkg.bunsenlabs.org/debian bunsen-helium InRelease                                                                          
Fehl:8 http://eu.pkg.bunsenlabs.org/debian bunsen-helium Release                                    
  404  Not Found [IP: 78.47.156.207 80]
[...]
Paketlisten werden gelesen... Fertig                  
E: The repository 'http://pkg.bunsenlabs.org/debian bunsen-helium Release' does not have a Release file.
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.

switching from

deb http://pkg.bunsenlabs.org/debian bunsen-helium main

to

deb https://kelaino.bunsenlabs.org/~johnraff/debian helium main

made everything work fine for me (I added the key already)

...anyways though both (helium and and hydrogen repos) had been tested here the install option that can be found in several places along the menu is of no use to me. I had never* been able to install anything by using it.

This is not that big a problem to me but i think it breaks the overall feeling of "oh see, a minimal Linux-Distro just providing enough comfort to give you a warm feeling when being pushed onto the learning curve"

Maybe this kind of misbehavior is only shown to me since i`m tracking testing/unstable on this machine but i came to have the impression that it could be related to the BL-*-Metapackages you use.
I do not claim to know how this kind of stuff should be handled, but i can`t resist asking myself whether this is necessary or not. Wouldn`t it be more easy to just install packages from the debian repos which already reside in the default sources.list?

*=like in the last 3months or so

naik --greetz

Head_on_a_Stick · 2017-07-17 21:08:09

Naik wrote:

i think it breaks the overall feeling of "oh see, a minimal Linux-Distro just providing enough comfort to give you a warm feeling when being pushed onto the learning curve"

Any references to the Helium(-dev) repositories on these boards have had warnings attached that they are experimental in nature and should not be used generally.

I don't think my Helium-dev guide ever had that "deb http://pkg.bunsenlabs.org/debian bunsen-helium main" line, can you remember where you got it from?

damo · 2017-07-17 21:11:04

Naik wrote:

Wouldn`t it be more easy to just install packages from the debian repos which already reside in the default sources.list?

The BL repos are meant to hold packages which aren't in the Debian Stable repos (mainly bunsen-*), or ones which which have been patched or brought from elsewhere.

The Hydrogen ones are shown here: Repository index

#1 2017-07-16 00:17:29

issue with BL software installer (Stretch)

#2 2017-07-16 08:38:51

Re: issue with BL software installer (Stretch)

#3 2017-07-16 10:50:27

Re: issue with BL software installer (Stretch)

#4 2017-07-16 12:01:34

Re: issue with BL software installer (Stretch)

#5 2017-07-16 12:11:51

Re: issue with BL software installer (Stretch)

#6 2017-07-16 12:13:44

Re: issue with BL software installer (Stretch)

#7 2017-07-16 12:26:14

Re: issue with BL software installer (Stretch)

#8 2017-07-16 12:31:37

Re: issue with BL software installer (Stretch)

#9 2017-07-17 02:41:33

Re: issue with BL software installer (Stretch)

#10 2017-07-17 02:45:54

Re: issue with BL software installer (Stretch)

#11 2017-07-17 21:01:38

Re: issue with BL software installer (Stretch)

#12 2017-07-17 21:08:09

Re: issue with BL software installer (Stretch)

#13 2017-07-17 21:11:04

Re: issue with BL software installer (Stretch)

Board footer