SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 2011-11-30 11:24:46

machinebacon
#! unstable
From: China
Registered: 2009-07-02
Posts: 6,826
Website

HowTo: Upgrade the #! Point Release to sid

This HowTo is written for/on a #! Point Release (originally the November 2011 version) with unstable (Sid) sources. It is reported to work on the 20120207 64bit backports release of Statler, too. It has been tested with Waldorf (wheezy) and seem to work okay, too.
It may or may not work with testing (jessie) - just change the sources.list, apt.conf, and apt/preferences accordingly. If somebody wants to try the testing variant, and it works, let me know and I change this introduction.

Debian calls sid an 'unstable' release, but this name derives from the fact that the updates for packages are coming in many times a day. The 'stable' release uses packages which have been tested on many different machines, for quite a long time. If you don't want to waste (or spend) time to maintain your computer and to download megabytes of updates a day, you better go with something like Debian Squeeze or CentOS. If you run a server, forget sid.

The difficulty of the transition is moderate, but you won't get away with copy & paste only. Read the instructions first, and if you are unclear, write a post and ask. I'll try to answer ASAP.

Generally, you should always use apt-get dist-upgrade and not synaptic (use synaptic only if you wish to search for packages, though I recommend apt-cache search SEARCH_TERM) if you run sid.

Installation

We start with a USB stick or CD, on which you successfully wrote your newestCrunchbang Statler iso. First of all, the creation of a bootable USB stick which detects network and CD-ROM correctly will most probably not work with unetbootin. I have used a live-usb-installer from http://www.learnfree.eu but you can use the dd method (see the #! WIKI) or, in Windows, use the Linux Live Installer.
If you get stuck in the boot process of your CD/USB or in the Debian (#!) installer, refer to the Support (Stable) Section of the #! forums
http://crunchbanglinux.org/forums/forum … rt-stable/

Boot into the newly installed system and configure the network. If this already fails here, again search help in the Support (Stable) section of the #! forums. To this point, you're running a standard #! Statler install.

Cancel post-installation script.

All of the following actions need elevated user privileges.

I'll use nano as default editor, you can pick geany, vi, ed, a magnetic needle...

Depending on your installation - and its network detection in the Debian installer - your sources.list is either fully populated or quite bare. Basically, the /etc/apt/sources-list-post-preseed file (if existing) can be copied to /etc/apt/sources.list

nano /etc/apt/sources.list

change the content to:

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

## CRUNCHBANG MULTIMEDIA
## Debian Multimedia Mirror
#deb http://packages.crunchbang.org/statler-mm squeeze main non-free
#deb-src http://packages.crunchbang.org/statler-mm squeeze main non-free

## CRUNCHBANG MOZILLA
## Debian Mozilla Mirror
#deb http://packages.crunchbang.org/statler-mozilla squeeze-backports iceweasel-release
#deb-src http://packages.crunchbang.org/statler-mozilla squeeze-backports iceweasel-release

## DEBIAN
deb http://ftp.debian.org/debian/ sid main contrib non-free
#deb-src http://ftp.debian.org/debian/ squeeze main contrib non-free

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

Optional: You can change the official Debian mirror to something closer to your location. See: http://www.debian.org/mirror/list

We can add the unofficial Debian multimedia repository later - I haven't looked into the #! MM repositories, yet. Backports are disabled from now on.

Preparing the dist-upgrade

We need to change the release defaults in apt.conf - if your apt.conf is blank, create it. We can also create another configuration file in /etc/apt/apt.conf.d/ if we want to keep the modularity

nano /etc/apt/apt.conf
#and
nano /etc/apt/apt.conf.d/00DefaultRelease

change the content to:

APT::Default-Release "sid";

Let's edit APT's preferences:

nano /etc/apt/preferences

change the priority:

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

Package: *
Pin: release n=sid
Pin-Priority: 500

So, even if (for whatever reasons) backports would be enabled, they'd only get a default priority of 100. If set like this, we can only manually install backports if we really want to.

---------------------------------
Save and exit.
---------------------------------

Update & Dist-upgrade

Now comes the update and upgrade part. Usually you can simply

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

If you want to play super-safe, do this:

sudo apt-get dist-upgrade -d

and then either leave X (init 1) or reboot, in GRUB pick Recovery Mode, boot into the tty and apply apt-get dist-upgrade

This will take a while, I had to download around 600MB, YMMV. You'll be asked questions related to Samba, whether certain services  should be restarted etc. Nothing spectacular.

If you get asked what you want to do with:
Configuration file `/etc/issue.distrib' - choose Y
Configuration file `/etc/issue.net.distrib' - choose Y
Configuration file `/etc/sudoers' - choose Y (you'll need to add your user to the sudoers manually, if you wish so)

Messages about "Required firmware files may be missing" can be ignored.

Time for a

reboot

The First boot into Sid

If there are two nm-applets in the tray, try:

rm /etc/xdg/autostart/nm-applet.desktop

You can now remove the crunchbang repos from /etc/apt/sources.list, if you like so. At the moment they don't conflict with Sid, but we never know.

PolicyKit

If you have problems with PolicyKit, use ConsoleKit's ck-launch-session by changing the login_cmd line of your /etc/slim.conf to:

login_cmd exec ck-launch-session /bin/bash -login ~/.xinitrc %session

and make an ~/.xinitrc file

#!/bin/sh
exec openbox-session

Mounting External Drives

If your external (ntfs) drives are not mounted in Thunar, try to

apt-get install ntfs-config ntfs-3g 

and run ntfs-config as root. After this,

apt-get install disk-manager

and run it as root. After a reboot your drives should be mounted automatically. (Thanks @Texus)

No Logout with cb-exit

If you are using the cb-exit script, which relies on hal, and you cannot log out from the Openbox Menu, add following part to the ~/.config/openbox/menu.xml, replacing the cb-exit entry (Thanks @jelloir)

    <menu id="session-menu" label="Session">
        <item label="Logout"><action name="Exit"><prompt>no</prompt></action></item>
        <item label="Suspend"><action name="Execute"><execute>
            dbus-send --system --print-reply --dest=org.freedesktop.UPower /org/freedesktop/UPower org.freedesktop.UPower.Suspend
        </execute></action></item>
        <item label="Hibernate"><action name="Execute"><execute>
            dbus-send --system --print-reply --dest=org.freedesktop.UPower /org/freedesktop/UPower org.freedesktop.UPower.Hibernate
        </execute></action></item>
        <item label="Poweroff"><action name="Execute"><execute>
            dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop
        </execute></action></item>
        <item label="Restart"><action name="Execute"><execute>
            dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart
        </execute></action></item>
    </menu>

It's also possible to shutdown with the following entries in menu.xml (Thanks @Corvo)

<item label="Reboot">
<action name="Execute"> <execute>sudo 'shutdown -r now'</execute> </action> </item>
<item label="Shut down">
<action name="Execute"> <execute>sudo 'shutdown -h now'</execute> </action> </item>

which requires adding the user in the sudoers:

visudo

at the bottom of the page, add

ALL   ALL=NOPASSWD:/sbin/shutdown

hal?
Talking of hal, if you still have the hal package installed, you'll get a bunch of error messages at boot (they're harmless). You can remove hal, it's old and smelly and not suported anymore.

Thunar, mounting, other shit
This guide was written when Debian was still using udisks. They have already moved to udisks2, so you might want to install that package if it's not pulled in by upgrades. Also, see this helpful post: http://crunchbang.org/forums/viewtopic. … 52#p324152 -- you need to edit some files, but it's quite painless.

Optional Steps & Recommendations

Get rid of slim?
Most problems related to shutdown and mounting are "fixed" by installing lightdm or gdm as login manager. Something like

init 1
/etc/init.d/slim stop
apt-get purge slim
apt-get install lightdm
dpkg-reconfigure lightdm
/etc/init.d/lightdm start

should do the trick.

Get rid of login managers
This is what I actually prefer and recommend. It shaves off a bit of RAM, so if this is an issue, follow me:

### leave your X session
### get rid of slim, lightdm or whatever login manager you use
sudo apt-get autoremove --purge slim
### edit your ~/.xinitrc file
nano ~/.xinitrc

Now comes the interesting part. Usually, a simple

#!/bin/sh
exec openbox-session

should already work. However, different users reported different solutions - here are some of them:

#!/bin/sh
dbus-launch thunar --daemon &
exec openbox-session

or

#!/bin/sh
exec ck-launch-session dbus-launch --sh-syntax --exit-with-session openbox-session

or

#!/bin/sh
. /etc/X11/Xsession
exec openbox-session

or even

#!/bin/sh
. /etc/X11/Xsession
dbus-launch thunar --daemon &
exec openbox-session

Try these, open thunar and try if it (auto)mounts your sticks and hard drives.

Bonus stuff: you can have automatic login to console and X, follow: http://linuxbbq.org/wiki/index.php/Auto … in_console

systemd ate all my init
There's a lot of bullshitting about how people get throat-raped by the Poetterings. Don't listen to them. Having systemd installed does not mean you use systemd as init system. If you want pure systemd, follow this: https://wiki.debian.org/systemd
You can add experimental to your sources.list and get the systemd and udevd packages from there, they are sometimes far more recent than the stuff in sid. Be careful, though.

HAL or consolekit?
As #! still relies on HAL to shutdown, I recommend changing the menu.xml so that cb-exit is not used anymore. (see above!)

Get a short summary of bugs before installing with apt

apt-get install apt-listbugs

Add the Debian multimedia repos (quote)

For sid (unstable) alpha, amd64, armel, hppa, i386, ia64, mipsel, powerpc and sparc packages.
add in your /etc/apt/sources.list
deb http://www.debian-multimedia.org sid main non-free
or
deb ftp://ftp.debian-multimedia.org sid main non-free

Security net, thanks to siduction
I warmly recommend using siduction repositories if you track sid. They have some additional applications like ceni (network configuration tool, I recommend it as a replacement for nm). You'll also get smoking hot kernels, always just one revision behind the newest of kernel.org -- and that's damned fresh and frequently updated, patched.

nano /etc/apt/sources.list

add these lines (of course, you can visit siduction.org and add other mirrors if you think these are too slow for you)

deb http://ftp.uni-stuttgart.de/siduction/user unstable main
#deb-src http://ftp.uni-stuttgart.de/siduction/user unstable main

deb http://ftp.uni-stuttgart.de/siduction/base unstable main contrib non-free
#deb-src http://ftp.uni-stuttgart.de/siduction/base unstable main contrib non-free

deb http://ftp.uni-stuttgart.de/siduction/extra unstable main contrib non-free
#deb-src http://ftp.uni-stuttgart.de/siduction/extra unstable main contrib non-free

deb http://ftp.uni-stuttgart.de/siduction/fixes unstable main contrib non-free
#deb-src http://ftp.uni-stuttgart.de/siduction/fixes unstable main contrib non-free

(don't forget to apt-get update!)

additional gfx stuff - use with caution
Use the epic smxi script for kernel upgrades, installation of gfx drivers, and generally as dist-upgrade tool (as root):

cd /usr/local/bin && wget -Nc smxi.org/smxi.zip && unzip smxi.zip && smxi

You will need to use smxi outside of X (init 1) - I copied this line from www.smxi.org

Grab the "old" statler Shiki-themes and the murrine engine, if you like (as normal user)

wget -c http://packages.crunchbanglinux.org/statler/pool/main/crunchbang-extra-themes_0.1_all.deb
wget -c http://packages.crunchbanglinux.org/statler/pool/main/statler-theme_0.20_all.deb
wget -c http://packages.crunchbanglinux.org/statler/pool/main/gtk2-engines-murrine_0.91.0-crunchbang-1~git201009100045_i386.deb

Use dpkg -i packagename.deb (as root) to unpack and install - they may or may not work big_smile

If slim works well for you, you can enable autologin like this:

nano /etc/slim.conf

change:

# default user, leave blank or remove this line
# for avoid pre-loading the username.
#default_user        simone

to

# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user        YOUR_USERNAME_HERE

and

# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login          no

to

# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
auto_login          yes

The ugliness of the few gtk-3.0 apps will only disappear if you
- replace nm-applet with (eg.) wicd, ceni, or manually use ifup/ifdown and replace evince with epdfview
- or find a gtk2/gtk3 theme *and* create

nano ~/.config/gtk-3.0/settings.ini 

where you add, for example

[Settings]
gtk-theme-name = NAME_OF_YOUR_THEME
gtk-icon-theme-name = gnome-colors-statler
gtk-fallback-icon-theme = gnome
# next option is applicable only if selected theme supports it
gtk-application-prefer-dark-theme = true
# set font name and dimension
gtk-font-name = Sans 10

Of course this theme shall be picked in lxappearance, too. Addendum: whenever possible, try to stay away from gtk3 applications. If you have problems with sid, they are usually coming from libgtk3. So, check the 'Unstable' section of the support forums for posts related to 'themes' or 'applications not starting'.

I'm sure I forgot something big_smile Have "fun" with the sidomized #! point release. If you find something is wrong, feel free to correct me.

Thanks el_koraco, Thorny, jelloir for their constructive input and everybody else who has bothered reading, testing and giving feedback. If certain points in this howto cause inconvenience (especially the way slim/cb-exit is handled) I like to apologize - I wanted to stay as close as possible to the standard point release, yet try to have a smooth transition with an installation that aims to be as reliable as Statler, but based on Sid.  Thanks to all who followed this guide and reported problems or success.

If you want to make a crunchification of the excellent (but ugly) aptosid, take a look at sunfizz' Howto: http://crunchbanglinux.org/forums/topic … x-version/ Be sure to read through jelloir's Debian Sid + Openbox Wiki http://crunchbanglinux.org/forums/topic … top-guide/ which covers the netinstall route and is a good resource for troubleshooting.

Info on Upgrading

- Always use

apt-get update && apt-get dist-upgrade 

- If possible, do this outside of X (init 1)
- Read the fscking output. Read what is going to be removed. If there are more packages removed than downloaded or upgraded, be careful. Sid receives updates four times a day. Waiting is always a good choice, use the time to visit the forums and see if there are upgrade warnings.
- It's a good idea to use the smxi script. Nevertheless, you have to read the output. If you are unclear, don't be shy, and ask on the #! forums. If you use KDE packages in Sid, you should better add the siduction sources and visit the siduction forums regularly. If you use Gnome3 packages in Sid, you're trying to remove the safety cap to drink bleach. That's my stupid opinion, but has saved me a lot of inconvenience.
- Do not mix squeeze/wheezy/sid, stable/testing/unstable, or any other combination. Stay with one. Once you are in sid/unstable, the way back to stable is not impossible, but very hard. Do not mix sid with anything like wheezy, testing, stable, statler, squeeze, hardy, etch, potato, whatnot!
- Don't use Ubuntu debs or even PPAs. If you do so, you will break your system. Not because I hate Ubuntu, but they are not designed for Debian. You can (!) install single smaller packages that only contain a python script or something like this, but nothing that is designated to run on Ubuntu only. Nah, rather build from sources - you would even learn something useful.
- Be careful if there are transitions happening in sid (bigger version changes of big packages, like perl, gcc) - they need a few days to be fully available in the repositories, and a typical feature is a huge number of removed packages. In this case do not upgrade. Wait a few days, usually after 2-3 days the transition is completed (for the common architectures, at least)
- Learn APT. Synaptic is for girls.

apt-cache search <term>
apt-cache depends <package>
sudo apt-get install <package>
sudo apt-get remove --purge <package>

By the way, in sid you can now use "apt" instead of "apt-get". Looks nicer, too.

References / Further readings:

debian sid openbox guide: http://wiki.bitbinary.com/index.php/Deb … _-_Openbox
linuxbbq upgrade warnings for sid: http://linuxbbq.org/bbs/viewforum.php?f=9
siduction forums: http://siduction.org/index.php?name=PNphpBB2
aptosidusers forums: http://aptosidusers.de/index.php?name=PNphpBB2
aptosid official forums: http://aptosid.com/index.php?name=PNphpBB2
antix sid upgraders forums: http://antix.freeforums.org/sid-upgraders-f5.html
LMDE forums (testing): http://forums.linuxmint.com/viewforum.p … 3bf58a4004
debian weather: http://edos.debian.net/weather/
debian transitions: http://release.debian.org/transitions/

Last edited by machinebacon (2015-01-25 03:02:51)


Sweaty lads picking up the soap | I love the new "Ignore user" button

Offline

Be excellent to each other!

#2 2011-11-30 12:39:15

el_koraco
#!/loony/bun
From: inside Ed
Registered: 2011-07-25
Posts: 4,749

Re: HowTo: Upgrade the #! Point Release to sid

nice howto!

Does the new #! release have the root account unlocked? I see you using su to configure sudo. If the account is not unlocked, I would do so, because if sudo gets borked on the upgrade, well, it's not fun.

sudo passwd root

And enter your new root password. From then on you can open a root shell with su - (opens it in root's home folder), or su (opens it in the folder you're in at the time), or login at the console as root.

If memory serves me well, when I did the d-u last time (that was on the old image), I had to remove tint2 for the process to complete. In general, if you run into trouble during the upgrade, the following steps typically apply (i know they helped me):

dpkg --configure -a
apt-get install -f
apt-get dist-upgrade

An extra security measure (as in, if you wanna be super paranoid) once you've changed the sources is to only download the packages, and drop to a root shell to complete the upgrade:

sudo apt-get dist-upgrade -d

Reboot, choose recovery mode at Grub prompt. Once logged in:

apt-get dist-upgrade

This leaves most services disabled, so there's less chance of major breakage. Though machinehippy's instructions should do fine, he is the resident Sid guru around here.

Offline

#3 2011-11-30 12:57:25

machinebacon
#! unstable
From: China
Registered: 2009-07-02
Posts: 6,826
Website

Re: HowTo: Upgrade the #! Point Release to sid

Thanks L-Ko for the input.

It happened that $USER was not in sudoers, that's why I wrote in the instructions that - if somebody is really wanting sudo -  the $USER has to be added, using su.
I got used to using su in Debian, actually sidux/aptosid forced me to it. Basically, it boils down to "use elevated privileges to perform the changes and upgrade", they won't work with a normal account anyway big_smile

The tint2 doesn't need to be changed, you are right that it really needed a removal/reinstall in the previous #!->Sid (or Sid + #!), but now it is going well. I have just finished the transition (and was actually writing the howto while doing it) and I didn't run into any troubles. The only things on hold are lxappearance and conky - these are more or less optional steps, I recommend to hold them (November 30) because else they will definitely not work after the transition, until day X.

The --download-only procedure is of course super-safe (I forgot to mention doing these kinds of dist-upgrades outside of X). It'll be edited in a moment smile

Thanks again for your input!


Sweaty lads picking up the soap | I love the new "Ignore user" button

Offline

#4 2011-11-30 13:04:58

el_koraco
#!/loony/bun
From: inside Ed
Registered: 2011-07-25
Posts: 4,749

Re: HowTo: Upgrade the #! Point Release to sid

machinebacon wrote:

It happened that $USER was not in sudoers, that's why I wrote in the instructions that - if somebody is really wanting sudo -  the $USER has to be added, using su.
I got used to using su in Debian, actually sidux/aptosid forced me to it. Basically, it boils down to "use elevated privileges to perform the changes and upgrade", they won't work with a normal account anyway big_smile

I would generally advise people to unlock the root account. Doesn't matter if it's never used, it can come in handy. I started using it regularly on Ubuntu, out of spite for all those "don't unlock the root account" threads big_smile

Edit: WRT smxi, init 3 is the same as init 2, 4 and 5 in Debian. But it doesn't matter, smxi will offer to shut down X if you run it inside an X session.

Last edited by el_koraco (2011-11-30 13:07:40)

Offline

#5 2011-11-30 13:14:11

machinebacon
#! unstable
From: China
Registered: 2009-07-02
Posts: 6,826
Website

Re: HowTo: Upgrade the #! Point Release to sid

^ Damned, too much sidux big_smile


Sweaty lads picking up the soap | I love the new "Ignore user" button

Offline

#6 2011-11-30 14:25:42

Thorny
#! CrunchBanger
Registered: 2011-05-19
Posts: 113

Re: HowTo: Upgrade the #! Point Release to sid

machinebacon,
It shouldn't be necessary to add a discrete entry to the sudoers file for a user, it should be sufficient to add the user to the sudoers group in order to give the user sudo permissions. There should already be a line enabling the users in the sudo group in the sudoers file.

Offline

#7 2011-11-30 14:29:28

machinebacon
#! unstable
From: China
Registered: 2009-07-02
Posts: 6,826
Website

Re: HowTo: Upgrade the #! Point Release to sid

Thanks Thorny, I remove the complete sudo thing.


Sweaty lads picking up the soap | I love the new "Ignore user" button

Offline

#8 2011-11-30 14:41:46

dubois
The Old Codger
From: Missoula, Montana
Registered: 2010-09-03
Posts: 2,238

Re: HowTo: Upgrade the #! Point Release to sid

That's a mighty impressive HOW TO machinebaconbig_smile

Offline

#9 2011-11-30 16:37:47

corvo
Member
From: Clovis, California, USA
Registered: 2011-11-29
Posts: 43

Re: HowTo: Upgrade the #! Point Release to sid

May I respectfully suggest to the forum mods that the thread topic be made sticky? This is a thorough and excellent HowTo. smile


"It is vain for the coward to flee; death follows close behind; it is only by defying it that the brave escape." - Voltaire

Offline

#10 2011-11-30 17:01:15

VastOne
#! Ranger
From: V-Ger
Registered: 2011-04-26
Posts: 10,165
Website

Re: HowTo: Upgrade the #! Point Release to sid

Impressive MB!

@El_K  ..  I have had sudo borked in a dist-upgrade and that is no fun!


VSIDO | Words That Build Or Destroy

I dev VSIDO

Offline

#11 2011-11-30 17:13:02

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: HowTo: Upgrade the #! Point Release to sid

Nice stuff machinebacon, very nice indeed.


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#12 2011-11-30 17:32:18

hinto
#! Windbag
From: Cary, NC
Registered: 2010-12-08
Posts: 1,487

Re: HowTo: Upgrade the #! Point Release to sid

Nice.... adding the tweeks to my LMDE-> turn #! distro.
-Hinto


"Sometimes I wish I hadn't taken the red pill" -Me

Offline

#13 2011-11-30 18:46:09

sunfizz98
Carbonated Orange Juice
From: su terminal
Registered: 2011-05-12
Posts: 1,876
Website

Re: HowTo: Upgrade the #! Point Release to sid

Excellent HowTo! Will try this soon for my newly installed #! desktop.

However, wouldn't it be wise to remove the #! MM repos in favor of sid's debian multimedia repo?

I will need to replace evince for epdfview to see how that goes and possibly incorporate that into my howto.

Last edited by sunfizz98 (2011-11-30 18:46:40)

Offline

#14 2011-11-30 19:18:16

machinebacon
#! unstable
From: China
Registered: 2009-07-02
Posts: 6,826
Website

Re: HowTo: Upgrade the #! Point Release to sid

^ Sunfizz, thanks for the feedback - the mm repos are commented.... (as I have not tested them yet, and I know that the sid ones definitely work well)

Last edited by machinebacon (2011-11-30 19:18:58)


Sweaty lads picking up the soap | I love the new "Ignore user" button

Offline

#15 2011-11-30 19:25:23

kowloonboy
#! Junkie
Registered: 2011-10-13
Posts: 443

Re: HowTo: Upgrade the #! Point Release to sid

@machinebacon - thanks again for a great HowTo. I will give it another go. smile


"To me, the extraordinary aspect of martial arts lies in its simplicity. The easy way is also the right way, and martial arts is nothing at all special; the closer to the true way of martial arts, the less wastage of expression there is." - Bruce Lee

Offline

#16 2011-11-30 19:29:55

vic
#! by Default
From: /grill
Registered: 2009-02-13
Posts: 3,361

Re: HowTo: Upgrade the #! Point Release to sid

corvo wrote:

May I respectfully suggest to the forum mods that the thread topic be made sticky? This is a thorough and excellent HowTo. smile

Relax, if it is not stickied, it will at least end up in the quick reference list for Statler.


Time to move on!#

Offline

#17 2011-11-30 22:57:01

corvo
Member
From: Clovis, California, USA
Registered: 2011-11-29
Posts: 43

Re: HowTo: Upgrade the #! Point Release to sid

Relax, if it is not stickied, it will at least end up in the quick reference list for Statler.

Duly noted, vicshrike, thank you.


"It is vain for the coward to flee; death follows close behind; it is only by defying it that the brave escape." - Voltaire

Offline

#18 2011-12-01 05:21:42

corvo
Member
From: Clovis, California, USA
Registered: 2011-11-29
Posts: 43

Re: HowTo: Upgrade the #! Point Release to sid

@machinebacon: Well, I upgraded to Sid and my wireless ceased to function. sad Not even ifup wlan0 would work. The interface shows up when I use ifconfig, but I am unable to use it. Needless to say, that was enough to get me back to Stable. I will say that was the only glaring issue I ran into, the only other issue was very minor, the two nm-applets in the tray (easily solved by following your instructions). Ah, and in your howto you wrote:

echo laxappearance hold | dpkg --set-selections

When it should be:

echo lxappearance hold | dpkg --set-selections

tongue

Thank you again for your howto! I was hoping to have a "rolling release" Crunchbang, but alas, twas not meant to be. Stable is good enough for now (for me). smile

Last edited by corvo (2011-12-01 05:23:00)


"It is vain for the coward to flee; death follows close behind; it is only by defying it that the brave escape." - Voltaire

Offline

#19 2011-12-01 05:48:37

machinebacon
#! unstable
From: China
Registered: 2009-07-02
Posts: 6,826
Website

Re: HowTo: Upgrade the #! Point Release to sid

^ The wireless problems could have been resolved, a pity you went back... Next time just save the dmesg output and boot into a LiveUSB, post the problems here or on the Stable forums (xaos52 is the king of network issues) and it will be fixed in no time.

@transition: did you start with the new point release or the "old" February Statler?

@wireless: you could have tried to boot into the old kernel (you should have a newer one thanks to the transition and the old backported one, at least) - no matter which kernel you use, the installation is now Sid

@two nm-applets: usually I'd recommend using everything else but not nm, on the other hand this is a brief (and most probably safe) instruction to move from Squeeze to Sid, so I wanted to stay as close as possible to the original (new) release.

@lxappearance: thanks for pointing out the typo, it's corrected smile


Sweaty lads picking up the soap | I love the new "Ignore user" button

Offline

#20 2011-12-01 06:48:30

corvo
Member
From: Clovis, California, USA
Registered: 2011-11-29
Posts: 43

Re: HowTo: Upgrade the #! Point Release to sid

@machinebacon: I began with the new point release (11/2011) to move to Sid. You are right, I should have tried to boot into the backport kernel, I really don't know why I hadn't thought of it. Could be due to the lack of sleep today. As for network-manager, I'm wondering if I should have purged that first and installed wicd in its place before dist-upgrade to Sid? Really, the lack of wireless was the main issue. Ah, and I forgot to mention that for some reason Thunar would start up VERY slowly. That would have been an easier fix. A simple apt-get remove thunar and apt-get install pcmanfm would have been a quick solution. The Thunar issue was an Arch Linux issue for a while there too (it still might be in fact).

Now that I think of it, do you think an upgrade to Testing would be easier/safer, or would I face the same issues? And would the process be, essentially, the same as the instructions you posted here? Example: replace "sid" with "testing" for the repository selection.


"It is vain for the coward to flee; death follows close behind; it is only by defying it that the brave escape." - Voltaire

Offline

#21 2011-12-01 07:13:17

machinebacon
#! unstable
From: China
Registered: 2009-07-02
Posts: 6,826
Website

Re: HowTo: Upgrade the #! Point Release to sid

@corvo:
i don't think sid removes your wireless (actually, there should be even more adapters be supported), that's why I think it is a simple configuration problem (which may or may not occur in testing, too)
- remove nm *after* downloading wicd (or ceni from the  aptosid repos, warm recommend)
- to solve the slow thunar startup, remove gvfs-backends
- move to testing: i haven't tested it (and most probably never will), however, I am sure it is okay to follow the instructions - BUT: uncomment the security-repos of debian and change to testing, accordingly.

Last edited by machinebacon (2011-12-01 07:14:29)


Sweaty lads picking up the soap | I love the new "Ignore user" button

Offline

#22 2011-12-02 02:44:46

corvo
Member
From: Clovis, California, USA
Registered: 2011-11-29
Posts: 43

Re: HowTo: Upgrade the #! Point Release to sid

All right, so my stubborn nature and eagerness to have a Crunchbang Sid got the better of me. I decided to give this one more shot. This time, however, I approached things differently and first I proceed to:

sudo apt-get purge network-manager* && sudo apt-get install wicd

After performing this, I followed the guide and lo and behold everything worked just perfectly! That smxi script works wonders and is perhaps the greatest script a Crunchbang/Debian user can have at their disposal (if you pay close attention to each step that is)! In short wireless is now working and I yet to have to run into any issues other than the issue with oblogout. But I'll post that issue in the appropriate thread. Thanks machinebacon! Proud Crunchbang Sid user as of 12/1/2011. big_smile


"It is vain for the coward to flee; death follows close behind; it is only by defying it that the brave escape." - Voltaire

Offline

#23 2011-12-02 02:55:13

VastOne
#! Ranger
From: V-Ger
Registered: 2011-04-26
Posts: 10,165
Website

Re: HowTo: Upgrade the #! Point Release to sid

Cool corvo..

smxi is indeed awesome..  I use it for every kernel upgrade and then for all nVidia drivers pkg'd to the new kernel..

Makes life very easy


VSIDO | Words That Build Or Destroy

I dev VSIDO

Offline

#24 2011-12-02 02:57:41

corvo
Member
From: Clovis, California, USA
Registered: 2011-11-29
Posts: 43

Re: HowTo: Upgrade the #! Point Release to sid

Are you using the Debian Sid kernel, VastOne? Or are you using the Aptosid kernel? I wanted to try the Liquorix kernel, but for now I'm using the Debian Sid kernel.

Last edited by corvo (2011-12-02 02:58:08)


"It is vain for the coward to flee; death follows close behind; it is only by defying it that the brave escape." - Voltaire

Offline

Help fund CrunchBang, donate to the project!

#25 2011-12-02 03:03:30

VastOne
#! Ranger
From: V-Ger
Registered: 2011-04-26
Posts: 10,165
Website

Re: HowTo: Upgrade the #! Point Release to sid

I use the latest Liquorix as my main kernel.. I have both aptosid and Debian's latest kernels also and switch between them.. 

I have more success with Liquorix than any, but YMMV ... And I use smxi to install each of these kernels

Last edited by VastOne (2011-12-02 03:03:40)


VSIDO | Words That Build Or Destroy

I dev VSIDO

Offline

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.
Server: acrobat

Debian Logo