Hi,
On 11-03-16 19:33, Francesco Poli wrote:
But: how does pinning help? I don't want it to become permanently pinned.
Each pin is automatically removed by a daily cron job, as soon as the
bug is fixed in the package version available for installation/upgrade.
Hmm, I used to pin something, but then it always was permanent. How does
the automatic unpinning work?
And indeed you usually do not have to worry about pins.
As I said, please take a look at the documentation, whenever you have
doubts.
I just read it, thanks for reminding me again. And thanks for simply
quoting the appropriate parts of the documentation to me :)
Just one suggestion: add 'p' to the hints at possible answers to the
question "Are you sure you want to install/upgrade the above packages?".
Or simply behave as if 'p' was responded when people answer 'no',
because I would expect that to be the most likely answer that a
knowledgeable user would give.
Or change the question to something like: "What would you like to do
now? a) abort the upgrade b) pin these packages to their current
versions until the bugs are solved c) just continue the upgrade.
If any of these would be implemented, it would be more obvious to users
this package what response to give.
Thanks for maintaining this useful package :)
--
Grtjs, Manuel
PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ )
PPS: Visit my homepage at http://manuel.msxnet.org/
