Updating Crunchbang to the Next Release

I’ve jumped across many Linux distros, and lately I’ve found myself really enjoying the simplicity of Crunchbang. It’s extremely lightweight, and I found my old Asus EEEpc netbook can handle it rather well. Well enough for me to abandon Lubuntu to run it exclusively on that netbook. The only drawback I’ve found is that since it draws directly from Debian stable, I can’t always get the most up to date software. I don’t mind not being bleeding edge, if that was the case I’d be running Arch or Gentoo, but sometimes I would like have some more recent packages available. With that being said, I recently updated my #! configuration to draw from the next release of Debian (jessie) instead of stable (wheezy). Here’s how to do it.

  1. Update your sources.list.
    $ sudo vim /etc/apt/sources.list

    And change all references of stable (wheezy) to testing (jessie). I also updated my references to waldorf to janice to catch new packages for #!.

    ## Compatible with Debian Wheezy, but use at your own risk.
    deb http://packages.crunchbang.org/janice janice main
    #deb-src http://packages.crunchbang.org/janice janice main
    # DEBIAN
    deb http://http.debian.net/debian jessie main contrib non-free
    #deb-src http://http.debian.net/debian jessie main contrib non-free
    deb http://security.debian.org/ jessie/updates main
    #deb-src http://security.debian.org/ jessie/updates main
  2. Update apt configuration.
    $ sudo vim /etc/apt/preferences
    Package: *
    Pin: release a=janice
    Pin-Priority: 1001
    Package: *
    Pin: release a=jessie
    Pin-Priority: 500
  3. Upgrade to janice/jessie
    $ sudo apt-get update
    $ sudo apt-get --no-install-recommends dist-upgrade

Overall it was a pretty easy and straightforward process.


~ by jschueths on April 2, 2014.

11 Responses to “Updating Crunchbang to the Next Release”

  1. Reblogged this on anthonyvenable110.

  2. You have a waldorf and waldorm in your example which should read janice off course… But its upgrading!

  3. You may notice that GTK applications won’t work, it’s because of the Waldorf theme that isn’t GTK3 compatible. To correct it, change your theme with “lxappearance”. You need also change it for root user, so do as well a change with “sudo lxappearance”. Happy Crunchbanging!

  4. tried it twice, completely borked my system… must be a combination of the latest packages from testing.

  5. Janice repository for CrunchBang is empty, so “deb http://packages.crunchbang.org/janice janice” is completely useless. If you want to use cb- packages you must keep waldorf line here.

  6. […] aim to use the latest versions of all the tools, and I’ll describe the process using Crunchbang (configured to track Debian Testing). Since we’ll be getting most of the tools from their source, a lot of the steps aren’t […]

  7. I think you’re going to need the public key and you may need to modify apt.conf too :-/


    • In my case I didn’t need to add the public key because I was upgrading an existing install of Crunchbang to Debian testing. So I already had the public keys for Crunchbang and Debian, so there was no extra work for me.

  8. For apt.conf you can just do this:

    APT “”;
    APT::Install-Recommends “false”;

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: