On Tuesday 28 April 2009 01:20:56 Michael Higgins wrote:
I _remember_ doing this just a few days ago, so I'm not doing it again...
but why is it still throwing a warning? Is this a limitation of portage or
the ebuild?
--
WARN: postinst
/usr/lib/cups exists - You need to remerge every ebuild that
installed into /usr/lib/cups and /etc/cups, qfile is in portage-utils:
# FEATURES=-collision-protect emerge -va1 $(qfile -qC /usr/lib/cups
/etc/cups | sed s:net-print/cups$::) FEATURES=-collision-protect is
needed to overwrite the compatibility symlinks installed by this package,
it won't be needed on later merges.
There's the solution to your problem. Every time you rebuild cups, it will
check and find that this directory exists, and assume that it's an upgrade
that will break packages linking to it. You could enable -collision-protect,
but I can't honestly recommend that.
You should also run revdep-rebuild
--
Did they forget to tell me what to do so that the warning stops? '-)
No, I think the initial check in pkg_postinst() is a little too wide. Merely
checking for the existence of a directory will give false positives. It would
be better to check for the existence of particular files and symlinks so the
ebuild knows more exactly what is going on.
I'd file a bug, and ask for this check to be made more specific
Is it possible that it's necessary to re-emerge all those packages on every
cups *ebuild* update?
Did you upgrade or just rebuild? With an upgrade, I'd revdep-rebuild and with
a rebuild, you could probably ignore this warning.
--
alan dot mckinnon at gmail dot com
