Default repositories and preferences in MX14?

[Eadwine Rose]

As the announcement today says: the upgrade messes things up unless you have the M12 Main CR enabled.

What exactly does that mean?


By default the repositories in synaptic have the mepiscr repo enabled.

I also read in the broken system thread that the preferences need to be set to prefer mepis. However currently the default preference is set to highest on my MX14 system. I have not touched that particular synaptic section myself, this is the first time that I looked at it, this is what it was set up as.


This is confusing as it contradicts to me.


Now what does one need to do to get the upgrades not to break the system?

Enable mepiscr repositories? This was enabled from the getgo, so leave as is?

Set the preferences to prefer mepis? If yes, should the default preferences in MX14's new final that is coming up not rather be set then to prefer Mepis, as opposed to what it is now: always prefer highest?

[richb]

@Eadwine

The confusion arises because M12 is also affected.

For MX-14 Leave the enabled repos at default settings as well as preferred distribution, (Highest). This worked for me in MX-14.

[Eadwine Rose]

Aha.. *eyes upgrades*



*gulp*

Here goes nothing!

[ko]

@Eadwine

The confusion arises because M12 is also affected.

For MX-14 Leave the enabled repos at default settings as well as preferred distribution, (Highest). This worked for me in MX-14.

I can confirm that the default settings for repos and preferred distribution are OK in MX-14. Don't change them.

[Eadwine Rose]

I can now also confirm all is still alive and kicking after a reboot.

[timkb4cq]

Actually that post said that if wheezy-backports were disabled, AND the main MEPIS 12 CR was enabled AND preferences were set to "prefer mepis" then a normal upgrade would remove kdm from M12. Having preferences at Highest Version kept the new consolekit package from being seen as an upgrade, thus avoiding the problem.

That was the price for having to fix wheezy-backports mistake here instead of on their end.
Fortunately, since preferences are set by default to highest version, and wheezy-backports are enabled, it will be a rare M12 install that triggers the issue. Once the debian backports team gets a new consolekit at their end I can remove my backport

[Eadwine Rose]

Thanks for clarifying, and you can see where I was (and still am) confused.


Goes to give a good argument in any case against auto updates In case the default settings are changed an automatic update might turn into a dramatic update...

[kmathern]

Actually that post said that if wheezy-backports were disabled, AND the main MEPIS 12 CR was enabled AND preferences were set to "prefer mepis" then a normal upgrade would remove kdm from M12. Having preferences at Highest Version kept the new consolekit package from being seen as an upgrade, thus avoiding the problem.

That was the price for having to fix wheezy-backports mistake here instead of on their end.
Fortunately, since preferences are set by default to highest version, and wheezy-backports are enabled, it will be a rare M12 install that triggers the issue. Once the debian backports team gets a new consolekit at their end I can remove my backport

There's now a message on the debian-backports mail list about the udev upgrade breaking/removing consolekit: https://lists.debian.org/debian-backpor ... 00114.html, it wasn't there earlier today. Maybe that will get them to backport it.

[Stevo]

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

[Eadwine Rose]

How does one test install things using synaptic? I just do mark all upgrades and see if it removes anything important.

Other than that I have no clue