Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 209807 - app-editors/nvu-1.0-r4 shouldn't install /usr/share/aclocal/nspr.m4
Summary: app-editors/nvu-1.0-r4 shouldn't install /usr/share/aclocal/nspr.m4
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Mozilla Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-12 09:45 UTC by Jakub Moc (RETIRED)
Modified: 2008-02-12 16:14 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jakub Moc (RETIRED) gentoo-dev 2008-02-12 09:45:06 UTC
Before I forget... :P

* This package will overwrite one or more files that may belong to other
 * packages (see list below). 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.
 * 
 * package dev-libs/nspr-4.7 NOT merged
 * 
 * Detected file collision(s):
 * 
 * 	/usr/share/aclocal/nspr.m4
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * app-editors/nvu-1.0-r4
 * 	/usr/share/aclocal/nspr.m4
Comment 1 Raúl Porcel (RETIRED) gentoo-dev 2008-02-12 16:14:50 UTC
Should be fixed now, thanks.