If you install from the new image and follow @el K's advice you should not experience future problems.

Thanks for that ivanovnegro.

ps.  If it all goes wrong who do I ask for my money back.

There shouldn't be. I'm not sure how mmmuch damage was done if a complete upgrade was done to the backports versions of all the installed packages, but it shouldn't present a problem. Thank god for

apt-get dist-upgrade --simulate

I must admit that I have never used the --simulate option.

Thanks for the top-tip.

So, if I subsequently pin squeeze to 500 as suggested by el_koraco in post #471 above, will there be any problems when updating/upgrading #! in the usual way?

If you install from the new image and follow @el K's advice you should not experience future problems.

So, if I subsequently pin squeeze to 500 as suggested by el_koraco in post #471 above, will there be any problems when updating/upgrading #! in the usual way?

There shouldn't be. I'm not sure how mmmuch damage was done if a complete upgrade was done to the backports versions of all the installed packages, but it shouldn't present a problem. Thank god for

apt-get dist-upgrade --simulate

Zill wrote:

However, I am concerned that the version of a package initially installed may then be later than the "stable" squeeze version.

That is also correct. Look at the kernel and Openbox, these things are now newer.

So, if I subsequently pin squeeze to 500 as suggested by el_koraco in post #471 above, will there be any problems when updating/upgrading #! in the usual way?

However, I am concerned that the version of a package initially installed may then be later than the "stable" squeeze version.

That is also correct. Look at the kernel and Openbox, these things are now newer.

SabreWolfy wrote:

[n00b]
What's wrong with backports?
[/n00b]

It's not part of the "official" stable repository. It mostly stuff from wheezy and sid that "mostly works" with squeeze and thus problems can occur. It is advised to use backports selectively to get a later version of this or that, but not to have them enabled all the time.

In regular Debian, enabling backports doesn't equate to everything updating to the backports version. #! has its own weird apt policy configuration there, problems can be avoided thus: http://crunchbanglinux.org/forums/topic … eferences/

[n00b]
What's wrong with backports?
[/n00b]

It's not part of the "official" stable repository. It mostly stuff from wheezy and sid that "mostly works" with squeeze and thus problems can occur. It is advised to use backports selectively to get a later version of this or that, but not to have them enabled all the time.

I don't like enabled backports either, but couldn't you disable them via synaptic or comment them out in sources.list? I mean, if you really want to try it this shouldn't a reason to stop you.

Yes, they could be disabled following installation of #!.  However, I am concerned that the version of a package initially installed may then be later than the "stable" squeeze version.  As I am not sure as to whether this will cause any problems later when updating the system I prefer not to have backports enabled from the outset.

Having said that, I intend to upgrade a different desktop PC in the medium term and would like to use a new release of CrunchBang then.  I just hope that, by then, there will be a "stable" version without backports enabled.

I may be in the market for a new Dell soon, I'm sure that will come with Windows 7 so I'll give it a try.

To bring this back on topic to the updated statler images, I have an old Dell laptop, 600mhz pentium 3 with 384mb ram, smoothly running the feb 2011 statler image with the ratpoison windows manager, do you think that would be a good candidate for the new release and if so why?

Personally I wouldn't update a system that's happily running the February #! release to the latest one, although I'd use the latest image for any new installs. The new Openbox setup is nice, but it's not the kind of thing that would make me update a perfectly good system. And there are some issues with the new release that will be worked out in the future, so this is one of those moments where I would wait a little bit.