Default repositories and preferences in MX14?

[lucky9]

It just involves an install of the packages. Then seeing if there are problems.

I do as you do Eadwine Rose. Mark and check what APT/Synaptic or Aptitude wants to install or remove.

[richb]

Test installing was referring to the wheezy-backport packagers testing with an install before committing them to the repository. Not us end users.

[timkb4cq]

Hopefully. It only takes a few minutes to rebuild. Maybe they'll try test-installing the packages first this time around.

The uploader didn't have consolekit on the machine he was using which means he didn't have Gnome, KDE or XFCE. So his system didn't break. Of course, if you're building for wheezy-backports you should check that all listed dependencies are satisfiable in wheezy or wheezy-backports, and preferably test with the default wheezy desktop (Gnome) installed.

[richb]

We tend to forget that every MX and M12 installed to date is a test install. The purpose is to find errors, including breakage and report to the developers. And it is a test install until it is released.

Wheezy-backports is released into the wild so the responsibility clearly lies with the developers that populate it.

[kmathern]

It looks like they will have a updated consolekit package in the wheezy-backports repo in the next day or so, there's a message on the debian-backports-changes list here: https://lists.debian.org/debian-backpor ... 00114.html, and I see the i386 & amd64 packages @http://incoming.debian.org/. (I haven't reloaded with a `apt-get update`, it might even be in the repos right now.)