So there I was with one of my less important computers and thought... gee today would be a good idea to just do a DU....
however, as I always, always read what is about to happen I saw the remove notice, just said *No* and looked here.
Its never a problem to just wait.
99% of the time I read the forums first. I always... *never* assume it is OK to DU without reading the message of what it is about to do.
That is always an absolute commandment.

alexk

Post subject:Posted: 14.11.2011, 20:48

Joined: 2010-10-01
Posts: 194

Status: Offline

First Commandment of Sid: Thou shalt ignore packages to be REMOVED only at thy GREATEST peril (especially if there are a whole slew of them).
Second Commandment: Thou shalt READ.

For a user, just sitting out a core library transition is usually the best idea - after all the release team is scheduling coordinated migrations with binNMUs pretty quickly (mostly a matter of 1-2 days, to get the worst settled). Holds however have the nasty side effect that they tend to get forgotten and might thereby introduce quite nasty side effects long after the fact.

Looking at past perl transitions, it usually didn't take much longer than two days - a time span that shouldn't bother anyone but the most impatient users.

gutterslob

Post subject:Posted: 15.11.2011, 08:37

Joined: 2010-12-25
Posts: 44
Location: Wandering
Status: Offline

slh wrote:

Holds however have the nasty side effect that they tend to get forgotten and might thereby introduce quite nasty side effects long after the fact.

That's the main reason why I try not to put packages on hold unless absolutely necessary. Not really fun picking up the pieces, plus it's just troublesome on the brain when one has different systems running different operating systems.

It's still kind of shocking how often people seem to d-u blindly. Maybe they got lulled into a false sense of stability over the last few relatively peaceful months.

slh

Post subject:Posted: 15.11.2011, 16:46

Joined: 2010-08-25
Posts: 778

Status: Offline

Depending on your mirror and architecture, the worst could be over already. This does not save you from actually checking for packages to be removed, of course (libperl5.12 should go).

vinur

Post subject:Posted: 16.11.2011, 08:01

Joined: 2010-09-11
Posts: 61
Location: Lake Oswego
Status: Offline

slh wrote:

Depending on your mirror and architecture, the worst could be over already. This does not save you from actually checking for packages to be removed, of course (libperl5.12 should go).

Performed D-U on main system and lessor system. No Issues, perfect.
yes... libperl5.12 went away.