HOW-TO Upgrading from #!Stable to #!Testing

thevdude · 2011-09-26 13:00:34

STEP 1: Setting up the Sources

This guide assumes you're going to Testing. You'll want to comment out all the lines in /etc/apt/sources.list. Then, add this to the bottom:

## DEBIAN
# TESTING
deb http://ftp.us.debian.org/debian testing main contrib non-free
deb-src http://ftp.us.debian.org/debian testing main contrib non-free

## DEBIAN SECURITY
# TESTING
deb http://security.debian.org/ wheezy/updates main

Save and close. We're one step closer to having testing! big_smile

STEP 2: Preferences and apt.conf

Okay, these next steps are kind of important, so listen up! There's at least two more files we need to change, and it's easy to do! open up /etc/apt/preferences and comment out everything in there by putting a # infront of them. (I like to keep things in the file incase something gets messed up. Then you can just switch the comments around, and you have it back to normal)

Now, this file assigns priorities to different packages, and we want testing to have highest priority. So we'll do something like this:

Package: *
Pin: release a=testing
Pin-Priority: 990

#Package: *
#Pin: release n=statler
#Pin-Priority: 1001

#Package: *
#Pin: release n=squeeze
#Pin-Priority: 100

That'll give packages from testing a priority of 990, which should make them the default choice (especially considering that there aren't any other sources)

Now you'll also want to edit /etc/apt/apt.conf. This is a quick, one word change:

APT::Default-Release "testing";

And the sources and preferences are set up! big_smile

STEP 3: Fixing stupid perl loop

If you're lucky, all that was all you needed. But in some cases, if you were try to do a sudo apt-get update && sudo apt-get dist-upgrade now, you'd get into a loop like this:

Preparing to replace libc6 2.11.2-10 (using .../libc6_2.13-16_i386.deb) ...
substr outside of string at /usr/share/perl5/Text/WrapI18N.pm line 130, <GEN1> line 4.

And that's no good. So we'll change that file a tiny bit, and make it work for us! big_smile Open /usr/share/perl5/Text/WrapI18N.pm into any editor you want that has a line count. Go to line 130. It should say

$r = substr($string, $l);

but we're going to change it to

if (length($text) < $l) {
    $r = '';
} else {
    $r = substr($string, $l);
}

and save it. We're now all ready to try out #!Testing! big_smile GET READY TO BLOW YOUR FREAKING SOCKS OFF!

STEP 4: BLOW YOUR FREAKING SOCKS OFF

Open up a terminal and run sudo apt-get update && sudo apt-get dist-upgrade

Wait a while while everything updates, and stand by because I'm pretty sure it'll want some input on a few things. If asked to replace any config files, open another terminal and backup the original and choose to replace. In my case (on a fresh installation) it only wanted to change 2 files, and I said Y.

Some issues with testing I've found:

Thunar finds my windows network, finds my desktop that I serve files from, and finds the folders themselves that I have shared. But it doesn't mount those folders. No, that would be too great. sad No problem mounting them from terminal or fstab, though. big_smile

Reboot (both from cb-logout script and shutdown -r now) reboots the kernel, not the computer. Not a huge issue, but a pain if you forget.

psyco430404 · 2011-09-26 13:17:32

That's a pretty good guide, nice work big_smile . Have you noticed any breakage with testing or is it fairly stable?

sunfizz98 · 2011-09-26 16:30:23

Nice work there! I'm assuming that you could do the same steps for unstable too?

thevdude · 2011-09-26 17:35:10

psyco430404 wrote:

That's a pretty good guide, nice work . Have you noticed any breakage with testing or is it fairly stable?

Nope. Everything working great! big_smile After I backup, I think I'm going to try unstable.

sunfizz98 wrote:

Nice work there! I'm assuming that you could do the same steps for unstable too?

Yup, just change all the testings to unstable, and get rid of the security repo. There isn't a security repo for sid.

sunfizz98 · 2011-09-26 18:05:58

@thevdude
Let me know about the results, cause I might want to do it for my desktop pc. I'm thinking x64bit too.

thevdude · 2011-09-26 19:26:30

Don't hold out on me. I'm extremely lazy and probably won't set up a backup for another week. D:

rizzo · 2011-09-26 20:30:52

thevdude wrote:

Thunar finds my windows network, finds my desktop that I serve files from, and finds the folders themselves that I have shared. But it doesn't mount those folders. No, that would be too great. No problem mounting them from terminal or fstab, though. .

It would be good to add some info on how to do this to the howto or in a new howto that you could place a link to. If you don't have time to do that, let me know and I'll write it smile I'm thinking something like this but referencing thunar instead of nautilus http://forums.linuxmint.com/viewtopic.php?f=42&t=42713

el_koraco · 2011-09-26 20:55:02

Rawr, I'm starting to itch a jump to Sid, but everything is working so good...

psyco430404 · 2011-09-26 21:43:13

sunfizz98 wrote:

@thevdude
I'm thinking x64bit too.

64 bit is great lol, only prob is if you use squeeze repos the wine is broken hmm

sunfizz98 · 2011-09-27 01:01:10

^That's when you add the frickelplatz repos.

thevdude · 2011-09-27 01:11:17

omns wrote:

thevdude wrote:
Thunar finds my windows network, finds my desktop that I serve files from, and finds the folders themselves that I have shared. But it doesn't mount those folders. No, that would be too great. No problem mounting them from terminal or fstab, though. .
It would be good to add some info on how to do this to the howto or in a new howto that you could place a link to. If you don't have time to do that, let me know and I'll write it I'm thinking something like this but referencing thunar instead of nautilus http://forums.linuxmint.com/viewtopic.php?f=42&t=42713

TBH, it was as simple as adding //AWESOME/music /mnt/networkmusic smbfs default,credentials=/home/robert/.config/.smbpass 0 0

although cifs instead of smbfs might work.

sunfizz98 · 2011-09-27 19:27:15

@thevdude
Do you still use the standard kernels provided by crunchbang or do you use smxi to fetch kernels?

nathwill · 2011-09-27 19:44:42

sticky!

gurtid · 2011-10-01 01:08:32

goddamn it! now i remember y i don't like wheezy openbox - xcompmgr doesn't play well on my setup (intel graphics)

good guide tho' thevdude . . .

ColInvictus · 2011-10-01 16:47:47

Nice. I just did this, but I left the Statler repo in sources.list and default release as "statler" in apt.conf. Is it odd that I had to run aptitude dist-upgrade 3 times to resolve all the dependencies?

gurtid · 2011-10-01 21:48:23

^-- no, quite common.

ColInvictus · 2011-10-01 22:39:34

Fair enough then. I've just got done installing #! in a VM on my Windows PC so I could get the #! Plymouth theme back - Wheezy overwrote it with a Debian theme. And I had to fix my grub custom settings as the scripts used in Statler seem to be a bit idiosyncratic. But generally everything went better than expected. Which is nice.

gurtid · 2011-10-02 05:20:09

Cool. i'm interested in wot's involved in restoring the statler plymouth theme so post up some details if you have time . . .

ColInvictus · 2011-10-02 10:25:06

It's dead simple if you have access to another install of #!. As I said, in my case I did a fresh install on a virtual machine. I did look at the disc image to see if I could find what I needed without installing, but it eluded me. Anyhoo, it was just a case of copying

/usr/share/plymouth/script/

from the VM to my newly Wheezied computer and running

plymouth-set-default-theme script
update-initramfs -uk all

to apply the change and badda bing, badda boom.

gurtid · 2011-10-02 10:29:55

awesome - thank you

ColInvictus · 2011-10-02 13:55:42

Been thinking (rarely a good thing). Wouldn't it make sense to leave the Statler repo in sources.list and let apt assign it the default priority? That way, any changes (unlikely, but not impossible) to any crunchbang-* packages or what-have-you will still be available, but Wheezy will take precedence with its 990 priority in apt_preferences. It's what I did and everything still seems to work.

Last edited by ColInvictus (2011-10-02 13:56:16)

Ozitraveller · 2011-10-06 00:51:54

It's been a few days since the last post and I'm wondering if anyone that has tried this has had any subsequent problems?

gurtid · 2011-10-06 04:19:17

i 'essentially' did this on this particular 64bit ob machine (but let smxi control the actual upgrade process). no major problems with the upgrade. on this machine (intel graphics) compositing bogs down a bit - only noticable moving windows - and sound is muted on startup.

wot r your particular concerns? performing the upgrade or running wheezy?

Ozitraveller · 2011-10-06 05:03:51

Running wheezy. What did you do with smxi?

machinebacon · 2011-10-06 05:44:33

www.smxi.org hosts a bundle of scripts which can help you with adding kernels, updating prop. gfx drivers and takes care of cleaning up crust, removes old kernels, etc. I like it, too. Only supports testing/unstable, officially.

CrunchBang Linux

SEARCH

#1 2011-09-26 13:00:34

HOW-TO Upgrading from #!Stable to #!Testing

#2 2011-09-26 13:17:32

Re: HOW-TO Upgrading from #!Stable to #!Testing

#3 2011-09-26 16:30:23

Re: HOW-TO Upgrading from #!Stable to #!Testing

#4 2011-09-26 17:35:10

Re: HOW-TO Upgrading from #!Stable to #!Testing

#5 2011-09-26 18:05:58

Re: HOW-TO Upgrading from #!Stable to #!Testing

#6 2011-09-26 19:26:30

Re: HOW-TO Upgrading from #!Stable to #!Testing

#7 2011-09-26 20:30:52

Re: HOW-TO Upgrading from #!Stable to #!Testing

#8 2011-09-26 20:55:02

Re: HOW-TO Upgrading from #!Stable to #!Testing

#9 2011-09-26 21:43:13

Re: HOW-TO Upgrading from #!Stable to #!Testing

#10 2011-09-27 01:01:10

Re: HOW-TO Upgrading from #!Stable to #!Testing

#11 2011-09-27 01:11:17

Re: HOW-TO Upgrading from #!Stable to #!Testing

#12 2011-09-27 19:27:15

Re: HOW-TO Upgrading from #!Stable to #!Testing

#13 2011-09-27 19:44:42

Re: HOW-TO Upgrading from #!Stable to #!Testing

#14 2011-10-01 01:08:32

Re: HOW-TO Upgrading from #!Stable to #!Testing

#15 2011-10-01 16:47:47

Re: HOW-TO Upgrading from #!Stable to #!Testing

#16 2011-10-01 21:48:23

Re: HOW-TO Upgrading from #!Stable to #!Testing

#17 2011-10-01 22:39:34

Re: HOW-TO Upgrading from #!Stable to #!Testing

#18 2011-10-02 05:20:09

Re: HOW-TO Upgrading from #!Stable to #!Testing

#19 2011-10-02 10:25:06

Re: HOW-TO Upgrading from #!Stable to #!Testing

#20 2011-10-02 10:29:55

Re: HOW-TO Upgrading from #!Stable to #!Testing

#21 2011-10-02 13:55:42

Re: HOW-TO Upgrading from #!Stable to #!Testing

#22 2011-10-06 00:51:54

Re: HOW-TO Upgrading from #!Stable to #!Testing

#23 2011-10-06 04:19:17

Re: HOW-TO Upgrading from #!Stable to #!Testing

#24 2011-10-06 05:03:51

Re: HOW-TO Upgrading from #!Stable to #!Testing

#25 2011-10-06 05:44:33

Re: HOW-TO Upgrading from #!Stable to #!Testing

Board footer