A couple of stumbling blocks to installing Beryllium on Bullseye

shadowfirebird · 2022-12-10 14:20:26

Of course I had to do this the hard way, rather than installing the Beryllium Release Candidate. But here I am trying to add Beryllium to the repository of a vanilla Debian 11 (Bullseye) install.

A couple of problems I have navigated around. Might be useful to someone -- alternatively, if I missed a better way of solving them, I would love to know.

First problem: having created an /etc/apt/sources.list.d/bunsen.list, I couldn't update because the key was not signed. And I couldn't install the key because I couldn't update.

I couldn't find a separate copy of the keyring for Beryllium except in Github, where it wasn't a .deb -- and `apt-key add` didn't work for me.

There is probably a much simpler way around this but I solved it by changing the line in bunsen.list to read like this:

deb [trusted=true] https://pkg.bunsenlabs.org/debian beryllium main

then I could `apt-update` and `apt install bunsen-keyring`. Once I had done that I could remove `[trusted=true]'

Second problem: trying to install package `bunsen-meta-all`.

root@agatha:/etc/apt/sources.list.d# apt-get install --no-install-recommends bunsen-meta-all
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 bunsen-meta-all : Depends: bunsen-themes but it is not installable
E: Unable to correct problems, you have held broken packages.

This seems like a bug -- apparently bunsen-themes is missing -- but Beryllium IS something that's not been released yet, so I can hardly complain?

EDIT: I initially put something here before about how switching to aptitude meant it all installed anyway, but my love affair with aptitude lasted all of five minutes. It said it worked. It installed nothing more than vanilla Openbox

So: go with with what you know. I opened synaptic and installed all the packages with "bunsen" in their name except for: bunsen-configs-lite, bunsen-meta-all, bunsen-meta-lite, bunsen-meta-packaging and bunsen-meta-lamp.

That worked, and I even appear to have got the themes? I just rebooted and picked "bunsen labs" as the window manager.

So that's it. It's all very nice. Well done, folks.

If anyone has better solutions, feel free to tell me about them?

Last edited by shadowfirebird (2022-12-10 15:03:19)

rbh · 2022-12-10 15:15:39

shadowfirebird wrote:

First problem: having created an /etc/apt/sources.list.d/bunsen.list, I couldn't update because the key was not signed. And I couldn't install the key because I couldn't update.

Well, I would say that you import a apt-key or install package *key-ring.
On page https://www.bunsenlabs.org/repositories.html, under heading "Repo signing key", it says:

1. Select and download the latest bunsen-keyring package for your distribution.
2. Install the package:
sudo dpkg -i /path/to/the/downloaded/package
sudo apt-get update

Link, to search for latest keyring: https://www.bunsenlabs.org/repoidx.html … en-keyring.
You can also download the key to as /etc/apt/trusted.gpg.d/bunsen-keyring.gpg

deb [trusted=true] https://pkg.bunsenlabs.org/debian beryllium main
then I could `apt-update` and `apt install bunsen-keyring`. Once I had done that I could remove `[trusted=true]'

You can also on the comandline give the command to trust and install bunsen-keyring.

This seems like a bug -- apparently bunsen-themes is missing -- but Beryllium IS something that's not been released yet, so I can hardly complain?

Reporting a bug ain't complaning! Thanks for that find.

shadowfirebird · 2022-12-13 18:36:06

This link: https://www.bunsenlabs.org/repoidx.html … en-keyring
does not link to the keyrings as a deb file you can install with dpkg. Or if it does, I can't work out where. It does, if you click in the right place, take you to the relevant github repo. But you can't install that with dpkg.

Thanks for the encouragement -- I was posting here to try to be of help in the release, a bit...

rbh · 2022-12-13 19:05:35

shadowfirebird wrote:

This link: https://www.bunsenlabs.org/repoidx.html … en-keyring
does not link to the keyrings as a deb file you can install with dpkg.

It is a link to search debfiles in Bunsenlabs repo, searching for "bunsen-keyring"
Edit:
~~But something has happend to the api. Sorry for that.~~

To the right of the text "Download", under the text "Architecture", you have the text "all". that is the link to the deb.

Here is direkt link:
Beryllium keyring:
https://pkg.bunsenlabs.org/debian/pool/ … -1_all.deb

Lithium keyring:
https://pkg.bunsenlabs.org/debian/pool/ … -1_all.deb

shadowfirebird · 2022-12-13 20:30:40

You're right. I would never have guessed that the word "all" was a hyperlink!

#1 2022-12-10 14:20:26

A couple of stumbling blocks to installing Beryllium on Bullseye

#2 2022-12-10 15:15:39

Re: A couple of stumbling blocks to installing Beryllium on Bullseye

#3 2022-12-13 18:36:06

Re: A couple of stumbling blocks to installing Beryllium on Bullseye

#4 2022-12-13 19:05:35

Re: A couple of stumbling blocks to installing Beryllium on Bullseye

#5 2022-12-13 20:30:40

Re: A couple of stumbling blocks to installing Beryllium on Bullseye

Board footer