Originally posted by SteveRiley
View Post
Announcement
Collapse
No announcement yet.
Why Upgrade? Getting tired...
Collapse
This topic is closed.
X
X
-
Originally posted by SteveRiley View PostMy read of Kubicle's suggestion is that you can always stay "rolling" by having only the single repo line for whatever the current development pocket is. Right now, that's:
Code:deb http://archive.ubuntu.com/ubuntu/ saucy main restricted universe multiverse
Code:deb http://archive.ubuntu.com/ubuntu/ saucy-proposed main restricted universe multiverse
In this interesting rolling model, you would actually not make any changes to your /etc/apt/sources.list until development opens for the next version. Once that happens, you will change the word saucy to whatever the name is for the next version and then perform a dist-upgrade.
This is a fascinating concept, one which I plan to try myself.
Do I have the concept down correctly?Windows no longer obstructs my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock Holmes
- Top
- Bottom
Comment
-
Pan-Galactic QuordlepleenSo Long, and Thanks for All the Fish
- Jul 2011
- 9524
- Seattle, WA, USA
- Send PM
Originally posted by Snowhog View PostOkay. So, now, I have raring repos. I 'add' the one (or two) saucy repos and continue as "I" do, with regular dist-upgrades.
You should continue your daily dist-upgrades as this will keep your machine fresh.
Originally posted by Snowhog View PostAt the time that saucy is released as 'final' -- no longer a release candidate -- I would change the one (or two) saucy repos to the next release code-name, and change my existing raring repos to saucy.
- Top
- Bottom
Comment
-
Okay. I'm gonna do it! (If you never hear from me again, please, remember me occasionally with fondness! )Windows no longer obstructs my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock Holmes
- Top
- Bottom
Comment
-
Pan-Galactic QuordlepleenSo Long, and Thanks for All the Fish
- Jul 2011
- 9524
- Seattle, WA, USA
- Send PM
I'm gonna try the same thing in a VM, starting with Precise. Then to Quantal, Raring, and Saucy. Will report back here when I'm done.
- Top
- Bottom
Comment
-
The button has been pushed! I hope that I don't end up tearing a hole in the fabric of the Universe!!Windows no longer obstructs my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock Holmes
- Top
- Bottom
Comment
-
Pan-Galactic QuordlepleenSo Long, and Thanks for All the Fish
- Jul 2011
- 9524
- Seattle, WA, USA
- Send PM
So far...
* Installed Precise into VirtualBox VM
* Modified /etc/apt/sources.list to be:
Code:deb http://us.archive.ubuntu.com/ubuntu/ quantal main restricted universe multiverse deb-src http://us.archive.ubuntu.com/ubuntu/ quantal main restricted universe multiverse deb http://archive.canonical.com/ubuntu quantal partner deb-src http://archive.canonical.com/ubuntu quantal partner deb http://extras.ubuntu.com/ubuntu quantal main deb-src http://extras.ubuntu.com/ubuntu quantal main
* The installation successfully upgraded from Precise to Quantal. I am now performing the Quantal-to-Raring upgrade.
- Top
- Bottom
Comment
-
Originally posted by SteveRiley View PostYour question implies that you might not truly understand what we're discussing
- Top
- Bottom
Comment
-
Pan-Galactic QuordlepleenSo Long, and Thanks for All the Fish
- Jul 2011
- 9524
- Seattle, WA, USA
- Send PM
Originally posted by kubicle View PostHaving ubuntu set up a "devel" pointer to the current development version would remove the need to edit the repo when a version is released
http://archive.ubuntu.com/ubuntu/dists/devel/
http://archive.ubuntu.com/ubuntu/dists/devel-proposed/
- Top
- Bottom
Comment
-
Pan-Galactic QuordlepleenSo Long, and Thanks for All the Fish
- Jul 2011
- 9524
- Seattle, WA, USA
- Send PM
Well, the experiment worked. My VM is now at Saucy. I had to dist-upgrade a second time once the Saucy upgrade finished, because APT's solver couldn't figure out how to handle an Amarok-related dependency during the Raring-to-Saucy conversion. The printer applet crashes on boot-up, and certain windows have an odd appearance -- I attribute the appearance issue to running in a VM.
Time to add saucy-proposed to see what might break, haha.
- Top
- Bottom
Comment
-
Umm, excuse me for being a little green/dumb, first I should mention I've never ran a VM, so I wouldn't know if you can 'virtually reboot' it or not, why I am saying this is because some upgrades require a reboot, just a curious onlooker (your experiment has now become a spectator sport, lol).
- Top
- Bottom
Comment
-
Pan-Galactic QuordlepleenSo Long, and Thanks for All the Fish
- Jul 2011
- 9524
- Seattle, WA, USA
- Send PM
- Top
- Bottom
Comment
-
Pan-Galactic QuordlepleenSo Long, and Thanks for All the Fish
- Jul 2011
- 9524
- Seattle, WA, USA
- Send PM
Re-applying the Air desktop theme fixed the unusual appearance.
Iterating through apt-get --purge autoremove and apt-get purge $(deborphan) until both had nothing left to do fixed the printer applet problem. There were some left-over Python bits from earlier releases that apparently caused the applet to get confused.
- Top
- Bottom
Comment
-
Originally posted by tek_heretik View PostUmm, excuse me for being a little green/dumb, first I should mention I've never ran a VM, so I wouldn't know if you can 'virtually reboot' it or not, why I am saying this is because some upgrades require a reboot, just a curious onlooker (your experiment has now become a spectator sport, lol).
Here is a fresh install of a raring guest inside my precise host.
sigpic
- Top
- Bottom
Comment
Comment