Enrico Weigelt wrote:
<big_snip />
My problem still seems unsolved (or did I miss something) ?
Lets say, if I've, installed foo-1.1, and it gets masked due
some bug(s), but 1.0 isn't, I want to get informed with an big
fat warning, *before* anything actually done, ie.
[...]
# WARNING: installed package foo-1.1 has been masked and would
# be downgraded:
# <masking comment ...>
[...]
An fully-automatic downgrade should *never* downgrade anything.
This is too dangerous, because essential features can get lost.
Again, my bugzilla example: assuming 2.22 will be unmasked some
day and I installed it w/ postgres support. Now there are some
bugs found, but not fixed fast enough, so it gets masked.
I run an update w/o knowing that it downgrades, and my whole
bugzilla hosting is suddenly broken.
Do you consider this as stability, seriously ?!
If your bugzilla hosting breaks with lower versions, then the ebuild contains a
RDEPEND="postgres? ( >=dev-db/postgresql-2.22 )". Now if >=postgresql-2.22 gets
masked, portage will bail out with an error because it can't find a valid
dependency tree. This will cause the comment above the masking line in p.mask to
be shown. You can then decide whether the breakage affects you or not and
depending on that unmask it locally or remove your bugzilla installation.
If there is a bugzilla-ebuild which works with <postgresql-2.22, it will be
downgraded too, leaving you with a working bugzilla.
I can't quite see the massive problem.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
