mockturtl wrote:edit: server is back up
Any guesstimated timeline for LMDE KDE next release?
Monsta wrote:The item about making your own LMDE/Squeeze should probably be changed... see viewtopic.php?f=199&t=99489#p566338
3.1.11 I am currently tracking stable. Can I change to testing or unstable? If so, How?
If you are currently running stable, then in the /etc/apt/sources.list file the third field will be either squeeze or stable. You need to change this to the distribution you want to run. If you want to run testing, then change the third field of /etc/apt/sources.list to testing. If you want to run unstable, then change the third field to unstable.
Currently testing is called wheezy. So, if you change the third field of /etc/apt/sources.list to wheezy, then also you will be running testing. But when wheezy becomes stable, you will still be tracking wheezy.
Unstable is always called Sid. So if you change the third field of /etc/apt/sources.list to sid, then you will be tracking unstable.
Currently Debian offers security updates for testing but not for unstable, as fixes in unstable are directly made to the main archive. So if you are running unstable make sure that you remove the lines relating to security updates in /etc/apt/sources.list.
If there is a release notes document available for the distribution you are upgrading to (even though it has not yet been released) it would be wise to review it, as it might provide information on how you should upgrade to it.
Nevertheless, once you make the above changes, you can run aptitude update and then install the packages that you want. Notice that installing a package from a different distribution might automatically upgrade half of your system. If you install individual packages you will end up with a system running mixed distributions.
It might be best in some situations to just fully upgrade to the new distribution running apt-get dist-upgrade, aptitude safe-upgrade or aptitude full-upgrade. Read apt's and aptitude's manual pages for more information.
3.1.12 I am currently tracking testing (wheezy). What will happen when a release is made? Will I still be tracking testing or will my machine be running the new stable distribution?
It depends on the entries in the /etc/apt/sources.list file. If you are currently tracking testing, these entries are similar to either:
deb http://ftp.us.debian.org/debian/ testing main
deb http://ftp.us.debian.org/debian/ wheezy main
If the third field in /etc/apt/sources.list is 'testing' then you will be tracking testing even after a release is made. So after wheezy is released, you will be running a new Debian distribution which will have a different codename. Changes might not be apparent at first but will be evident as soon as new packages from unstable go over to the testing distribution.
But if the third field contains 'wheezy' then you will be tracking stable (since wheezy will then be the new stable distribution).
LifeInTheGrey wrote:Suffice to say, yes ... a lot of stuff from UP4 (from the Mint repo, specifically) conflicts with Squeeze and will bork it. It is still entirely possible to have an LMDE Squeeze, it just requires a little sacrifice. You could (a) be much more mindful of updates, or (b) disable the Mint repo so that you only receive Debian squeeze and squeeze-backports updates. This way you can still keep the fantastic GNOME and Mint Menu, and will still get all the up-to-date stuff. Yes yes ... not ALL the up-to-date stuff ... for those that are still refusing to use Iceweasel because they use proprietary version of the same code (Firefox) ... you'll be out of luck. Other than those few exceptions, though, you should be safe.
That is for those that want to cling to a few more moments of our belovedly deceased GNOME 2. For those that are willing to let go ... MATE is pretty much the exact same thing, Compiz and all, and its gotten pretty stable. Just sayin.
the backport in the packages.linuxmint repo are not replacement/conflict/addiction for the debian backports.
i can't remember last time linuxmint.backport was used http://packages.linuxmint.com/list.php? ... n#backport
the issues come from main upstream import.
zerozero, I hashed out this source:deb http://packages.linuxmint.com/ debian main upstream import backport
Users browsing this forum: No registered users and 1 guest