* [gentoo-amd64] File collision with courier-imap and maildrop
@ 2008-01-09 19:35 P.V.Anthony
2008-01-10 11:21 ` [gentoo-amd64] " Duncan
0 siblings, 1 reply; 4+ messages in thread
From: P.V.Anthony @ 2008-01-09 19:35 UTC (permalink / raw
To: gentoo-amd64
Hi,
Trying to install courier-imap and maildrop and encountering file
collisions.
Is there any way to solve this? Some way to force it?
Guessing that the files are the same as courier-imap and maildrop come
from the same main courier-mta.
Here is the error message.
------------------ start ----------------------
* Messages for package mail-filter/maildrop-2.0.4:
* This package will overwrite one or more files that may belong to other
* packages (see list below). Add "collision-protect" to FEATURES in
* make.conf if you would like the merge to abort in cases like this. You
* can use a command such as `portageq owners / <filename>` to identify
* the installed package that owns a file. If portageq reports that only
* one package owns a file then do NOT file a bug report. A bug report is
* only useful if it identifies at least two or more packages that are
* known to install the same file(s). If a collision occurs and you can
* not explain where the file came from then you should simply ignore the
* collision since there is not enough information to determine if a real
* problem exists. Please do NOT file a bug report at
* http://bugs.gentoo.org unless you report exactly which two packages
* install the same file(s). Once again, please do NOT file a bug report
* unless you have completely understood the above message.
*
* Detected file collision(s):
*
* /usr/share/man/man1/maildirmake.1.bz2
* /usr/share/man/man8/deliverquota.8.bz2
* /usr/bin/maildirmake
------------------ end ----------------------
P.V.Anthony
--
gentoo-amd64@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* [gentoo-amd64] Re: File collision with courier-imap and maildrop
2008-01-09 19:35 [gentoo-amd64] File collision with courier-imap and maildrop P.V.Anthony
@ 2008-01-10 11:21 ` Duncan
2008-01-12 16:26 ` P.V.Anthony
0 siblings, 1 reply; 4+ messages in thread
From: Duncan @ 2008-01-10 11:21 UTC (permalink / raw
To: gentoo-amd64
"P.V.Anthony" <pvantony@singnet.com.sg> posted
47852216.2040600@singnet.com.sg, excerpted below, on Thu, 10 Jan 2008
03:35:50 +0800:
> Trying to install courier-imap and maildrop and encountering file
> collisions.
>
> Is there any way to solve this? Some way to force it?
>
> Guessing that the files are the same as courier-imap and maildrop come
> from the same main courier-mta.
There's a way (actually several) to force it, but be sure to file a bug
on it anyway (checking first to see if one's already filed, of course).
IOW, don't let the fact that you can force it cause you to avoid the bug
filing step, because it /is/ a bug, and should be fixed.
1) You can avoid the problem once with
FEATURES=-collision-protect emerge <whatever>
2) Since that one causes a possibly quite lengthy full emerge, and the
collision-protect test happens at the end, after the package is compiled,
right before it's actually merged, you may prefer using ebuild. That's a
bit more complicated as portage uses the environment (including FEATURES)
from previous steps in later calls to ebuild, so you have to edit that
saved environment to get it to finish.
Edit ${T}/environment (see man 5 ebuild for the meaning of the ${T}
variable) as appropriate, in this case, removing collision-protect from
features.
ebuild /<path/to/ebuild.ebuild> merge
(See man 1 ebuild for the ebuild command details.)
Note that unlike emerge, ebuild can't figure out where the ebuild is by
itself. You have to give it the full path to the ebuild,
/${PORTDIR}/${CATEGORY}/${PN}/${PF}.ebuild . Of course that's a bit of a
hassle, so for trivial merges, it's easier just to use (1) above, but for
those that take awhile, typing the full path isn't /too/ hard, especially
not with tab-completion. =8^)
3) If you want to have portage avoid collision-protect checking for a
specific file, class of files, or an entire directory, by default, set
the COLLISION_IGNORE variable in make.conf (man 5 make.conf for details).
Normally, you'll want to do the one-shot thing using methods 1 or 2,
since you'd expect the bug you file (right?!) to be resolved before you
have to update or remerge that package. However, method 3 comes in handy
in cases such as the one I had recently in the kde overlay, testing KDE4
svn packages. In that case, upstream (the KDE devs) were still actively
changing files around, adding new ones, moving them to different
packages, deleting old ones, etc, and a lot of these were non-critical
stuff like icons and the like. The folks running the Gentoo kde overlay
recommended that people set FEATURES=collision-protect as a safety
measure to avoid KDE3 and KDE4 interfering with each other, but having
the merges stop just because an icon appeared in two different KDE4
packages because upstream had just changed it wasn't useful, and was VERY
frustrating. That's where COLLISION_IGNORE comes in, as I was able to
set it to have portage avoid the KDE4 icons dir entirely.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-amd64] Re: File collision with courier-imap and maildrop
2008-01-10 11:21 ` [gentoo-amd64] " Duncan
@ 2008-01-12 16:26 ` P.V.Anthony
2008-01-13 10:53 ` Duncan
0 siblings, 1 reply; 4+ messages in thread
From: P.V.Anthony @ 2008-01-12 16:26 UTC (permalink / raw
To: gentoo-amd64
On this day, 10-January-2008 7:21 PM, Duncan wrote:
> There's a way (actually several) to force it, but be sure to file a bug
> on it anyway (checking first to see if one's already filed, of course).
> IOW, don't let the fact that you can force it cause you to avoid the bug
> filing step, because it /is/ a bug, and should be fixed.
>
> 1) You can avoid the problem once with
>
> FEATURES=-collision-protect emerge <whatever>
This method worked. Thank you for the solution. Really needed this solution.
Looked at doing a bug report and found that it was done already. In fact
on the 1st of Jan 2008.
http://bugs.gentoo.org/show_bug.cgi?id=203947
> 3) If you want to have portage avoid collision-protect checking for a
> specific file, class of files, or an entire directory, by default, set
> the COLLISION_IGNORE variable in make.conf (man 5 make.conf for details).
This one is really cool. Thank you very much for sharing this information.
P.V.Anthony
--
gentoo-amd64@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* [gentoo-amd64] Re: File collision with courier-imap and maildrop
2008-01-12 16:26 ` P.V.Anthony
@ 2008-01-13 10:53 ` Duncan
0 siblings, 0 replies; 4+ messages in thread
From: Duncan @ 2008-01-13 10:53 UTC (permalink / raw
To: gentoo-amd64
"P.V.Anthony" <pvantony@singnet.com.sg> posted
4788EA46.2090506@singnet.com.sg, excerpted below, on Sun, 13 Jan 2008
00:26:46 +0800:
[About collision-protect and -ignore.]
> Thank you very much for sharing this information.
Thanks for the success report, as well. Nice to know that it worked.
=8^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-01-13 10:53 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-09 19:35 [gentoo-amd64] File collision with courier-imap and maildrop P.V.Anthony
2008-01-10 11:21 ` [gentoo-amd64] " Duncan
2008-01-12 16:26 ` P.V.Anthony
2008-01-13 10:53 ` Duncan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox