You are not logged in.

#1 2015-10-07 23:29:55

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

Upgrade #! Waldorf to Debian jessie Pt. 1

I have a copy of the Waldorf 32 bit ISO and decided to see about upgrading it to jessie. This is the first part which involves changing your sources to jessie and dist-upgrading. I did a fresh install of #! and exited the Welcome script (cb-welcome), your mileage may vary and use at your own risk.

Please read Section 4.1.1, recording the Upgrade session...
https://www.debian.org/releases/stable/ … rd-session

And the whole chapter...
https://www.debian.org/releases/stable/ … ng.en.html

Make sure your wheezy system is up to date...

sudo apt-get update && sudo apt-get upgrade

Open /etc/apt/sources.list as root and comment out or delete the CrunchBang entries...

## CRUNCHBANG
## Compatible with Debian Wheezy, but use at your own risk.
#deb http://packages.crunchbang.org/waldorf waldorf main
#deb-src http://packages.crunchbang.org/waldorf waldorf main

In the same file, change "wheezy" to "jessie"...

## DEBIAN
deb http://http.debian.net/debian jessie main contrib non-free
#deb-src http://http.debian.net/debian jessie main contrib non-free

## DEBIAN SECURITY
deb http://security.debian.org/ jessie/updates main
#deb-src http://security.debian.org/ jessie/updates main

Also as root, remove or rename the file /etc/apt/preferences.

Update, ignore any signing key warnings...

sudo apt-get update

The following packages will give us problems, let's remove them for now...

sudo apt-get purge tint2 tint2conf xscreensaver compton-git && sudo apt-get -f install

This will remove cb-pipemenus, cb-lock and cb-welcome. We'll replace them with the BL equivalents later in Pt. 2: Install and Configure BunsenLabs.

Run an upgrade, this will take a while. Run the command again to make sure everything is upgraded...

sudo apt-get upgrade && sudo apt-get -f install
sudo apt-get upgrade && sudo apt-get -f install

Apt reported the package xserver-xorg-input-all as being held back, I reinstalled it...

sudo apt-get install --reinstall xserver-xorg-input-all

We're ready to dist-upgrade. You can do this by running...

sudo apt-get dist-upgrade

However, I like to err on the side of caution and switch to Init 3 first. Logout of your session, press Ctl+Alt+F1, login and switch to su...

sudo su

Then switch to Init 3, dist-upgrade and reboot (this will also take a while). Rerun the dist-upgrade to make sure everything is upgraded...

init 3
apt-get dist-upgrade && apt-get -f install
apt-get dist-upgrade && apt-get -f install

We need to clean out some cruft...

apt-get --purge autoremove

This will remove some packages you may want (bluez, udisks). This is where recording the session comes in. Otherwise, write these packages down by hand just in case. Finally...

reboot

The grub entry for #! will now read as Debian GNU/Linux and the background will be different. Boot into it and cross your fingers. With any luck you'll see the login window with a new theme and the jessie Lines wallpaper. Login. You won't have a panel or compositing yet, don't worry.

Install tint2...

sudo apt-get install tint2

Enable the BunsenLabs bunsen-hydrogen and jessie-backports repositories as described here...
http://pkg.bunsenlabs.org/#repositories

sudo apt-get update

Install compton, obmenu and xfce4-power-manager from our backports...

sudo apt-get install -t jessie-backports compton obmenu xfce4-power-manager-data

Install bunsen-os-release, bunsen-pipemenus and bunsen-themes and icons...

sudo apt-get install bunsen-os-release bunsen-pipemenus bunsen-faenza-icon-theme bunsen-themes

Run update-grub...

sudo update-grub

Edit ~/.config/openbox/autostart to match the following...

## GNOME PolicyKit and Keyring
eval $(gnome-keyring-daemon -s --components=pkcs11,secrets,ssh,gpg) &
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
## Set root window colour
#hsetroot -solid "#2E3436" &

## Group start:
## 1. nitrogen - restores wallpaper
## 2. compositor - start
## 3. sleep - give compositor time to start
## 4. tint2 panel

nitrogen --restore &
compton -Cc &
(sleep 2 && tint2) &

Edit ~/.config/openbox/menu.xml, replacing all instances of cb- with bl- except for cb-lock and cb-exit (use Ctrl-f to open a search box and Ctrl+g to advance to the next instance). The cb-x-www-browser-pipemenu entry needs some love so let's comment it out for now (the line is around #180-ish)...

	<!-- <menu execute="bl-x-www-browser-pipemenu" id="wwwbrowsers" label="WWW Browsers"/> -->

Set your themes to Bunsen and your icons to Faenza-Dark-Bunsen.

Reboot, your grub entry should now read BunsenLabs GNU/Linux. You should have a working desktop running jessie and a mix of #! and BL packages.

It will probably take a while before I can create Pt. 2 of this, how to bring the rest of the system in line with Hydrogen, so please posts your steps, ideas and problems here till then (@BL team, this means you!)

Offline

#2 2015-10-07 23:46:24

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

Re: Upgrade #! Waldorf to Debian jessie Pt. 1

Offline

#3 2015-10-08 03:28:46

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

Re: Upgrade #! Waldorf to Debian jessie Pt. 1

My fonts on webpages like yahoo.com looked terrible, editing .fonts.conf to contain the following and logging out fixed it...

<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
 <match target="font">
  <edit mode="assign" name="hinting" >
   <bool>true</bool>
  </edit>
 </match>
 <match target="font" >
  <edit mode="assign" name="autohint" >
   <bool>true</bool>
  </edit>
 </match>
 <match target="font">
  <edit mode="assign" name="hintstyle" >
  <const>hintslight</const>
  </edit>
 </match>
 <match target="font">
  <edit mode="assign" name="rgba" >
   <const>rgb</const>
  </edit>
 </match>
 <match target="font">
  <edit mode="assign" name="antialias" >
   <bool>true</bool>
  </edit>
 </match>
 <match target="font">
   <edit mode="assign" name="lcdfilter">
   <const>lcddefault</const>
   </edit>
 </match>
 <!-- Helvetica is a non true type font, and will look bad. This
replaces it with whatever is the default sans-serif font -->

<match target="pattern" name="family" >
<test name="family" qual="any" >
<string>Helvetica</string>
</test>
<edit mode="assign" name="family" >
<string>sans-serif</string>
</edit>
</match>
<dir>~/.fonts</dir>

</fontconfig>

Offline

#4 2015-10-08 06:58:22

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 8,759
Website

Re: Upgrade #! Waldorf to Debian jessie Pt. 1

Nice guide, thanks!

The Waldorf system should be probably be fully updated *before* changing /etc/apt/sources.list

sudo apt-get update
sudo apt-get upgrade

There is a section in the Debian 8 release notes that covers the process of switching from wheezy to jessie in great detail:
https://www.debian.org/releases/stable/ … ng.en.html


“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII., 18.

Forum Rules   •   How to report a problem   •   Software that rocks

Offline

#5 2015-10-08 17:02:47

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

Re: Upgrade #! Waldorf to Debian jessie Pt. 1

Head_on_a_Stick wrote:

Nice guide, thanks!

The Waldorf system should be probably be fully updated *before* changing /etc/apt/sources.list

You're right, I was lucky not to have trouble directly upgrading. I'll update the OP.

There is a section in the Debian 8 release notes that covers the process of switching from wheezy to jessie in great detail:
https://www.debian.org/releases/stable/ … ng.en.html

+1.

Offline

#6 2015-10-08 17:15:50

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

Re: Upgrade #! Waldorf to Debian jessie Pt. 1

OP edited, I linked to the Installation guide and re-ordered it a bit.

Offline

#7 2015-11-11 10:51:07

Jess
New Member
Registered: 2015-11-11
Posts: 2

Re: Upgrade #! Waldorf to Debian jessie Pt. 1

@hhh: thanks for a great how-to.

Is there a part 2 somewhere?

Or do I just uninstall all CB-* packages and install all the Bunsen packages here: https://www.bunsenlabs.org/resources.ht … ug-reports?

Offline

#8 2015-11-11 14:41:34

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

Re: Upgrade #! Waldorf to Debian jessie Pt. 1

Yeah, there's no Part2 yet. That partition doesn't even exist on my system any more. tongue

Jess wrote:

Or do I just uninstall all CB-* packages and install all the Bunsen packages here: https://www.bunsenlabs.org/resources.ht … ug-reports?

That's the idea, yes, but it's not going to be quite that simple. Installing the bunsen-* packages won't properly configure them in some cases. Especially bunsen-configs, that will install to /usr/share/bunsen/skel ( I think?) but you'll need to copy those files to the right locations under ~/.config. But you probably won't want your current configs completely overridden, so some lengthy file comparison may be in order.

Another example is that installing bunsen-themes will mean they'll be on your system, but of course you still need to choose them in the various settings managers.

BTW, the packages are named bunsen-*, the actual scripts are named bl-* (so bl-exit in /usr/bin, not bunsen-exit).

If you get it all figured out, post back so we can create Part2!

Offline

#9 2015-11-19 02:45:38

Jess
New Member
Registered: 2015-11-11
Posts: 2

Re: Upgrade #! Waldorf to Debian jessie Pt. 1

hhh wrote:

If you get it all figured out, post back so we can create Part2!

Hmmm, I like to live dangerously so I just followed your instructions, then did a `sudo apt-get purge cb-*`, changed over the apt source to the bunsen ones, and thenn installed all the listed bunsen-* packages.

I havent found any problems yet - after a restart bunsen came up  per normal with all menus etc intact and with all the themes applied. The only thing i had left to do was to pull my tint2/conky configs from waldorf from github and I was right at home.

YMMV of course, but it worked for me...

Offline

#10 2016-02-11 02:29:33

RitterSport
New Member
Registered: 2016-02-11
Posts: 2

Re: Upgrade #! Waldorf to Debian jessie Pt. 1

Hi!  I know I'm a little late to this party, but I just recently started getting warnings from Chrome that it will soon no longer support Wheezy and I thought I should find a way to upgrade to Jessie.

So, I think I followed all the steps, but I must have missed something -- I'm missing the bar along the top that has the window icons and the various status icons (wi-fi, battery, etc.).  Without the window icons, if I minimize a window, the only way to get back to it is to alt-tab.  I also have no idea how much battery remains, what the volume is, and so on.

Any idea which step I might have missed?

Edited to add:  I figured it out.  I had left the autostart section the same since it looked so close to what I already had (only changing compositor to compton).  I guess the old syntax has changed or something.  Anyway, autostart is now starting tint2 properly and all is well.  Thanks so much for putting this guide together!

Last edited by RitterSport (2016-02-11 02:40:12)

Offline

#11 2016-02-11 02:41:59

tknomanzr
BL Die Hard
From: Around the Bend
Registered: 2015-09-29
Posts: 1,029

Re: Upgrade #! Waldorf to Debian jessie Pt. 1

Star by installing tint2

sudo apt install tint2

If you are still missing icons after that, post back and we will sort it out once tint2 is installed and you can actually tell what you are missing.

Offline

#12 2016-02-11 02:51:37

RitterSport
New Member
Registered: 2016-02-11
Posts: 2

Re: Upgrade #! Waldorf to Debian jessie Pt. 1

Thanks for the quick response!  I actually figured it out -- autostart wasn't properly starting up tint2.  I should have made a new post rather than just editing my old one.

Thanks, though.  Linux support is definitely the best.

Offline

#13 2016-04-25 15:13:22

Maki
Member
Registered: 2016-04-14
Posts: 26

Re: Upgrade #! Waldorf to Debian jessie Pt. 1

I'm going to run through this soon on a Waldorf lappy, but it looks to cover just about anything I can think of. Wish me luck?


Break BunsenLabs. Learn how it works. Help find bugs and build new additions. Give back to the community. If you don't take LEGO apart you can't build new things with it.

Offline

Board footer

Powered by FluxBB