You are not logged in.
Due to the latest sad news of Crunchbang being discontinued I thought about reverting to Debian Stable.
Yes, the title may sound lame but I want to be sure not to make a stupid mistake (I use *buntu on regular basis).
I searched Google for "Debian wheezy default repositories" or "Debian stable default repositories" but no ready to copy-paste list found.
Mu current sources.list
## CRUNCHBANG
## Compatible with Debian Wheezy, but use at your own risk.
deb http://packages.crunchbang.org/waldorf waldorf main
# deb-src http://packages.crunchbang.org/waldorf waldorf main
## DEBIAN
deb http://http.debian.net/debian wheezy main contrib non-free
# deb-src http://http.debian.net/debian wheezy main contrib non-free
## DEBIAN SECURITY
deb http://security.debian.org/ wheezy/updates main
# deb-src http://security.debian.org/ wheezy/updates main
# w,heezy-backports
deb http://http.debian.net/debian/ wheezy-backports main contrib non-free
deb http://http.us.debian.org/debian/ wheezy contrib mainI'd like to have contrib and non-free enabled also.
And what difference is between those two?:
deb http://http.debian.net/debian wheezy main contrib non-free
deb http://http.us.debian.org/debian/ wheezy contrib mainSeem the same to me except one have non-free enabled.
Last edited by Zoidberg (2015-02-06 18:09:33)
Offline
just disable
# deb http://packages.crunchbang.org/waldorf waldorf mainand move /etc/apt/preferences away, or edit accordingly.
Online
I haven't even thought about preferences.
I had:
Package: *
Pin: release a=waldorf
Pin-Priority: 1001
Package: *
Pin: release a=wheezy
Pin-Priority: 500And changed it to
Package: *
Pin: release a=wheezy
Pin-Priority: 1001
Package: *
Pin: release a=wheezy-backports
Pin-Priority: 500Thanks for help!
Offline
Wheezy should be under 1000 (Not that I know how backports are behaving in this game, i'd remove them).
some reading https://wiki.debian.org/AptPreferences
Online
Thanks for pointing this out. Luckily I haven't run apt-get update yet, making all the changes on Crunchbang's partition from my Xubuntu. However it wouldn't be much of a tragedy if I did. I've made a backup yesterday.
I've found this http://serverfault.com/questions/22414/ … om-testing
And now my sources list looks like so (decided to add testing, so I can use apt-get -t testing install if needed):
#security.list:
deb http://security.debian.org/ stable/updates main contrib non-free
deb http://security.debian.org/ testing/updates main contrib non-free
#stable.list:
deb http://mirror.steadfast.net/debian/ stable main contrib non-free
#deb-src http://mirror.steadfast.net/debian/ stable main contrib non-free
deb http://ftp.us.debian.org/debian/ stable main contrib non-free
#deb-src http://ftp.us.debian.org/debian/ stable main contrib non-free
deb http://mirror.steadfast.net/debian/ testing main contrib non-free
#deb-src http://mirror.steadfast.net/debian/ testing main contrib non-free
deb http://ftp.us.debian.org/debian/ testing main contrib non-free
#deb-src http://ftp.us.debian.org/debian/ testing main contrib non-freeAnd preferences looks like this:
Package: *
Pin: release l=Debian-Security
Pin-Priority: 1000
Package: *
Pin: release a=stable
Pin-Priority: 995
Package: *
Pin: release a=testing
Pin-Priority: 750Offline
^ Debian considers it a generally bad idea to mix stable and testing on the same install; that's why they have the backports and updates repos.
As bronto suggested, I'd just remove /etc/apt/preferences so that backports would be pinned low and switch back to wheezy and wheezy-backports. Also, it's typically redundant to have multiple repos in /etc/apt/sources.list for the same stream (e.g. you currently have two mirrors listed for stable). Here's what I would recommend if you want to stick with wheezy once jessie goes stable:
#security.list:
deb http://security.debian.org/ wheezy/updates main contrib non-free
#stable.list:
deb http://ftp.us.debian.org/debian/ wheezy main contrib non-free
#deb-src http://ftp.us.debian.org/debian/ wheezy main contrib non-free
deb http://ftp.us.debian.org/debian/ wheezy-backports main contrib non-free
#deb-src http://ftp.us.debian.org/debian/ wheezy-backports main contrib non-free(Backports is automatically pinned at 100 by its Release Files, see here. Leaving it pinned that low is generally considered the safest way to use it with stable.)
Offline
Ok. I'll stick to the sources.list you suggested. And removing preferences.
Offline
@pvsage: Thank you for that repo list update. I'm now running solid Wheezy stable; the dist-upgrade was minor (with a forced update of tint2) and I'm set. 
Offline
Oh, yes...Tint2. The easier way would have been to purge tint2 and tint2conf first, then reinstall tint2. The version of tint2 that comes with Waldorf was one of the handful of packages that corenominal built from a git-pull, and the functionality of tint2conf has since been added to the main tint2 package. That's why there was a problem updating it.
Offline
Why would one need to remove the waldorf depo? Is it a better strategy? Would there any potential issue if I keep it unchanged?
Offline
Why would one need to remove the waldorf depo? Is it a better strategy? Would there any potential issue if I keep it unchanged?
You would have to stay with wheezy, and won't be able to dist-upgrade to jessie.
Artwork at deviantArt; Iceweasel Personas; SLiM #! Themes; Openbox themes
Online
Why would one need to remove the waldorf depo? Is it a better strategy? Would there any potential issue if I keep it unchanged?
It's a good idea to remove the Waldorf repo at this point whether you plan to migrate to Jessie or stay with Wheezy/Waldorf. Several of the binaries in Waldorf were newer builds when Waldorf was released, but have been superseded by versions in Wheezy. At the absolute least, Waldorf's pinning should be reduced to 500 or less, and preferably lower than Wheezy's.
Expect to have to purge tint2 and tint2conf and reinstall tint2; the separate tint2conf causes a versioning conflict that gives APT a headache.
Offline
Thanks damo and pvsage.
Gone through the steps just now. Only that whenever I check on "Restart tint2" in menu, it gives me this message: (Openbox) Failed to execute child process "tint2restart" (No such file or directory)". Is it possible to fix it?
Offline
Thanks damo and pvsage.
Gone through the steps just now. Only that whenever I check on "Restart tint2" in menu, it gives me this message: (Openbox) Failed to execute child process "tint2restart" (No such file or directory)". Is it possible to fix it?
Does tint2 start OK if you just use the command?
tint2 &tint2restart is just a simple bash script. Make sure you have it:
which tint2restartIf it is missing, then create it and make it executable
#!/bin/bash
# ----------
# Simple script to restart tint2
if [ "$(pidof tint2)" ]; then
killall tint2 && sleep 1s && tint2 &
exit 0
else
tint2 &
exit 0
fiArtwork at deviantArt; Iceweasel Personas; SLiM #! Themes; Openbox themes
Online
Does tint2 start OK if you just use the command?
tint2 &
Yes, tint2 can start normally.
Offline
So there you go then. Restart it manually, or check the script is OK.
Artwork at deviantArt; Iceweasel Personas; SLiM #! Themes; Openbox themes
Online
where do i find the file to edit tint2 restart?
Offline
where do i find the file to edit tint2 restart?
I already told you. If it is an executable script, the path will be shown by
which tint2restartYou can also use "whereis", "find", "locate" etc etc to find files on a linux system.
Last edited by damo (2015-02-10 10:41:56)
Artwork at deviantArt; Iceweasel Personas; SLiM #! Themes; Openbox themes
Online
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.