[Cupt-devel] Bug#764755: cupt: Pinned package is upgraded due to strict Depends from another package

Eugene V. Lyubimkin jackyf at debian.org
Fri Oct 17 20:48:37 UTC 2014


Control: clone -1 -2
Control: severity -2 wishlist
Control: reassign -2 apt-listbugs
Control: retitle -2 please increase priority of "hold"-type generated pins

Hi,

To apt-listbugs folks: please use much more higher pin priority (say,
10000 or 20000) if what you want to say is "don't modify this package
unless you have a very good reason", not "try this version first unless
some other package relations disagree". The difference between
highest-possible-by-default-990 and 1000 might be enough for
'candidate-or-nothing' APT but unfortunately isn't for priority-based
resolving in Cupt. I'd be grateful if you could consider this change for
jessie so users of cupt in coming stable could use this feature of
apt-listbugs.

Independently of that the bug against Cupt remains open to track the
changes coming to 2.9.0 (work underway) to treat these kinds of 'version
priority downgrade' more negatively than in 2.8.x by default plus the
ability to configure it to be even more stricter if user wants so.  Even
after that changes, though, high (or, on the contrary, low) priority
numbers are still the best way to tell how negative/positive different
version choices are, especially when compared to version choices of
other packages.

-- 
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++ GNU/Linux userspace developer, Debian Developer



More information about the Cupt-devel mailing list