BunsenLabs Lithium ARM edition...

bard · 2019-12-23 13:39:17

Hi all,

New thread for a new project. Title says it all. Love BL so try to install it on all my machines...

I have 3 RPis (One RPi 1 256 Mb RAM - Tor Relay when it's not broken..., One RPi 3B - Media Center and One RPi4 4 Gb RAM).

I've been trying to install BL on RPi4. Succeeded with a Raspbian Buster Lite install with few more utilities (Openbox, Synaptics, LAMP, Guake,...).
For some reason, the experimental repo didn't work (probably because of the ARM arch), so I had to download each package (arch-all) according to the repository list, tried to install each package by itself (dpkg -i), had to solve missing dependencies most of the time but overall installed fine (only exception was maybe meta package since it has intel and some other microcode issues, so had to force install it).
Then looked for arch-specific packages (armhf) in Debian and BL repos (or googled it).

Rebooted, logged in, startx for GUI and voilà!
I am in the process of tweaking things a little (Tint2, Conky, ob-menu-generator,...) but overall works great.
Even installed my bluetooth headset and it works fine (no A2DP sink yet but no big deal).

A small issue I have (but it may be my fault...) is that Wifi connections are not managed by nm-applet ("device not ready"...) but Wifi works fine (set in Raspi-config). If I plug or unplug an Ethernet cable, nm-applet sees it fine... Still investigating this one.

Just my experience, so thought I would share and maybe help make BL-Arm a more popular "standard"... ;-)
Still have to test a Samsung Q35 and a 2006 Macbook (both running Helium for now) but this will be discussed in another thread.

hhh · 2019-12-24 04:30:31

Mod note, recommending this thread to continue discussion on the subject because the original thread is from 2015.

I can't comment on ARM, I don't have the hardware. @johnraff is mostly away-from-keyboard for at a least 2 weeks, but I'm not sure if he has ARM hardware either. @twoion should be able to shed some light re: ARM he sees this thread.

bard · 2019-12-26 14:40:13

Hi hhh,

No pb for me. Looks like not too many people tried it yet.
I can test anything and report if needed.
Let's wait and see.

gennargiu · 2019-12-27 14:36:36

Hi Bard can you create a testing image bl lithium arm for raspberry pi 4 ? Best regards and happy holidays from Naples italy. smile

gennaro

twoion · 2019-12-27 17:03:35

@bard the experimental repos are built by John and only have amd64 and/or i386 packages. This is not indicative of what the final repo setup will look like and support.

It is no problem to support ARM architectures for official lithium packages as long as there is a current Docker Debian image available for the architecture (our new build flow will be container-based and no longer use pbuilder because it is broken on Buster for ARM crosscompilation) (additionally, our 2 binary packages, tint2 and jgmenu, must compile on these architectures for full support -- if they don't, then it'll be possible to use the architecture-independent BL packages regardless as long as the architecture is enabled for the repository to generate the correct index files).

armhf (arm32v7, if I read this correctly) is something we had partial support for in the past; it should be possible to support it in the future as well. The pi4 seems to require Debian arm64 (arm64v8), there is an image on Dockerhub so I can look into enabling this architecture for the final release.

https://wiki.debian.org/RaspberryPi claims that raspbian actually builds 1 image for all Pis and that it is only running an armel (fixed-point 32bit) kernel -- what is the debian architecture running on top of that kernel? always armel? What Debian architecture do you need to support current-gen Pis? Just do dpkg --print-architecture && dpkg --print-foreign-architectures on the Pi.

(None of us devs have a Pi or other ARM device as far as I know, so it is unlikely that we can get into this topic 'deeply'. Our main concern are the i386/amd64 Debian architectures.)

dumetrulo · 2020-02-07 08:05:19

I would very much like BunsenLabs for ARM, I have a Pinebook Pro which would be very suitable.

My thoughts for installing it for now were as follows: use the unofficial Debian installer you can find in the Pine64 forums to install a minimal Bullseye, then add the BL packages to it. Do you think that should work?

ohnonot · 2020-02-07 19:53:25

Which binary packages are in the BL repositories? tint2, jgmenu - that should be about it, no?
So, install Debian for ARM, then add bunsen repos. Compile those 2 packages yourself...?
I have compiled tint2 on a Pinebook, btw. It was easy-peasy.

xgpt · 2020-02-19 15:10:34

I'd love to help test this, I've got various SBCs, rpi-zero, pi-3B, a few pi-4's, and an orangepi PC (not PC+, not PC2, PC)

they all run raspbian or armbian, which are pretty much just debian with small numbers of tweaks to make them work on these things. making a list of binary packages in the repos would help me immensely in testing for y'all. also a meta-package to install in a single step. something like bunsen-meta-desktop or whatever that calls in everything in the repos

damo · 2020-02-19 15:37:43

@xgpt

bunsen-meta-all - Metapackage for the full BunsenLabs install

bunsen-meta-all/debian/control

jimjamz · 2020-12-27 23:09:54

I've tried to continue this on, following on from the two topics:
https://forums.bunsenlabs.org/viewtopic.php?id=6352
https://forums.bunsenlabs.org/viewtopic.php?id=6222

I installed a fresh version of RaspiOS Lite to the Pi's SD card.
I have added the repo to /etc/apt/sources.list, which now looks like:

deb http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpi
deb http://pkg.bunsenlabs.org/debian lithium main

Following on from https://www.bunsenlabs.org/repositories.html :
I downloaded and installed the keyring package.
//Should I verify the signing key has been added with `gpg -k`?
I have added the key and updated APT.

I then proceed to install `bunsen-meta-all`. I have tried this including and excluding the argument `--no-install-recommends`, but I still get the same result:

Reading package lists...
Building dependency tree...
Reading state information...
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: amd64-microcode but it is not installable
                   Depends: firmware-b43-installer but it is not going to be installed
                   Depends: firmware-b43legacy-installer but it is not going to be installed
                   Depends: i965-va-driver but it is not installable
                   Depends: intel-microcode but it is not installable
                   Depends: unrar but it is not installable
                   Depends: xserver-xorg-video-intel but it is not installable

It looks like it's trying to install the other architectures as well, but why? Isn't this also preventing the repositories from being installed correctly?

Last edited by jimjamz (2020-12-27 23:11:18)

rbh · 2020-12-28 00:52:28

jimjamz wrote:

I downloaded and installed the keyring package.
//Should I verify the signing key has been added with `gpg -k`?

Never wrong to verify things.. But if you want to list your apt-keys, the command is:

$ apt-key list

The following packages have unmet dependencies:
bunsen-meta-all : Depends: amd64-microcode but it is not installable
Depends: firmware-b43-installer but it is not going to be installed
Depends: firmware-b43legacy-installer but it is not going to be installed
Depends: i965-va-driver but it is not installable
Depends: intel-microcode but it is not installable
Depends: unrar but it is not installable
Depends: xserver-xorg-video-intel but it is not installable

I presume that my 32-bits installation also have amd64-microcode installed. That should not do any harm, but is essential on an 64-bit machine.

On page https://www.bunsenlabs.org/repositories.html, you have a list of repositories needed. You must add repos for Debian, as your raspbian.raspberrypi.org, does not carry all needed packages. I would reconmend you to also add repo for security.

## DEBIAN 10 buster
deb http://httpredir.debian.org/ buster main contrib non-free
deb http://httpredir.debian.org/debian/ buster-backports main contrib non-free
deb http://httpredir.debian.org/debian/ buster-updates main contrib non-free
deb http://httpredir.debian.org/debian/ buster-proposed-updates main contrib non-free

# Debian Security buster
deb http://security.debian.org/debian-security/ buster/updates main contrib non-free

You can omit buster-backports and buster-proposed-updates.

Last edited by rbh (2020-12-28 00:59:22)

jimjamz · 2020-12-28 14:20:04

Of course, makes sense that the BL packages would depend on Debian's repos.

I've downloaded Debian's signing keys required for the Debian repo entries @rbh has recommended in his sources.list

However, the buster entry is having some issues:

Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Ign:3 http://deb.debian.org buster InRelease
Hit:5 https://deb.debian.org/debian buster-updates InRelease
Hit:6 https://deb.debian.org/debian-security buster/updates InRelease
Err:7 http://deb.debian.org buster Release
  404  Not Found [IP: 151.101.18.132 80]
Hit:4 http://eu.pkg.bunsenlabs.org/debian lithium InRelease
Err:8 https://security.debian.org/debian-security buster/updates InRelease
  Could not connect to security.debian.org:443 (151.101.64.204). - connect (111: Connection refused) Could not connect to security.debian.org:443 (151.101.128.204). - connect (111: Connection refused) Could not connect to security.debian.org:443 (151.101.0.204). - connect (111: Connection refused) Could not connect to security.debian.org:443 (151.101.192.204). - connect (111: Connection refused) Could not connect to security.debian.org:443 (2a04:4e42:600::204), connection timed out Could not connect to security.debian.org:443 (2a04:4e42:400::204), connection timed out Could not connect to security.debian.org:443 (2a04:4e42:200::204), connection timed out Could not connect to security.debian.org:443 (2a04:4e42:c00::204), connection timed out Could not connect to security.debian.org:443 (2a04:4e42::204), connection timed out Could not connect to security.debian.org:443 (2a04:4e42:a00::204), connection timed out Could not connect to security.debian.org:443 (2a04:4e42:e00::204), connection timed out Could not connect to security.debian.org:443 (2a04:4e42:800::204), connection timed out
Reading package lists...
E: The repository 'http://deb.debian.org buster Release' does not have a Release file.

I've also read that this might be a bad idea by mixing both Debian's and Raspbian's packages due to the difference in architecture.

For anyone who has already attempted this, what issues did you have by doing this and how did you mitigate them?
FYI, I'm also using a first-gen RPi to test this as @dogwood did.

rbh · 2020-12-28 18:09:06

jimjamz wrote:

the Debian repo entries @rbh has recommended in his sources.list

No, it is not my sources.list. I mirror debian, BL and some other repos to my server and my sources list feteches from my server.

However, the buster entry is having some issues:
Ign:3 http://deb.debian.org buster InRelease

I wrote,

deb http://httpredir.debian.org/ buster main contrib non-free
deb http://httpredir.debian.org/debian/ buster-backports main contrib non-free

I rewrote the adresses, as I just could not copy my own sourses.list. I dropped "debian" on first row. it should be:

deb http://httpredir.debian.org/debian buster main contrib non-free

Hit:4 http://eu.pkg.bunsenlabs.org/debian lithium InRelease

and that should be on https:

Err:8 https://security.debian.org/debian-security buster/updates InRelease
Could not connect to security.debian.org:443 (151.101.64.204). - connect

But that must be http://.

Sorry for the confusion i created.

I've also read that this might be a bad idea by mixing both Debian's and Raspbian's packages due to the difference in architecture.

I have never worked with RasperyPi, only installed Rasperry for x86.
When fetching packages, you should only fetch packages for your arch, or "arch-less" packages. But, you can add arch-directive before each line in sources:

deb [ arch=armhf ] http://[...]

Last edited by rbh (2020-12-28 18:10:36)

johnraff · 2020-12-29 02:22:26

rbh wrote:

When fetching packages, you should only fetch packages for your arch, or "arch-less" packages. But, you can add arch-directive before each line in sources:
deb [ arch=armhf ] http://[...]

Apt usually takes care of the architecture automatically, though.

cog · 2020-12-29 03:14:25

Hey guys, I got Lithium running on the rapsberry pi 4-b 8GB model pretty good a few months ago.

https://forums.bunsenlabs.org/viewtopic … 15#p108115

I used this as a base image:

https://downloads.raspberrypi.org/raspi … 64/images/

I installed the bunsen-keyring then bunsen-meta-all (this is the only thing I had to rebuild because it depended on 4 packages that were not resolvable that were either amd64 or intel based.

Then I basically rebuilt bunsen-meta-all without 4 packages using pbuilder and installed from a local directory/repo, probably some more could go (firmware related) but it doesn't really matter at this point.

the only things I changed in the source package were debian/control & debian/changelog

here you go for reference

debian/control

Source: bunsen-meta-all
Section: metapackages
Priority: optional
Maintainer: John Crawley <john@bunsenlabs.org>
Build-Depends: debhelper (>= 10)
Standards-Version: 4.3.0
Homepage: https://github.com/BunsenLabs/bunsen-meta-all
Vcs-Git: https://github.com/BunsenLabs/bunsen-meta-all.git
Vcs-Browser: https://github.com/BunsenLabs/bunsen-meta-all

Package: bunsen-meta-all
Architecture: all
Description: Metapackage for the full BunsenLabs install
 This metapackage will install all the packages needed
 for a full BunsenLabs system.
Depends: ${misc:Depends},
 alsa-utils,
 anacron,
 apt-transport-https,
 apt-xapian-index,
 aptitude,
 arandr,
 arj,
 at,
 at-spi2-core,
 bash-completion,
 btrfs-progs,
 catfish,
 chntpw,
 clipit,
 compton,
 conky-all,
 cpufrequtils,
 cryptsetup,
 curl,
 crda,
 dbus-x11,
 dmz-cursor-theme,
 dosfstools,
 efibootmgr,
 eject,
 enchant,
 evince,
 f2fs-tools,
 fbxkb,
 feh,
 file-roller,
 filezilla,
 firefox-esr,
 firmware-b43-installer,
 firmware-b43legacy-installer,
 firmware-linux,
 firmware-realtek,
 firmware-iwlwifi,
 fonts-cantarell,
 fonts-noto,
 fonts-noto-cjk,
 fonts-noto-mono,
 fonts-inconsolata,
 fonts-liberation,
 ftp,
 fuse,
 galculator,
 galternatives,
 gddrescue,
 gdebi,
 geany,
 ghostscript,
 gigolo,
 gmrun,
 gnome-keyring,
 gnome-themes-standard,
 gparted,
 gsimplecal,
 gstreamer1.0-libav,
 gstreamer1.0-plugins-bad,
 gstreamer1.0-plugins-base,
 gstreamer1.0-plugins-good,
 gstreamer1.0-plugins-ugly,
 gstreamer1.0-pulseaudio,
 gtk2-engines-pixbuf,
 gvfs,
 gvfs-backends,
 gvfs-fuse,
 hardinfo,
 haveged,
 hdparm,
 hddtemp,
 hexchat,
 hfsprogs,
 htop,
 hwdata,
 inotify-tools,
 inxi,
 jgmenu,
 lame,
 less,
 libblockdev-crypto2,
 libexo-1-0,
 libinput-tools,
 libpam-gnome-keyring,
 libreoffice-calc,
 libreoffice-gtk2,
 libreoffice-writer,
 libnotify-bin,
 libqt5svg5,
 lightdm,
 lightdm-gtk-greeter,
 lightdm-gtk-greeter-settings,
 light-locker,
 lm-sensors,
 locales,
 lsb-release,
 lshw,
 lvm2,
 lxappearance,
 lxterminal,
 lzop,
 mlocate,
 modemmanager,
 network-manager,
 network-manager-gnome,
 nitrogen,
 ntfs-3g,
 ntp,
 obconf,
 openbox,
 openssh-client,
 p7zip-full,
 papirus-icon-theme,
 pavucontrol,
 pciutils,
 pcmciautils,
 pnmixer,
 policykit-1,
 policykit-1-gnome,
 pulseaudio,
 python,
 python-keybinder,
 python-notify,
 python-xdg,
 qt5-style-plugins,
 rfkill,
 ristretto,
 rpl,
 rsync,
 rzip,
 scrot,
 smartmontools,
 suckless-tools,
 sudo,
 synaptic,
 thunar,
 thunar-archive-plugin,
 thunar-gtkhash,
 thunar-media-tags-plugin,
 thunar-volman,
 tint2,
 transmission-gtk,
 tumbler,
 unace,
 unalz,
 unar,
 unrar,
 unzip,
 update-inetd,
 usb-modeswitch,
 usbutils,
 user-setup,
 uuid-runtime,
 va-driver-all,
 vdpau-va-driver,
 vlc,
 vlc-plugin-notify,
 wireless-tools,
 xbindkeys,
 xcape,
 xdg-user-dirs,
 xdg-utils,
 xfburn,
 xfce4-notifyd,
 xfce4-power-manager,
 xfce4-screenshooter,
 xfsprogs,
 xinput,
 xorg,
 xserver-xorg-input-all,
 xserver-xorg-input-synaptics,
 xserver-xorg-input-evdev,
 xserver-xorg-input-wacom,
 xserver-xorg-video-all,
 xserver-xorg-video-qxl,
 xsel,
 xz-utils,
 yad,
 zip,
 bunsen-common,
 bunsen-configs,
 bunsen-configs-pulse,
 bunsen-conky,
 bunsen-docs,
 bunsen-exit,
 bunsen-fortune,
 bunsen-images,
 bunsen-keyring,
 bunsen-os-release,
 bunsen-papirus-icon-theme,
 bunsen-pipemenus,
 bunsen-themes,
 bunsen-thunar,
 bunsen-utilities,
 bunsen-welcome

Package: bunsen-meta-lite
Architecture: all
Description: Metapackage for a reduced BunsenLabs install
 This metapackage will install a selection of the packages needed
 for a BunsenLabs system, making some lighter substitutions.
Depends: ${misc:Depends},
 alsa-utils,
 amd64-microcode,
 anacron,
 apt-transport-https,
 arandr,
 arj,
 at,
 at-spi2-core,
 bash-completion,
 btrfs-progs,
 chntpw,
 clipit,
 conky-all,
 cpufrequtils,
 cryptsetup,
 curl,
 crda,
 dbus-x11,
 dillo,
 dmz-cursor-theme,
 dosfstools,
 efibootmgr,
 eject,
 evince,
 f2fs-tools,
 fbxkb,
 feh,
 file-roller,
 firmware-b43-installer,
 firmware-b43legacy-installer,
 firmware-linux,
 firmware-realtek,
 firmware-iwlwifi,
 fonts-inconsolata,
 fonts-liberation,
 fuse,
 galculator,
 galternatives,
 gddrescue,
 gdebi,
 gigolo,
 gmrun,
 gnome-keyring,
 gparted,
 gsimplecal,
 gtk2-engines-pixbuf,
 gvfs,
 gvfs-backends,
 gvfs-fuse,
 hardinfo,
 haveged,
 hdparm,
 hddtemp,
 hfsprogs,
 htop,
 hwdata,
 i965-va-driver,
 intel-microcode,
 inxi,
 jgmenu,
 less,
 libexo-1-0,
 libinput-tools,
 libpam-gnome-keyring,
 libnotify-bin,
 libqt5svg5,
 lightdm,
 lightdm-gtk-greeter,
 lightdm-gtk-greeter-settings,
 light-locker,
 lm-sensors,
 locales,
 lsb-release,
 lshw,
 lvm2,
 lxappearance,
 mlocate,
 modemmanager,
 mousepad,
 mpv,
 network-manager,
 network-manager-gnome,
 nitrogen,
 ntfs-3g,
 ntp,
 obconf,
 openbox,
 openssh-client,
 p7zip-full,
 pavucontrol,
 pciutils,
 pcmciautils,
 pnmixer,
 policykit-1,
 policykit-1-gnome,
 pulseaudio,
 python,
 python-keybinder,
 python-notify,
 python-xdg,
 qt5-style-plugins,
 rfkill,
 ristretto,
 rsync,
 rxvt-unicode,
 rzip,
 scrot,
 smartmontools,
 suckless-tools,
 sudo,
 synaptic,
 thunar,
 thunar-archive-plugin,
 thunar-gtkhash,
 thunar-volman,
 tint2,
 transmission-gtk,
 unace,
 unalz,
 unar,
 unrar,
 unzip,
 update-inetd,
 usb-modeswitch,
 usbutils,
 user-setup,
 uuid-runtime,
 va-driver-all,
 vdpau-va-driver,
 wireless-tools,
 xbindkeys,
 xcape,
 xdg-user-dirs,
 xdg-utils,
 xfburn,
 xfce4-notifyd,
 xfce4-power-manager,
 xfsprogs,
 xinput,
 xorg,
 xserver-xorg-input-all,
 xserver-xorg-input-synaptics,
 xserver-xorg-input-evdev,
 xserver-xorg-input-wacom,
 xserver-xorg-video-all,
 xserver-xorg-video-intel,
 xserver-xorg-video-qxl,
 xsel,
 xz-utils,
 yad,
 zip,
 bunsen-common,
 bunsen-configs-lite,
 bunsen-configs-pulse,
 bunsen-conky,
 bunsen-docs,
 bunsen-exit,
 bunsen-fortune,
 bunsen-images,
 bunsen-keyring,
 bunsen-os-release,
 bunsen-paper-icon-theme,
 bunsen-pipemenus,
 bunsen-themes,
 bunsen-thunar,
 bunsen-utilities,
 bunsen-welcome

debian/changelog

bunsen-meta-all (10.1-1.1) lithium; urgency=medium

  * Non-maintainer upload.
  * Backported to the Raspberry Pi 4-B. 

 -- Will Elliott <will@mattie>  Mon, 09 Nov 2020 00:18:31 -0700

bunsen-meta-all (10.1-1) lithium; urgency=medium

  * Add bunsen-meta-lite with slightly fewer and lighter packages.

 -- John Crawley <john@bunsenlabs.org>  Wed, 15 Jul 2020 15:57:58 +0900

bunsen-meta-all (10.0.1-7) lithium; urgency=medium

  * Replace mirage with ristretto.
  * Add at, gnome-themes-standard and thunar-gtkhash.

 -- John Crawley <john@bunsenlabs.org>  Sat, 16 May 2020 14:12:25 +0900

bunsen-meta-all (10.0.1-6) lithium; urgency=medium

  * Add gddrescue. Remove xbindkeys-config.

 -- John Crawley <john@bunsenlabs.org>  Fri, 08 Nov 2019 17:11:54 +0900

bunsen-meta-all (10.0.1-5) lithium; urgency=medium

  * Add inxi, lshw and lxterminal. Remove terminator.

 -- John Crawley <john@bunsenlabs.org>  Tue, 06 Aug 2019 17:16:11 +0900

bunsen-meta-all (10.0.1-4) lithium; urgency=medium

  * Add jgmenu, xbindkeys and associated packages.

 -- John Crawley <john@bunsenlabs.org>  Thu, 11 Jul 2019 16:11:17 +0900

bunsen-meta-all (10.0.1-3) lithium; urgency=medium

  * Restore held packages.
  * Replace paper icons with papirus.
  * Replace gnumeric with libreoffice-calc.
  * Add lightdm gtk settings GUI app.

 -- John Crawley <john@bunsenlabs.org>  Fri, 31 May 2019 17:10:16 +0900

bunsen-meta-all (10.0.1-2~heldpkgs2) lithium; urgency=medium

  * Restore bunsen-keyring.

 -- John Crawley <john@bunsenlabs.org>  Wed, 30 Jan 2019 18:26:32 +0900

bunsen-meta-all (10.0.1-2~heldpkgs1) lithium; urgency=medium

  * Provisionally add haveged to cover entropy issue.

 -- John Crawley <john@bunsenlabs.org>  Wed, 16 Jan 2019 11:08:44 +0900

bunsen-meta-all (10.0.1-1~heldpkgs1) lithium; urgency=medium

  * Remove e2fsprogs (essential package already present).

 -- John Crawley <john@bunsenlabs.org>  Tue, 08 Jan 2019 10:37:14 +0900

bunsen-meta-all (10.0-1~test1) lithium; urgency=medium

  * Migrate to Lithium repository.
  * Upgrade standards version to 4.3.0, debhelper compat to 10.
  * Update copyright year.
  * Temporarily remove some packages:
     bunsen-keyring
     bunsen-os-release
     gigolo*
     firmware-b43* 

 -- John Crawley <john@bunsenlabs.org>  Mon, 07 Jan 2019 18:43:06 +0900

bunsen-meta-all (9.0.1-8) helium; urgency=medium

  * Add less.

 -- John Crawley <john@bunsenlabs.org>  Tue, 24 Apr 2018 14:38:49 +0900

bunsen-meta-all (9.0.1-7) helium; urgency=medium

  * Write to /etc/bunsen/bunsen_install on install or remove.

 -- John Crawley <john@bunsenlabs.org>  Mon, 16 Apr 2018 16:41:53 +0900

bunsen-meta-all (9.0.1-6) helium; urgency=medium

  * Add fonts-noto-cjk, fonts-liberation.

 -- John Crawley <john@bunsenlabs.org>  Tue, 03 Apr 2018 16:13:34 +0900

bunsen-meta-all (9.0.1-5) helium; urgency=medium

  * Add xcape to dependencies.

 -- John Crawley <john@bunsenlabs.org>  Sun, 11 Feb 2018 13:18:16 +0900

bunsen-meta-all (9.0.1-4) helium; urgency=medium

  * Restore obmenu.

 -- John Crawley <john@bunsenlabs.org>  Sun, 10 Dec 2017 15:09:26 +0900

bunsen-meta-all (9.0.1-3) helium; urgency=medium

  * Add bunsen-paper-icon-theme.

 -- John Crawley <john@bunsenlabs.org>  Sat, 25 Nov 2017 12:42:58 +0900

bunsen-meta-all (9.0.1-2) helium; urgency=medium

  * Replace volumeicon-alsa with pnmixer.

 -- John Crawley <john@bunsenlabs.org>  Fri, 24 Nov 2017 17:33:46 +0900

bunsen-meta-all (9.0.1-1) helium; urgency=medium

  * Change Recommends to Depends
     ( APT::Never-MarkAuto-Sections:: is honoured in apt 1.0.10)
  * Update package list.
  * Update README.

 -- John Crawley <john@bunsenlabs.org>  Wed, 22 Nov 2017 15:57:45 +0900

bunsen-meta-all (9.0-3) helium; urgency=medium

  * Add xserver-xorg-input-synaptics to recommends.

 -- John Crawley <john@bunsenlabs.org>  Wed, 21 Jun 2017 16:24:20 +0900

bunsen-meta-all (9.0-2) helium; urgency=high

  * Add xserver-xorg-video-intel to recommends.

 -- John Crawley <john@bunsenlabs.org>  Mon, 12 Jun 2017 14:39:17 +0900

bunsen-meta-all (9.0-1) helium; urgency=medium

  * debian/control: Adjust recommends for helium.

 -- John Crawley <john@bunsenlabs.org>  Thu, 11 May 2017 17:17:17 +0900

bunsen-meta-all (8.0-5) bunsen-hydrogen; urgency=medium

  * debian/control: Remove gstreamer0.10 plugins from recommends.

 -- John Crawley <john@bunsenlabs.org>  Sun, 20 Aug 2017 13:37:03 +0900

bunsen-meta-all (8.0-4) bunsen-hydrogen; urgency=medium

  * debian/control: Add libreoffice-gtk and hardinfo to recommends.

 -- John Crawley <john@bunsenlabs.org>  Mon, 27 Mar 2017 16:12:41 +0900

bunsen-meta-all (8.0-3) bunsen-hydrogen; urgency=medium

  * debian/control: Adjust recommends to requirements of Deuterium point release.

 -- John Crawley <john@bunsenlabs.org>  Thu, 09 Feb 2017 12:29:13 +0900

bunsen-meta-all (8.0-2) bunsen-hydrogen; urgency=high

  * debian/control: Add bunsen-keyring to recommends.

 -- John Crawley <john@bunsenlabs.org>  Thu, 11 Aug 2016 14:31:53 +0900

bunsen-meta-all (8.0-1) bunsen-hydrogen; urgency=low

  * Initial release

 -- John Crawley <john@bunsenlabs.org>  Sun, 08 May 2016 15:02:53 +0900

cog · 2020-12-29 03:42:14

If you want a pure-er debian/lithium experience Id use these for the base install but you won’t get all the optimizations from the raspberry pi foundation.

https://raspi.debian.net/tested-images/

cog · 2020-12-29 03:56:12

I still got the machine in the closet if y’all need anything else. Let me know. I just don’t have bandwidth in the mountains so can’t download a lot.

grubernd · 2020-12-30 15:20:05

I hope I will have the time to do more testing with BL on the RPi4 .. mainly because the GUI-version of RaspiOS is a Kindergarten toy with so many bugs and inconsistencies I don't even know where to start. Quite embarrassing for a company that is selling their hardware in the million units.

Anyway .. I have a somehow running BL Li using the netinstall. With some apps in the menu, but not installed (e.g. arandr) and other weird effects.

My usage for BL Li on the RPi4 will be mainly with several 4k TVs, so some working HiDPI theme might be required, too.

As the instructions how cog got his system running are incomprehensible to me, my question is:

Should I try to debug the netinstall or the bunsen-meta-all package into a shape that JustWorks™ on ARM64?

johnraff · 2020-12-31 01:20:26

^The netinstall script gives you more scope for tweaking.

jimjamz · 2021-01-01 14:27:07

Firstly, Happy New Year to all!

rbh wrote:

I rewrote the adresses, as I just could not copy my own sourses.list. I dropped "debian" on first row. it should be:
deb http://httpredir.debian.org/debian buster main contrib non-free

D'oh! I should have seen that, as it was fairly obvious. I'd spent a while staring at the source addresses, and by that time I had gone repository-blind! smile Thanks for updating.

rbh wrote:

and that should be on https:

Thanks, I've updated the eu.pkg.bunsenlabs.org entry to HTTPS.

rbh wrote:

jimjamz wrote:
Err:8 https://security.debian.org/debian-security buster/updates InRelease
Could not connect to security.debian.org:443 (151.101.64.204). - connect
But that must be http://.

Sorry, I'm going a little bit off-topic here, but I did notice for Debian Security repositories, there are two different URLs (presumably resolving to the same address), yet strangely, only one will accept HTTPS (deb.debian.org/debian-security) and the other will not (security.debian.org/debian-security). Is the former the more preferable to use over the latter? Does it matter?

rbh wrote:

Sorry for the confusion i created..

No worries at all. I appreciate the help. I can relate to the confusion. After minutes of updating my sources.list, I start to go repo-blind.

johnraff wrote:

Apt usually takes care of the architecture automatically, though.

How does Apt know? Do you think it inspects the response of:

dpkg --print-architecture

cog wrote:

I used this as a base image:
https://downloads.raspberrypi.org/raspi … 64/images/

Why arm64? This image is not officially supported by The Raspberry Foundation just yet and is not maintained (last update: 2020-08-24), unlike armhf.
I'd prefer to have it working with armhf first, then once I'm familiar with the build and install process, I can look at applying that process to arm64 once TRF start to support it later in 2021.
Right now, I'm testing this on a first-gen RPi Model B so arm64 is a moot point.

cog wrote:

Then I basically rebuilt bunsen-meta-all without 4 packages using pbuilder and installed from a local directory/repo, probably some more could go (firmware related) but it doesn't really matter at this point.
the only things I changed in the source package were debian/control & debian/changelog

Thanks for the info. Being unfamiliar (i.e. a complete noob) with the build process, please would you care to share reproduction steps on how you did this?
What are the 4 packages omitted from your build?
Perhaps you have a link to another BL post that outlines the steps in the build process using pbuilder?

johnraff · 2021-01-02 05:05:29

jimjamz wrote:

johnraff wrote:
Apt usually takes care of the architecture automatically, though.
How does Apt know? Do you think it inspects the response of:
dpkg --print-architecture

Could be - I haven't delved into apt's source code. But the important thing is that it does know the architecture of the system it's installing packages for.

jimjamz · 2021-01-03 21:10:17

cog wrote:

Then I basically rebuilt bunsen-meta-all without 4 packages using pbuilder and installed from a local directory/repo, probably some more could go (firmware related) but it doesn't really matter at this point.

After running:

sudo apt install bunsen-meta-all

I noticed that the 4 packages that are not installable are:

amd64-microcode
i965-va-driver
intel-microcode
xserver-xorg-video-intel

@cog - I now understand that your debian/control omits these 4 packages also.
However, I have no idea how to proceed. I have no knowledge of pbuilder or how to use it to re-build debian/control. I am assuming that you have built and hosted this somewhere separately (on your local machine), but does this mean you will have to update your /etc/apt/sources.list to point to a local directory, so that when you install bunsen-meta-all, it will install the dependencies from your local debian/control? But how to do this?

@damo @johnraff - perhaps it would be useful to have a `bunsen-meta-raspi` package in the repositories that omits the above packages ARM installations wouldn't require?
Alternatively, please provide some steps on how I can create my own. I'm willing to put in the time for this and document everything so that we can extend our support and documentation to supporting Pi and other ARM device installations.

EDIT: A quick scan of this would indicate that I need to obtain the source for the bunsenlabs packages. Would I achieve this by adding the following to /etc/apt/sources.list ?:

deb-src https://deb.debian.org/debian-security/ buster/updates main contrib non-free

Then getting the source for bunsen-meta-all ?:

sudo apt source bunsen-meta-all

Am I on the correct path? Even so, I still don't yet know how to proceed.

Last edited by jimjamz (2021-01-03 21:20:00)

rbh · 2021-01-03 22:17:26

jimjamz wrote:

EDIT: A quick scan of this would indicate that I need to obtain the source for the bunsenlabs packages. Would I achieve this by adding the following to /etc/apt/sources.list ?:
deb-src https://deb.debian.org/debian-security/ buster/updates main contrib non-free
Then getting the source for bunsen-meta-all ?:
sudo apt source bunsen-meta-all
Am I on the correct path?

If you want to download packages or source for Bunsenlabs, you must add Bunsenlab repo:

deb-src https://pkg.bunsenlabs.org/debian/ lithium main

But, I think beter would be to fork the repo on github: https://github.com/BunsenLabs

Even so, I still don't yet know how to proceed.

Yes, some trheshold there is... I have recently paid a years subsciption to Apress and downloaded two books about Git. Hope to get sone time to dive into it. I also fell perpelexed...

johnraff · 2021-01-04 02:00:43

jimjamz wrote:

perhaps it would be useful to have a `bunsen-meta-raspi` package in the repositories that omits the above packages ARM installations wouldn't require?
Alternatively, please provide some steps on how I can create my own...
...Am I on the correct path?

Of course learning about how Debian packages are built is very valuable, also a grasp of git will always be useful.

But if your immediate goal is to install the full set of BunsenLabs packages on an arm system there's no need to make a custom metapackage. The bunsen-meta-* packages are just for convenience, but if you have a list of packages you want to install, you can just give it directly to apt. You have already been over the package list, so you could either write a very long command line:

sudo apt install thispackage thatpackage yetanotherpackage...

or maybe, more neatly, put the package list in a file, one package name on each line (or just space-separated):

somepackage
someotherpackage
...

and give it to apt like this

sudo apt install $( < path/to/packagelist )

jimjamz · 2021-01-10 16:25:17

rbh wrote:

If you want to download packages or source for Bunsenlabs, you must add Bunsenlab repo:
deb-src https://pkg.bunsenlabs.org/debian/ lithium main

D'oh! I didn't realise until I read your reply that, in my previous post, I had incorrectly pasted the wrong `deb-src` URL, pasting debian-security instead of the `lithium` one. Sorry for the confusion.

johnraff wrote:

You have already been over the package list, so you could either write a very long command line:
sudo apt install thispackage thatpackage yetanotherpackage...

Yes, that is what I was afraid of being suggested. Indeed, it was what I was trying to avoid.

or maybe, more neatly, put the package list in a file, one package name on each line (or just space-separated):
somepackage
someotherpackage
...
and give it to apt like this
sudo apt install $( < path/to/packagelist )

I did not know you could do that! As a software engineer, Git knowledge is not an issue, but unfortunately, my knowledge of Debian's package management and building my own distribution remains a weakness; something I am eager to improve.

I will give this a try (hopefully next week) and report back.

Last edited by jimjamz (2021-01-10 16:26:11)

#1 2019-12-23 13:39:17

BunsenLabs Lithium ARM edition...

#2 2019-12-24 04:30:31

Re: BunsenLabs Lithium ARM edition...

#3 2019-12-26 14:40:13

Re: BunsenLabs Lithium ARM edition...

#4 2019-12-27 14:36:36

Re: BunsenLabs Lithium ARM edition...

#5 2019-12-27 17:03:35

Re: BunsenLabs Lithium ARM edition...

#6 2020-02-07 08:05:19

Re: BunsenLabs Lithium ARM edition...

#7 2020-02-07 19:53:25

Re: BunsenLabs Lithium ARM edition...

#8 2020-02-19 15:10:34

Re: BunsenLabs Lithium ARM edition...

#9 2020-02-19 15:37:43

Re: BunsenLabs Lithium ARM edition...

#10 2020-12-27 23:09:54

Re: BunsenLabs Lithium ARM edition...

#11 2020-12-28 00:52:28

Re: BunsenLabs Lithium ARM edition...

#12 2020-12-28 14:20:04

Re: BunsenLabs Lithium ARM edition...

#13 2020-12-28 18:09:06

Re: BunsenLabs Lithium ARM edition...

#14 2020-12-29 02:22:26

Re: BunsenLabs Lithium ARM edition...

#15 2020-12-29 03:14:25

Re: BunsenLabs Lithium ARM edition...

#16 2020-12-29 03:42:14

Re: BunsenLabs Lithium ARM edition...

#17 2020-12-29 03:56:12

Re: BunsenLabs Lithium ARM edition...

#18 2020-12-30 15:20:05

Re: BunsenLabs Lithium ARM edition...

#19 2020-12-31 01:20:26

Re: BunsenLabs Lithium ARM edition...

#20 2021-01-01 14:27:07

Re: BunsenLabs Lithium ARM edition...

#21 2021-01-02 05:05:29

Re: BunsenLabs Lithium ARM edition...

#22 2021-01-03 21:10:17

Re: BunsenLabs Lithium ARM edition...

#23 2021-01-03 22:17:26

Re: BunsenLabs Lithium ARM edition...

#24 2021-01-04 02:00:43

Re: BunsenLabs Lithium ARM edition...

#25 2021-01-10 16:25:17

Re: BunsenLabs Lithium ARM edition...

Board footer