Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
* Enable users to continuously track the development focus of Ubuntu without having to explicitly upgrade
For: 3 Against: 0 Abstained: 0
* Enable users to continuously track the development focus of Ubuntu as a "rolling release" rather than having to explicitly upgrade
For: 0 Against: 3 Abstained: 0
I'm not clear on the first bullet point. Does this mean they won't require "apt-get upgrade" on the system just to get one package to update?
Any details on how they'll accomplish that? And what is the middle ground between "more flexibility in package updates" and "rolling release"?
Ubuntu to halve support length for non-LTS releases (The H)
Posted Mar 19, 2013 22:58 UTC (Tue) by tjc (subscriber, #137)
Posted Mar 19, 2013 23:36 UTC (Tue) by dmitrij.ledkov (subscriber, #63320)
The details are fuzzy and pending implementation. It is not quite sure if it means: "without changing sources.list" (example SRU/security updates today) or "packages keep the same name", (example SRU/security updates today) or "additional ppa/archives will need to be added" (example Cloud Archive for new OpenStack releases) or "people will need to installed renamed package" (example quantal kernel/X stack in precise is renamed with -lts-quantal suffix).
Please note that only part of the proposal was debated and voted upon. The Technical Committee will meet again in two weeks to continue the rest of the proposal.
Many implementation details will be then announce by respective teams involved: Release Team, Stable Release Updates team, Security Team, Archive Maintainance Team, QA and etc.
Posted Mar 20, 2013 18:36 UTC (Wed) by geofft (subscriber, #59789)
"upgrade" means update all packages currently installed, as far as possible, but don't install any new ones.
"dist-upgrade" means update all packages currently installed, but be willing to install new ones.
It just so happened that "upgrade" was the first thing implemented in apt, and when people needed to upgrade between releases, they realized that "apt-get upgrade" wasn't going to work because new releases brought in new dependencies. In practice, nobody had been adding dependencies within a Debian stable release. But as it turns out, adding dependencies is actually a useful thing to be able to do within stable releases, so in general the current recommendation is to use "dist-upgrade" regardless and forget that "upgrade" exists. (aptitude calls it "full-upgrade" for this exact reason.)
The process of upgrading between distro releases, on Ubuntu at least, is preferably done with do-release-upgrade, not any apt-get command (although I've done it with apt-get dist-upgrade and been fine). Certainly apt-get dist-upgrade doesn't _change_ what release you're on, so you need to do that manually.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds