$ apt-cache policy amarok
100 http://backports.debian.org/debian-backports/ squeeze-backports/main amd64 Packages
990 http://ftp.caliu.cat/debian/ squeeze/main amd64 Packages
...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.
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.
It takes no more than simply setting the distribution string in the "/etc/apt/sources.list" to the suite name: "testing" or "unstable"; or the codename: "wheezy" or "sid". This makes you live the life of eternal upgrades.
The use of testing or unstable is a lot of fun but comes with some risks. Even though the unstable suite of Debian system looks very stable for most of the times, there have been some package problems on the testing and unstable suite of Debian system and a few of them were not so trivial to resolve. It may be quite painful for you. Sometimes, you may have a broken package or missing functionality for a few weeks.
Make the system dual bootable by installing the stable suite of Debian system to another partition
hariskar wrote:Do I have to install Debian sid to install Amarok 2.6? Can't I install it on Debian 6.0.6?
How do I backport a sid package to testing or stable?
Install the Debian source (and the development tools, especially debhelper, devscripts, and build-essential), and then build the package.
Step by step:
Following the same steps you used to add the backports repo:
add a deb-src line for sid to your sources.list
deb-src http://ftp.us.debian.org/debian/ unstable main contrib non-free
apt-get build-dep PACKAGE_NAME
apt-get -b source PACKAGE_NAME
The resulting debs should be in the current directory and can be installed with dpkg -i the.deb or gdebi if you have it installed.
thegeko wrote:Actually, I should run unstable, because packages in testing are still somewhat old.
BUT, the excuse that stable is bug free, is a MYTH.
For instance right now, amarok plays each song twice in a row on random mode, I mean if this is not serious bug, then what is??
Thus it seems to me, old versions in stable carry their old bugs solved long ago. From this point of view I don't see many advantages of stable.
Thus usual point "simply upgrade to testing" is not that simple and does not stand.
The reason is that upgrade process is the last thing that is tested before moving release to testing. Now I am just waiting till current testing becomes stable, so I can upgrade without trouble. And then upgrade to testing.
I mean howcome ubuntu has newest software and seems to me like it has same amount of bugs at any point of time.
Users browsing this forum: PvO and 8 guests