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.
- 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 #!.
## CRUNCHBANG ## 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 # DEBIAN SECURITY deb http://security.debian.org/ jessie/updates main #deb-src http://security.debian.org/ jessie/updates main
- Update apt configuration.
$ sudo vim /etc/apt/preferences
Package: * Pin: release a=janice Pin-Priority: 1001 Package: * Pin: release a=jessie Pin-Priority: 500
- 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.
Reblogged this on anthonyvenable110.
anthonyvenable110 said this on April 2, 2014 at 9:43 am |
You have a waldorf and waldorm in your example which should read janice off course… But its upgrading!
Iedjee said this on May 24, 2014 at 6:20 am |
Thanks for catching that.
jschueths said this on May 27, 2014 at 10:26 am |
Now you’ve corrected it, perfect! Im enjoying my Janice / Jessie…
Iedjee said this on May 27, 2014 at 10:31 am
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!
Iedjee said this on May 27, 2014 at 11:27 pm |
tried it twice, completely borked my system… must be a combination of the latest packages from testing.
Phresh said this on October 20, 2014 at 7:45 am |
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.
thoronaug said this on January 4, 2015 at 4:46 am |
[…] 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 […]
Open Source development for STM32L processors under Linux (Introduction) | Dr. Watt said this on January 18, 2015 at 12:34 pm |
I think you’re going to need the public key and you may need to modify apt.conf too
http://crunchbang.org/forums/viewtopic.php?id=26538
PJ Brunet said this on February 2, 2015 at 8:37 pm |
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.
jschueths said this on February 3, 2015 at 10:15 am |
For apt.conf you can just do this:
APT “”;
APT::Install-Recommends “false”;
PJ Brunet said this on February 2, 2015 at 8:39 pm |