Re: [gentoo-user] What gives with all these file collisions?

2017-06-04 Thread Tom H 
On Fri, Jun 2, 2017 at 3:07 AM, Kent Fredric  wrote:
> On Fri, 2 Jun 2017 08:23:22 +0200
> Alan McKinnon  wrote:
>>
>> Or you could use Ubuntu.
>
> Can you please refrain from such phrases.

History with Alab G.

As an Ubuntu user, perhaps I should take offense! :)

Re: [gentoo-user] What gives with all these file collisions?

2017-06-02 Thread Willie M 
On Fri, 2 Jun 2017 19:05:25 +1200
Kent Fredric  wrote:

> On Thu, 1 Jun 2017 23:32:55 -0700
> Willie M  wrote:
> 
> > I am sure you can use the FEATURES to ignore collisions. It has been
> > awhile but I am sure it is still there.  
> 
> Disabling collisions detections is not really good advice, as it can
> lead to real problems and break your system.
> 
> Then again, just pasting lists to RM is not smart either.
> 
> Better to work out *why* there's a collision first.
> 
> In the example the user posted, they're installing kde-apps/k3b:5 on
> top of kde-apps/k3b:4
> 
> Those packages should block against each other in some way if they
> install the same files.
> 
> This sort of stuff happens if you're running ~arch, and is usually
> grounds for a bug.

I see.

-- 

Willie L Matthews
matthews.willi...@gmail.com
702-659-9966


pgpj1UYBBCRyg.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] What gives with all these file collisions?

2017-06-02 Thread J. Roeleveld 
On June 2, 2017 9:07:57 AM GMT+02:00, Kent Fredric  wrote:
>On Fri, 2 Jun 2017 08:23:22 +0200
>Alan McKinnon  wrote:
>
>> Or you could use Ubuntu.
>
>Can you please refrain from such phrases.

Based on the history of emails from the OP, this is quite justified.

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] What gives with all these file collisions?

2017-06-02 Thread Kent Fredric 
On Fri, 2 Jun 2017 02:23:44 -0400
Alan Grimes  wrote:

> without spending all day and all night cut-pasting filenames into
> another terminal and running rm on them...

Looking at the candidate you showed: 

k3b:

  version=2.0.3-r5 slot=4   stable
  version=17.04.1  slot=5   testing

It seems like its plausible you recently changed your keywording choices
somewhere from "arch" to "~arch", bringing a lot of untested upgrades
with it. Or, you allowed portage to perform far more auto-unmasks than
really made sense for what you're doing.

I could be wrong though.

But what appears to be the problem is you have 2 k3b versions, which,
according to slots, should be permitted to be co-installed, but
according to the files they install, can't be co-installed.

This seems like possible cause for opening a bug on k3b, so that
k3b:5 blocks against k3b:4 and vice versa.

But as for the other cases you saw, I can't really comment, because its
seldom the case that multiple packages are having file collisions for
the same reason.

The only usual reason for that sort of thing happening on a broad scale
is /usr/  getting provisioned during install, and staying, but the
contents index in /var/db/pkg getting lost somehow due to the segv +
reboot, leaving the files there, but leaving portage with no memory of
where they came from.

I've had that sort of thing happen before, but its very rare.



pgpviBXX5ekHZ.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] What gives with all these file collisions?

2017-06-02 Thread Kent Fredric 
On Fri, 2 Jun 2017 08:23:22 +0200
Alan McKinnon  wrote:

> Or you could use Ubuntu.

Can you please refrain from such phrases.


pgp4LI4dYrEo7.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] What gives with all these file collisions?

2017-06-02 Thread Kent Fredric 
On Thu, 1 Jun 2017 23:32:55 -0700
Willie M  wrote:

> I am sure you can use the FEATURES to ignore collisions. It has been
> awhile but I am sure it is still there.

Disabling collisions detections is not really good advice, as it can
lead to real problems and break your system.

Then again, just pasting lists to RM is not smart either.

Better to work out *why* there's a collision first.

In the example the user posted, they're installing kde-apps/k3b:5 on
top of kde-apps/k3b:4

Those packages should block against each other in some way if they
install the same files.

This sort of stuff happens if you're running ~arch, and is usually
grounds for a bug.


pgpvkOk9RAg0H.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] What gives with all these file collisions?

2017-06-02 Thread Willie M 
On Fri, 2 Jun 2017 02:23:44 -0400
Alan Grimes  wrote:

> I'm trying to emptytree my system because GCC update because I need to
> reboot because Nvidia-drivers segfaulted and broke a 2-month endurance
> run on my new mobo of my number theory code, set to use 15
> hyperthreads and 25gb of ram...
> 
> 
> I'm getting lots of package failures due to file collisions and it's
> really starting to get annoying, I mean how am I supposed to fix:
> 
> without spending all day and all night cut-pasting filenames into
> another terminal and running rm on them...
> 
> 
> * Messages for package kde-apps/k3b-17.04.1:
> 
>  * 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 / ` 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 https://bugs.gentoo.org/ unless you report exactly
>  * which two packages install the same file(s). See
>  * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on
> how
>  * to solve the problem. And once again, please do NOT file a bug
> report
>  * unless you have completely understood the above message.
>  *
>  * Detected file collision(s):
>  *
>  *  /usr/share/doc/HTML/en/k3b/K3bAdvancedSettings.png
>  *  /usr/share/doc/HTML/en/k3b/K3bDiskChoice.png
>  *  /usr/share/doc/HTML/en/k3b/K3bMoreActions.png
>  *  /usr/share/doc/HTML/en/k3b/index.cache.bz2
>  *  /usr/share/doc/HTML/en/k3b/K3bSetVerify.png
>  *  /usr/share/doc/HTML/en/k3b/K3bAddButton.png
>  *  /usr/share/doc/HTML/en/k3b/K3bsetup.png
>  *  /usr/share/icons/hicolor/48x48/apps/k3b.png
>  *  /usr/share/icons/hicolor/scalable/apps/k3b.svgz
>  *  /usr/share/icons/hicolor/128x128/apps/k3b.png
>  *  /usr/share/icons/hicolor/64x64/apps/k3b.png
>  *  /usr/share/icons/hicolor/16x16/apps/k3b.png
>  *  /usr/share/icons/hicolor/22x22/apps/k3b.png
>  *  /usr/share/icons/hicolor/32x32/apps/k3b.png
>  *  /usr/share/mime/packages/x-k3b.xml
>  *  /usr/include/k3bmd5job.h
>  *  /usr/include/k3baudiojob.h
>  *  /usr/include/k3bmixeddoc.h
>  *  /usr/include/k3bdevicecombobox.h
>  *  /usr/include/k3bthreadjob.h
>  *  /usr/include/k3baudiodecoder.h
>  *  /usr/include/k3bdevicehandler.h
>  *  /usr/include/k3bactivepipe.h
>  *  /usr/include/k3baudiozerodata.h
>  *  /usr/include/k3bvcdoptions.h
>  *  /usr/include/k3bblankingjob.h
>  *  /usr/include/k3bintmapcombobox.h
>  *  /usr/include/k3bvideodvdvideostream.h
>  *  /usr/include/k3bfileitem.h
>  *  /usr/include/k3baudiodoc.h
>  *  /usr/include/k3baudiocdtrackdrag.h
>  *  /usr/include/k3baudiocdtracksource.h
>  *  /usr/include/k3b_export.h
>  *  /usr/include/k3bdevice.h
>  *  /usr/include/k3bplugin.h
>  *  /usr/include/k3bthroughputestimator.h
>  *  /usr/include/k3bfilesplitter.h
>  *  /usr/include/k3bmedium.h
>  *  /usr/include/k3bdevicetypes.h
>  *  /usr/include/k3bversion.h
>  *  /usr/include/k3bwavefilewriter.h
>  *  /usr/include/k3bglobalsettings.h
>  *  /usr/include/k3bdatadoc.h
>  *  /usr/include/k3bvideodvdaudiostream.h
>  *  /usr/include/k3binffilewriter.h
>  *  /usr/include/k3bvcdjob.h
>  *  /usr/include/k3bpluginconfigwidget.h
>  *  /usr/include/k3bdvdformattingjob.h
>  *  /usr/include/k3bdatajob.h
>  *  /usr/include/k3bcdrecordwriter.h
>  *  /usr/include/k3bfilesysteminfo.h
>  *  /usr/include/k3bprocess.h
>  *  /usr/include/k3bmetawriter.h
>  *  /usr/include/k3biso9660.h
>  *  /usr/include/k3bdiskinfo.h
>  *  /usr/include/k3btocfilewriter.h
>  *  /usr/include/k3bbusywidget.h
>  *  /usr/include/k3bcore.h
>  *  /usr/include/k3bverificationjob.h
>  *  /usr/include/k3brawaudiodatasource.h
>  *  /usr/include/k3bjobhandler.h
>  *  /usr/include/k3bmovixdoc.h
>  *  /usr/include/k3bvideodvdptt.h
>  *  /usr/include/k3bdeviceselectiondialog.h
>  *  /usr/include/k3bchecksumpipe.h
>  *  /usr/include/k3bmsfedit.h
>  *  /usr/include/k3baudiodatasourceiterator.h
>  *  /usr/include/k3bmovixjob.h
>  *  /usr/include/k3bjob.h
>  *  /usr/include/k3bpluginmanager.h
>  *  /usr/include/k3bthreadwidget.h
>  *  /usr/include/k3baudiofileanalyzerjob.h
>  *  /usr/include/k3bmediacache.h
>  *  /usr/include/k3bisooptions.h
>  *  /usr/include/k3baudiotrack.h
>  *  /usr/include/k3bcdtextvalidator.h
>  *

Re: [gentoo-user] What gives with all these file collisions?

2017-06-02 Thread Alan McKinnon 
On 02/06/2017 08:23, Alan Grimes wrote:
> I'm trying to emptytree my system because GCC update because I need to
> reboot because Nvidia-drivers segfaulted and broke a 2-month endurance
> run on my new mobo of my number theory code, set to use 15 hyperthreads
> and 25gb of ram...
> 
> 
> I'm getting lots of package failures due to file collisions and it's
> really starting to get annoying, I mean how am I supposed to fix:
> 
> without spending all day and all night cut-pasting filenames into
> another terminal and running rm on them...

Well, it won't be all day and all night. More like 5 minutes.
Less than 1 if you know how to use an editor, for, cat, rm and/or xargs.

Or you could use Ubuntu.

-- 
Alan McKinnon
alan.mckin...@gmail.com

[gentoo-user] What gives with all these file collisions?

2017-06-02 Thread Alan Grimes 
I'm trying to emptytree my system because GCC update because I need to
reboot because Nvidia-drivers segfaulted and broke a 2-month endurance
run on my new mobo of my number theory code, set to use 15 hyperthreads
and 25gb of ram...


I'm getting lots of package failures due to file collisions and it's
really starting to get annoying, I mean how am I supposed to fix:

without spending all day and all night cut-pasting filenames into
another terminal and running rm on them...


* Messages for package kde-apps/k3b-17.04.1:

 * 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 / ` 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 https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 *
 * Detected file collision(s):
 *
 *  /usr/share/doc/HTML/en/k3b/K3bAdvancedSettings.png
 *  /usr/share/doc/HTML/en/k3b/K3bDiskChoice.png
 *  /usr/share/doc/HTML/en/k3b/K3bMoreActions.png
 *  /usr/share/doc/HTML/en/k3b/index.cache.bz2
 *  /usr/share/doc/HTML/en/k3b/K3bSetVerify.png
 *  /usr/share/doc/HTML/en/k3b/K3bAddButton.png
 *  /usr/share/doc/HTML/en/k3b/K3bsetup.png
 *  /usr/share/icons/hicolor/48x48/apps/k3b.png
 *  /usr/share/icons/hicolor/scalable/apps/k3b.svgz
 *  /usr/share/icons/hicolor/128x128/apps/k3b.png
 *  /usr/share/icons/hicolor/64x64/apps/k3b.png
 *  /usr/share/icons/hicolor/16x16/apps/k3b.png
 *  /usr/share/icons/hicolor/22x22/apps/k3b.png
 *  /usr/share/icons/hicolor/32x32/apps/k3b.png
 *  /usr/share/mime/packages/x-k3b.xml
 *  /usr/include/k3bmd5job.h
 *  /usr/include/k3baudiojob.h
 *  /usr/include/k3bmixeddoc.h
 *  /usr/include/k3bdevicecombobox.h
 *  /usr/include/k3bthreadjob.h
 *  /usr/include/k3baudiodecoder.h
 *  /usr/include/k3bdevicehandler.h
 *  /usr/include/k3bactivepipe.h
 *  /usr/include/k3baudiozerodata.h
 *  /usr/include/k3bvcdoptions.h
 *  /usr/include/k3bblankingjob.h
 *  /usr/include/k3bintmapcombobox.h
 *  /usr/include/k3bvideodvdvideostream.h
 *  /usr/include/k3bfileitem.h
 *  /usr/include/k3baudiodoc.h
 *  /usr/include/k3baudiocdtrackdrag.h
 *  /usr/include/k3baudiocdtracksource.h
 *  /usr/include/k3b_export.h
 *  /usr/include/k3bdevice.h
 *  /usr/include/k3bplugin.h
 *  /usr/include/k3bthroughputestimator.h
 *  /usr/include/k3bfilesplitter.h
 *  /usr/include/k3bmedium.h
 *  /usr/include/k3bdevicetypes.h
 *  /usr/include/k3bversion.h
 *  /usr/include/k3bwavefilewriter.h
 *  /usr/include/k3bglobalsettings.h
 *  /usr/include/k3bdatadoc.h
 *  /usr/include/k3bvideodvdaudiostream.h
 *  /usr/include/k3binffilewriter.h
 *  /usr/include/k3bvcdjob.h
 *  /usr/include/k3bpluginconfigwidget.h
 *  /usr/include/k3bdvdformattingjob.h
 *  /usr/include/k3bdatajob.h
 *  /usr/include/k3bcdrecordwriter.h
 *  /usr/include/k3bfilesysteminfo.h
 *  /usr/include/k3bprocess.h
 *  /usr/include/k3bmetawriter.h
 *  /usr/include/k3biso9660.h
 *  /usr/include/k3bdiskinfo.h
 *  /usr/include/k3btocfilewriter.h
 *  /usr/include/k3bbusywidget.h
 *  /usr/include/k3bcore.h
 *  /usr/include/k3bverificationjob.h
 *  /usr/include/k3brawaudiodatasource.h
 *  /usr/include/k3bjobhandler.h
 *  /usr/include/k3bmovixdoc.h
 *  /usr/include/k3bvideodvdptt.h
 *  /usr/include/k3bdeviceselectiondialog.h
 *  /usr/include/k3bchecksumpipe.h
 *  /usr/include/k3bmsfedit.h
 *  /usr/include/k3baudiodatasourceiterator.h
 *  /usr/include/k3bmovixjob.h
 *  /usr/include/k3bjob.h
 *  /usr/include/k3bpluginmanager.h
 *  /usr/include/k3bthreadwidget.h
 *  /usr/include/k3baudiofileanalyzerjob.h
 *  /usr/include/k3bmediacache.h
 *  /usr/include/k3bisooptions.h
 *  /usr/include/k3baudiotrack.h
 *  /usr/include/k3bcdtextvalidator.h
 *  /usr/include/k3baudiocuefilewritingjob.h
 *  /usr/include/k3bmsf.h
 *  /usr/include/k3bdeviceglobals.h
 *  /usr/include/k3bbootitem.h
 *  /usr/include/k3baudiofile.h
 *  /usr/include/k3bcddb.h
 *  /usr/include/k3bcdcopyjob.h
 *  /usr/include/k3bvalidators.h
 *  /usr/include/k3bvcddoc.h
 *