• Registered: 2011-07-27
  • Posts: 499

Topic: Question about Statler repo in #! stable.

Was trying to post a how to update adobe flashplayer thread ... in tips, tricks etc. Thought of something that's bugging me and would like to ask about this. The following is the book of an afterthought I had about commenting out the statler repos in sources.list. Lol ... the afterthoughts were starting to take up more room than the how to. tongue


PS, not so fast ... sighs. Felt need to babble a bit more. The implications of commenting out the statler repo in sources.list is something to keep in mind. Think by default synaptic ... apt etc will try to install the latest package available in the repos. Obviously fiddling around with sources.list can lead to borkage. Am not sure and wondering, what the impact might be in commenting out the statler repos, then doing a dist-upgrade would be. I've done so once and had no problems with this install. I mean have dist-upgrade 'd once with the statler repos left commented out. Actually left mine that way for whatever reason. All the repos by default are gonna be Debian stable anyway am sure.

Does make me wonder what would happen if someone temporarily comments out the statler repos, later puts it back the way it was originally and does a dist-upgrade on their system. Would the pin-priority involved pull and replace some of the packages someone had installed from the statler repos, or would the highest version installed still win out? Am not a big fan of doing dist-upgrades myself. Tend to update/upgrade the stuff I want and stay away from dist-upgrades. If someone more knowledgeable on the topic would like to clarify ... great.

Otherwise, just trying to avoid inadvertently causing others da dreaded borkage. Giving a heads up about something that occurred. Mentioned notice I HAD to comment out the statler repos to get newer software packages to install at times. The tug of war between the statler repo and others, is a wee bit annoying me thinks. Though no doubt Corenominal had good reasons for it.


So guess the question is, would temp commenting out the statler repo's, switching them back the way they are and doing dist-upgrades along the way bork someone's #! install ... or no ? Statlers repos in this version of #! get a pin-priority of 1001 according to /etc/apt/preferences . Though have noticed I've needed ( well chose) to comment that repo out to get newer software to install.

Guess there's always stuff like ...

buntu stuff about apt
Debian apt preferences
Random stuff about apt-pinning


Just don't want to inadvertently cause people headaches and borkage advising them to comment out the statler repo as an easy solution kinda thing. So looks like I didn't HAVE to comment out the statler repo, are other ways and is just the way I went about it, shrugs.



vll !

Last edited by CBizgreat! (2012-01-27 19:39:07)

  • From: de la red
  • Registered: 2011-06-02
  • Posts: 2,530

Re: Question about Statler repo in #! stable.

If you comment out the Statler repo, nothing would happen, you are just on Debian Stable, you will only miss future updates made by @corenominal to the CrunchBang repo.

Why you could not get updates of new software, not sure, the whole apt preferences in #! are a bit strange. I suppose because the preference for Squeeze is too small. Look at this thread: http://crunchbanglinux.org/forums/topic … eferences/.

If it is true that you cannot get updates from Debian Stable (Squeeze) tehn the decision with the actual apt preferences is even worse than I thought. I would change the preference for Squeeze to 500 and for Statler also to 500 and backports back to 100.

Quick reference | The ultimate MPD guide

The sound of #! COFFEE
  • Registered: 2011-07-27
  • Posts: 499

Re: Question about Statler repo in #! stable.

Thanks for the clarification Ivan,

Was afraid of that. Have posted more than once telling people to comment out the statler repo to upgrade to something. It's how I did it, for something like adding the iceweasel release backport. If ya leave the sources.list the way it is. Nope ... complaining about missing dependencies blahblahblah. Comment out the statler repo ... Installs no prob. Same thing for apt-get adobe flashplayer, El_koraco told me how at one time. Tried it, looked like it was working ... nope. Comment out statler repos, goes through no prob, shrugs.


Was just worried about telling folks to comment it out temp to do stuff. Then wondering if the next time they did a dist-upgrade ... The packages they have installed/need would get replaced by stuff in the statler repo or ... Thus maybe borking them. Oh well ... agree with Ivan. Many ways to skin cats ... blahblahblah. Changing pin-priority and preferences sounds like a good-better way to go about it.


vll !

Last edited by CBizgreat! (2012-01-27 22:39:43)