On Sun, 2009-11-01 at 13:03 +1100, Amos Shapira wrote:
> That's generally what I'd expect, based on my experience with Debian > and CentOS, and why I tried to stick to it - I usually don't care > about having latest versions (as long as the current one does the job) > and I don't have too much spare time to mess with upgrades unless I > absolutely must. > > But when a bug was fixed in a later release it was NOT back-ported to > the LTS release - so what does "LTS" stand for? "Local Transport > Strategy"? (http://www.clacksweb.org.uk/property/developmentplan/glossary/), > "Leaning Toothpick Syndrome"? "Low-Temperature Superconductor"? > (http://en.wikipedia.org/wiki/LTS) https://wiki.ubuntu.com/LTS To get the LTS updated a 'stable release update' is needed - SRU: https://wiki.ubuntu.com/StableReleaseUpdates. When an individual fix is backported its called an SRU - see below for 'backports', which is a whole other thing. > > - backports are available if you want newer packages on a per package > > basis. > > "Backporting", in the definitions I'm familiar with (e.g. RHEL), is to > fix an OLDER version which is current in a supported release, not an > upgrade to a later version of the software. In Debian/Ubuntu 'backports' (NOT BackportING) is a collection of newer packages built as much as possible against an older release. https://help.ubuntu.com/community/UbuntuBackports -Rob
signature.asc
Description: This is a digitally signed message part
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
