>>> Installing (18 of 93) net-libs/libsoup-2.42.0
* checking 185 files for package collisions
* 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):
* Searching all installed packages for file collisions...
* Press Ctrl-C to Stop
* Package 'net-libs/libsoup-2.42.0' NOT merged due to file collisions.
* If necessary, refer to your elog messages for the whole content of the
* above message.
It seems a soft block on libsoup-gnome will resolve it, but there are two other things:
- gnome2_src_configure with parameters should go at the end of src_configure (the second one is redundant)
- 'http? ( || ( >=net-libs/libsoup-2.42:2.4 >=net-libs/libsoup-2.34.0[gnome] ) )' dep in gvfs-1.16.0 is bogus (there's no net-libs/libsoup[gnome] in the tree atm)
All should be handled now, thanks
(In reply to comment #2)
> All should be handled now, thanks
In such case, which version of libsoup-gnome did have 'gnome' useflag ?
(In reply to comment #3)
> (In reply to comment #2)
> > All should be handled now, thanks
> In such case, which version of libsoup-gnome did have 'gnome' useflag ?
Please point to exact problem after syncing instead of being sarcastic