>>> Installing x11-wm/afterstep-2.2.4 * 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. * * Detected file collision(s): * * /usr/bin/ascompose * /usr/bin/asi18n * /usr/bin/asflip * /usr/bin/asgrad * /usr/bin/astext * /usr/bin/astile * /usr/bin/asview * /usr/bin/asmerge * /usr/bin/asscale * /usr/bin/afterimage-libs * /usr/bin/afterimage-config * /usr/bin/asvector * /usr/lib/libAfterImage.so.0.99 * /usr/include/libAfterImage/export.h * /usr/include/libAfterImage/afterbase.h * /usr/include/libAfterImage/afterimage.h * /usr/include/libAfterImage/bmp.h * /usr/include/libAfterImage/xcf.h * /usr/include/libAfterImage/xpm.h * /usr/include/libAfterImage/xwrap.h * /usr/include/libAfterImage/ximage.h * /usr/include/libAfterImage/asim_afterbase.h * /usr/include/libAfterImage/draw.h * /usr/include/libAfterImage/config.h * /usr/include/libAfterImage/imencdec.h * /usr/include/libAfterImage/pixmap.h * /usr/include/libAfterImage/ungif.h * /usr/include/libAfterImage/asimagexml.h * /usr/include/libAfterImage/asstorage.h * /usr/include/libAfterImage/blender.h * /usr/include/libAfterImage/transform.h * /usr/include/libAfterImage/char2uni.h * /usr/include/libAfterImage/ascmap.h * /usr/include/libAfterImage/asvisual.h * /usr/include/libAfterImage/asfont.h * /usr/include/libAfterImage/import.h * /usr/include/libAfterImage/asimage.h * /usr/lib/libAfterImage.so * /usr/lib/libAfterImage.so.0 * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * media-libs/libafterimage-1.15 * /usr/bin/afterimage-config * /usr/bin/afterimage-libs * /usr/bin/ascompose * /usr/bin/asflip * /usr/bin/asgrad * /usr/bin/asi18n * /usr/bin/asmerge * /usr/bin/asscale * /usr/bin/astext * /usr/bin/astile * /usr/bin/asvector * /usr/bin/asview * /usr/include/libAfterImage/afterbase.h * /usr/include/libAfterImage/afterimage.h * /usr/include/libAfterImage/ascmap.h * /usr/include/libAfterImage/asfont.h * /usr/include/libAfterImage/asim_afterbase.h * /usr/include/libAfterImage/asimage.h * /usr/include/libAfterImage/asimagexml.h * /usr/include/libAfterImage/asstorage.h * /usr/include/libAfterImage/asvisual.h * /usr/include/libAfterImage/blender.h * /usr/include/libAfterImage/bmp.h * /usr/include/libAfterImage/char2uni.h * /usr/include/libAfterImage/config.h * /usr/include/libAfterImage/draw.h * /usr/include/libAfterImage/export.h * /usr/include/libAfterImage/imencdec.h * /usr/include/libAfterImage/import.h * /usr/include/libAfterImage/pixmap.h * /usr/include/libAfterImage/transform.h * /usr/include/libAfterImage/ungif.h * /usr/include/libAfterImage/xcf.h * /usr/include/libAfterImage/ximage.h * /usr/include/libAfterImage/xpm.h * /usr/include/libAfterImage/xwrap.h * /usr/lib/libAfterImage.so * /usr/lib/libAfterImage.so.0 * /usr/lib/libAfterImage.so.0.99 * * Package 'x11-wm/afterstep-2.2.4' NOT merged due to file collisions. If * necessary, refer to your elog messages for the whole content of the * above message. >>> Failed to install x11-wm/afterstep-2.2.4, Log file: Reproducible: Always
Perhaps afterstep should depend on libafterimage instead of installing all those files itself.
Actually, afterstep should provide libafterimage. Or i dunno. (In reply to comment #1) > Perhaps afterstep should depend on libafterimage instead of installing all > those files itself. >
Until bug #253259 is solved, I've added a blocker in afterstep (libafterimage already had a blocker) libafterimage needs a new release from upstream too (version bundled in afterstep 2.29 is newer)
