You are not logged in.
@loco:
A look into the future: if you'll run Waldorf, you can change the sources from testing to stable or simply from testing to wheezy - but remember that the apt-preferences should have exactly the same entry (so if you use "wheezy" in the sources.list, you need to use "wheezy" in apt-preferences, too)
Offline
I started with #! 8.04 and fresh install of the new version is what I've seen work.
I like to keep a separate /home partition and change my username to "snowpineold" before installing the new version, so I get a new user account with the new settings of the new release and then can copy other files over at my leisure.
Last edited by snowpine (2012-06-13 11:34:27)
/hugged
Offline
Welcome back, Baconator! You weren't gone long, but you were missed. I'm sure that, just as was the case with Wheezy, many people's favorite nonfree packages will disappear from Waldorf during the freeze shakedown (glares at the Debian guy who cut Minitube from Squeeze
). Probably be even more fundamental changes too...xorg is still a bubbling cauldron of confusion...
I'm sorry if I wasn't clear in the opening post, but certainly *right now* is far too soon to expect anything in Waldorf to be set in stone; I was just "think[ing] about the future" when Wheezy does become Stable.
@elvaqueroloco: I'm pretty sure that, just as was the case with Statler, the Testing images of Waldorf reference Wheezy in /etc/apt/sources.list; therefore, it should automatically track the Testing-to-Stable transition.
@omns: Since you probably have more experience with Debian than everyone else "in the room" *combined*, I'm siding with elvaqueroloco and deferring to your knowledge.
@VastOne & pidsley: Great points; yes, the Statler-to-Waldorf layer on top of the Debian Stable-to-Stable transition does further complicate issues.
while ( ! ( succeed = try() ) );
We've earned a reputation as a nice, friendly community; please help us keep it that way.
Offline
More good discussion. I was planning to try an upgrade by modifying sources this morning, and I think I will also try using a separate home partition (I like snowpine's new user method).
For more discussion, here are the questions I'd like to be able to answer, and some proposals (just proposals!):
1. I am a new user, and I have not installed #! -- which version (of the three available) should I install?
A. Waldorf. While it is labeled as a "testing" release, it is already stable enough for general use. Because we know you are going to want to "upgrade" to this release eventually, we'd recommend just starting with it. If you have any problems during or after the install, please ask on the forum -- we'll be happy to help and you will be helping us make Waldorf even better.
2. I installed Statler (stable or backports) a few days ago and now I think I want Waldorf. Can you tell me how to upgrade?
A. Unless you have made a lot of configuration changes after you installed Statler, the easiest way to upgrade is to simply reinstall using Waldorf. If you have made many changes after installing, please see question 3.
3. I've been using Statler since the February release, and I have all my configuration files just the way I want them. Please tell me how to upgrade to Waldorf without losing all my hard work.
A. Please see (this not yet written guide) for instructions on how to use a separate home partition and creating a new user to install Waldorf and migrate your configuration files.
4. Can't I just upgrade by changing my sources.list?
A. While it is possible to upgrade most of your software using this method, there are other fundamental changes in Waldorf that would need to be made manually for a full upgrade. Re-installing with a separate home partition is really much easier.
Last edited by pidsley (2012-06-13 12:52:08)
Want Waldorf, but with sid and systemd? Try Darkside.
Offline
@pidsley you're essentially answering all those questions the same way and already have the answers you need.
'A fresh install rather than an upgrade would be the best way to install Waldorf.'
imo 
Offline
Offline
Well there's no real same page or official recommendation. That comes later from corenominal 
Offline
@pidsley, when asked about these types of things I just give my personal opinion. Others will do the same if they agree.
Your reasoning and proposed responses seem okay to me but I'd express caution over recommending Waldorf over Statler. Some people prefer rock solid and it needs to be made clear that Waldorf is in development and despite being very stable already, will have bugs from time to time.
Offline
...and some idiots might be tempted to throw out the *one kernel* that works with their wifi, then have to spend three hours building the kernel headers because they aren't available upstream...
...but not blaming anybody but myself for that one.
while ( ! ( succeed = try() ) );
We've earned a reputation as a nice, friendly community; please help us keep it that way.
Offline
Your reasoning and proposed responses seem okay to me but I'd express caution over recommending Waldorf over Statler. Some people prefer rock solid and it needs to be made clear that Waldorf is in development and despite being very stable already, will have bugs from time to time.
Don't worry; I won't be recommending mass conversion to Waldorf. I'll defer to the mods and corenominal. 
Last edited by pidsley (2012-06-13 19:16:18)
Want Waldorf, but with sid and systemd? Try Darkside.
Offline
@VastOne: As I said in that thread, it was just a waiting game; I guess three hours isn't too big a price to pay for such valuable experience. (Especially at what my employer pays per hour.) Besides...
while ( ! ( succeed = try() ) );
We've earned a reputation as a nice, friendly community; please help us keep it that way.
Offline
^ You have no idea how many times I've quoted that title, especially to Megan. 
while ( ! ( succeed = try() ) );
We've earned a reputation as a nice, friendly community; please help us keep it that way.
Offline
Well, I tried an upgrade this morning by starting with a clean Statler bpo install and modifying the sources.list. The dist-upgrade downloaded 753 MB of new stuff (that's right, larger than a Waldorf iso) and took more than two hours to complete (I have a slow DSL connection, but even after the download it took 30-45 minutes, with one -f episode). And I was left with what I can only call "Statdorf" or "Waldtler" -- a mixed bag of working and not working software; some themes were broken, wireless was broken, and who knows what else. The upgrade "worked" -- at least it didn't fail, but I can't really recommend it...
Last edited by pidsley (2012-06-14 00:41:22)
Want Waldorf, but with sid and systemd? Try Darkside.
Offline
^I love the smell of a fresh install in the morning 
#!, all else is but a shadow!
ENOUGH;)
Offline
I thinl, there is better way to make #! rolling-release distributive.
Offline
I always do a clean install but save certain rc's,conf's etc on a usb key for reference, so far loaded statler 32bit,
just went from waldorf 32bit 405img to 64bit 806img using usb install and havent had any non-configurable problems yet. I will say gnome-mplayer surprises me with video rendering superior to vlc, especially with me being obsessed with vintage music video like older pink floyd concert footage. Anyways, Debian is def the way to go and very capable if not already superior to the "buntu" anything! My biggest install problem is remembering how to erase the read only files on the usb to load the next image !! 
Offline
Surely, instead of being drastic and performing a fresh install, one could merely edit the sources.list and apt-preferences, dist-upgrade and then create a new user account. That way, any new config changes and defaults will be generated in the new user account. Once that is all sorted and things are backed up, delete the original account and recreate it again – if you want the username back + new configs and defaults.
Last edited by elb0wf4ce (2012-11-01 16:27:56)
If it ain't broke, try harder.
Offline
Not sure this would work. For one thing, there are enough differences between Statler and Waldorf for the contents of /etc/skel to cause borkage, and I'm pretty sure what you describe won't replace that. Probably a host of other "gotchas" as well.
while ( ! ( succeed = try() ) );
We've earned a reputation as a nice, friendly community; please help us keep it that way.
Offline
Not sure this would work. For one thing, there are enough differences between Statler and Waldorf for the contents of /etc/skel to cause borkage, and I'm pretty sure what you describe won't replace that. Probably a host of other "gotchas" as well.
Wouldn't the contents of /etc/skel be overwritten by the newer versions with their new defaults? There's always alternatives to a fresh install, I find. It beats having to reinstall various different apps and hefty games.
If it ain't broke, try harder.
Offline
Pretty sure /etc/skel/ is copied from the live media during install, and not affected by anything in the repos...
while ( ! ( succeed = try() ) );
We've earned a reputation as a nice, friendly community; please help us keep it that way.
Offline
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.