If Squeeze does not pull new patches or security updates

ivanovnegro · 2012-03-01 00:28:13

We had many discussions about the pin preferences of Squeeze, backports and Statler, also there are the #! Multimedia and Mozilla repos.

I have a suggestion for all people that encounter problems from time to time with the newest unbackported images as with the backported ones and also with all older releases.

This is for people that want to stay on a more Debian like approach with all CrunchBang 10 Statler systems.

Maybe my effort will find its way in newer releases to make CrunchBang even better and better.

Yes, I know, I am a purist and use exclusively Debian and many things come from that point of view but I think my suggestions are viable. If you do not like them, ignore me, if yes, discuss on the issues. smile The devil is in the details, some people often say.

Ok, let's begin.

First:

Change the pin priority of Squeeze to 500 and the priority of Statler also to 500:

<your editor of choice> /etc/apt/preferences

Save and close.

This should assure that you recieve all maintenance and security updates from Debian for Squeeze in timely manner whereas Statler blocks all updates because of the higher pin priority and because it seems Statler does not recieve any updates on some packages, at least at the moment.
Additionally this will assure that activated backports only come in when the user itself wants them and not automatically.

Now we proceed

Remove the #! Multimedia and #! Mozilla repo.

If you want the newest Iceweasel, take the Debian Mozilla repo from here: http://mozilla.debian.net/, that means you would need to activate the Debian backports anyway. But this way you would recieve always the newest version from the Debian guys whereas Statler did not pull yet any updates. If you have already backports activated, remove just all #! repos related to backports.

For the Debian backports you need this entry in your sources list:

deb http://backports.debian.org/debian-backports squeeze-backports main

or with non-free packages

deb http://backports.debian.org/debian-backports squeeze-backports main contrib non-free

To make it happen:

<editor of choice> /etc/apt/sources.list

Change it like above, save and close. Then proceed with the Mozilla instruction from their page I posted above.

The same goes with the multimedia packages, take the repo from Debian to assure updates.
Go to this site and grab the repo, follow the instructions.

With this little workaround you will assure total Debian Squeeze compatibility and still use all #! related stuff.

If you do not follow my workaround, no problem, everything will work just fine, no explosions, no damages but Iceweasel was recently not updated to 10.0.2, I guess some packages of Squeeze will not recieve security updates, I think @CBizGreat covered that. Also look at this thread. And if you use the #! images without backports you will have issues like @safetycopy had because of the backported Iceweasel version by Statler, look here.

See also @el K's advice: http://crunchbanglinux.org/forums/topic … ferences/.

PS: If you are happy with all automatic backports then do not follow this guide but I would change the Squeeze priority to 500.

Last edited by ivanovnegro (2012-03-26 16:21:46)

CBizgreat! · 2012-03-01 08:40:12

Nice how to Ivan ... Yep, hopefully this lil repo's quirk gets quashed, it's annoying even if people have a buncha ways to quickly fix it. Think it would help make #! even more kickbutt than it already iz. wink

johnraff · 2012-03-12 16:58:35

Thanks Ivan - this is exactly what I want.
One question: what about /etc/apt/apt.conf
Should we change the DefaultRelease, currently

APT::Default-Release "statler";

and if so, to what?

ivanovnegro · 2012-03-12 17:10:58

Good question, I forgot to think about this.
But I would then decide to make Squeeze the default release and not Statler. With a pin preference of both, Statler and Squeeze, to 500 they would be handled equally by the package manager. I ran it that way on my Stable system without problems. Of course in my case it was a crunchified Debian anyway.
But maybe it is even posssible to just leave Statler as the default release.

CrunchBang Linux

SEARCH

#1 2012-03-01 00:28:13

If Squeeze does not pull new patches or security updates

#2 2012-03-01 08:40:12

Re: If Squeeze does not pull new patches or security updates

#3 2012-03-12 16:58:35

Re: If Squeeze does not pull new patches or security updates

#4 2012-03-12 17:10:58

Re: If Squeeze does not pull new patches or security updates

Board footer