SECTION ONE - DEBIAN AND LINUX MINT DEBIAN EDITION
1) -Debian has three releases at any given time: 1.a) - stable currently debian 7.0 codenamed Wheezy, released in 04/may/2013 ( and with a new release every two years );
because of this long release cycle the pkgs in stable can and will be quickly outdated, but stable is the most solid O.S. you can have installed:
Understand that the job of Debian is, and always has been, to produce Stable. The other releases are means to that end. You may find the other releases perfectly usable for whatever use you have for them. Great. That wouldn't be much of a surprise to any longtime Debian user. Many users, including (of course) Debian Developers use them routinely.
3.1.3 The stable distributions really contains outdated packages. Just look at Kde, Gnome, Xorg or even the kernel. They are very old. Why is it so?
Well, you might be correct. The age of the packages at stable depends on when the last release was made. Since there is typically over 1 year between releases you might find that stable contains old versions of packages. However, they have been tested in and out. One can confidently say that the packages do not have any known severe bugs, security holes etc., in them. The packages in stable integrate seamlessly with other stable packages. These characteristics are very important for production servers which have to work 24 hours a day, 7 days a week.
On the other hand, packages in testing or unstable can have hidden bugs, security holes etc., Moreover, some packages in testing and unstable might not be working as intended. Usually people working on a single desktop prefer having the latest and most modern set of packages. Unstable is the solution for this group of people.
As you can see, stability and novelty are two opposing ends of the spectrum. If stability is required: install stable distribution. If you want to work with the latest packages, then install unstable.
If security or stability are at all important for you: install stable. period. This is the most preferred way.
- - to solve the quick aging of stable you can use backports
Backports are recompiled packages from testing (mostly) and unstable (in a few cases only, e.g. security updates) in a stable environment so that they will run without new libraries (whenever it is possible) on a Debian stable distribution. It is recommended to select single backports which fit your needs, and not to use all available backports.
1.b) - testing (upon which LMDE is based) is where debian tests and builds the next stable release
The "testing" distribution is an automatically generated distribution. It is generated from the "unstable" distribution by a set of scripts which attempt to move over packages which are reasonably likely to lack release-critical bugs. They do so in a way that ensures that dependencies of other packages in testing are always satisfiable.
- testing is the development branch from where the next stable release will come;
- as so, it's also known by the codename of the next stable release Jessie (what will become debian 8 )
- testing is not a fully rolling release: it rolls for about one and a half year until the deep freeze,
- this means that at a given time debian decides to freeze their development branch and for about 6 months concentrate in squashing bugs, so that the new stable release would be as solid as possible;
- when LMDE came out (in september 2010) testing was in deepfreeze preparing debian 6, the same will happen from November/2014 until April (more or less)/2015 when debian 8 is due
- We will freeze at 23:59 UTC on the 5th of November 2014, and we will run one automated migration at that time.
- testing is not about bleeding-edge software (the apps can be fairly updated but hardly will be the latest&greatest)
- - due to it's unpredictable nature, there's a few good practices to keep when running a sid-based system:
The most important thing is to keep in mind that you are participating in the development of Debian when you are tracking testing or unstable. This means that you should know your way around Linux, Debian and the Debian packaging system and that you should have an interest in tracking down and fixing bugs. There are a couple of things you can do in order to ease your life as a sid user such as:
Always be careful when you perform updates and check if the actions proposed by the package managing tools are in line with your wishes and expectations. (i.e. make sure that you do not remove a plethora of packages you need by blindly accepting the proposed action)
Install the apt-listbugs and apt-listchanges packages in order to be made aware of grave bugs or important changes when you install new packages or during an upgrade.
Keep a good live CD/USB such as Debian Live around at all times so you can still work on the system even if it is not booting anymore.
Automatically create daily, weekly and monthly backups in order to ensure that corrupted data is not a problem.
- apt-listbugs is a tool that might make your life easier if you are running sid (it's also handy in testing of course) youtube tutorial here
1.c.1) - experimental is not a standalone release. If you want to use packages from experimental you first have to install 'Sid' and then add the 'Experimental' line to your repo and then upgrade" (but with extra care, if sid can break, experimental will break for sure)apt-listbugs is a tool which retrieves bug reports from the Debian Bug Tracking System and lists them. Especially, it is intended to be invoked before each upgrade/installation by apt in order to check whether the upgrade/installation is safe.
- if you like experimenting, learning and can afford a breakage now and then (with the consequent downtime it brings) sid is a great schoolUsers shouldn't be using packages from here, because they can be dangerous and harmful even for the most experienced people."
You have been warned
- - this was/is for many users the real LMDE; the one that is closer (in direct sync) with testing.
- when debian 6 was released and the new cycle began things became interesting and in order to cope with possible breakages we organized this thread
- if i may a personal opinion, lmde is a great linux school, the only reason i'm still using a gtk-based distro (ZeroZero);
- - in july 2011 the Mint Team decided to introduce the notion of UP in LMDE.
- basically the question was: the way lmde was structured until then (pointing directly at testing) was making life hard for the less experienced users, so the Mint Team decided to mirror the debian testing repos and release point-updates with "stable" and documented packs.By changing your APT sources and replacing Debian Testing with the Linux Mint Debian Latest repository, you basically point to a Debian Testing that is frozen in time and updated once a month. By the time the next batch of updates becomes available to you, the Linux Mint team has had time to adjust packages in the Linux Mint repository and to document the information you need to go through a safe and easy update.
- to help debugging those updates were created incoming and latest: basically these repos are identical, but incoming is updated a few days/a week before latest to test the UP and then it will migrate from incoming to latest:
- Update-Pack 8 has been released on February the 4th 2014.To facilitate this process, we’re opening another repository called “Incoming”, which is downstream from Debian Testing and upstream from “Latest”. In other words, we first update the “Incoming” repository. We test things out and we gather information from people using the “Incoming” repositories. And when we’re happy with the state of things, we point the “Latest” archive to the “Incoming” one.
- 4.a) -Clonezilla (almost a must)
A little clumzy to first learn, but actually very easy to use after the very first time.
a nice tutorial here
4.b) - Gparted
4.c ) -SMXI (especially helpful with video drivers)
4.d ) -debian weather
just be aware that debian weather only monitors main, so conflicts in contrib, non-free and multimedia are not reflected in a given day "weather"The "weather" of a given Debian-based distribution is an indication of how safe it is on a given day to attempt some package installation/upgrade. A "bad day" is a day in which a sensible percentage of that distribution repository is not installable due to unsatisfiable inter-package dependencies.
SECTION TWO - QUESTIONS & ANSWERS
Q0- Why should I use apt dist-upgrade to upgrade my system?
This is the best advice to LMDE user: Forget that you ever heard of apt upgrade.
As explained by ZeroZero:
A more detailed explanation is given here.1- it's documented in the wounds and scars we got in the early days of lmde
2- it's also documented in the systems that crashed and burned because of it
3- it's finally documented in the fact that not one rolling release has or recommend any form of partial upgrade (and although lmde can't technical be called a rolling release, these UP updates act like it)
Q1- how is security handled in LMDE?
- let's see, if security is THE most important value for you, then you probably shouldn't be using LMDE/debian testing/sid (stable is your answer)
- debian testing security team is responsible for:
The team is providing security support for Debian's testing branch by
writing patches and doing NMUs to unstable as necessary
tracking the fixed packages and working with the Debian Release Managers to make sure fixes reach testing quickly
if this process is too slow, providing fixed packages built against testing in the testing-security apt repository:
deb http://security.debian.org testing/updates main contrib non-free
deb-src http://security.debian.org testing/updates main contrib non-free
However, the majority of security fixes reach testing by migration from unstable. (more about NMUs here and here).
- as you can see above only as a last resort the security fixes are pulled down though security.debian.org and only for debian main (contrib and non-free are not supported by the security team)
Contrib and non-free aren't official parts of the Debian Distribution and are not released, and thus not supported by the security team. Some non-free packages are distributed without source or without a license allowing the distribution of modified versions. In those cases no security fixes can be made at all. If it is possible to fix the problem, and the package maintainer or someone else provides correct updated packages, then the security team will generally process them and release an advisory.
- sid has no security team:
Unstable is a rapidly moving target and the security team does not have the resources needed to properly support it.
- some more reading
- another interesting sum up about security
- short answer: no, it will break your debian installation;
- long answer: it's your system, you do with it what you want, if you break it, "you keep the pieces, we laugh at you"; but you were warned: PPA's are ubuntu-specific repos and more often than not you will find hidden incompatibilities as happens with others ubuntu libs
- even knowing this you want/need a random PPA? fine! we expect from you to know how to manually add an entry to your sources.list.
- let's assume (for the sake of this answer) that's there's nothing wrong with your sources.list (check above to see if your repos are correct)
- if you are using latest or incoming there's a buffer between your UP and testing see, that buffer can be longer or shorter, leading to a lag compared to testing.
- if you are using testing, you might find out that not always you have the latest v. available, it's not surprising if you look at the requirements for the the pkgs migration from sid to testing:
A package is installed into the testing dist from DebianUnstable automatically when a list of requirements is fulfilled:
The package is at least 10 days old.
The package has been built for all the architectures which the present version in testing was built for.
Installing the package into testing will not make the distribution more uninstallable.
The package does not introduce new release critical bugs. here
- the newest pkgs arrive on sid or experimental and from there down to testing (after the high debian requirements are fulfilled)
- but if you look at this and this we easily see that it takes more than being a good hacker and have a great app to have the latest&greatest available in debian's ftp's.
- ok, this addressees the "why", now how do i solve this if i have an outdated app?
- 1 - compile it (it's usually easier than it sounds)
- 2 - can't you wait for the next UP (if tracking latest) or the next testing migration?
- 3 - look in the immediately next debian release (just a reminder: if you are using lmde with the default latest repos look first in testing)
- 4 - look around in the debian universe (there should be somewhere what you are looking for)
Disclaimer: this is not an howto AptPinning (it's out of the scope of this faq), i will just try to give here some pointers about the subject and its relation with lmde.
- 1- lmde has a preferences file (cat /etc/apt/preferences), unlike debian and ubuntu for example, look at it, study it, realize exactly what it means before you decide to add/change any rule there;
- 2- if you are using the default repos and have no intentions in adding others this doesn't concern you, this file is only of use if you decide to mix (in a safe way) latest/testing/sid/experimental (just some of those/all of them/whatever);
- 3- the way it is (default) the preferences file tell Apt that all Mint packages have priority (700) over any the same package from debian (500); this is ok because keeps Mint identity (and once again, if you are using the default just leave it as-is);
- 4- the question is: if you leave latest and move to testing or sid you will find out soon that those preferences are interfering with your system; this is the call to look at AptPinning
- http://forums.linuxmint.com/viewtopic.p ... 7&t=107216
- http://www.debian.org/doc/manuals/debia ... te_version
- http://www.debian.org/doc/manuals/apt-h ... html#s-pin
- read, read, read, before you start tweaking the preferences file.