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] How do I turn off ansi (colour) codes in ... script output

2017-06-02 Thread R0b0t1 
On Fri, Jun 2, 2017 at 7:12 PM, R0b0t1  wrote:
> On Fri, Jun 2, 2017 at 6:06 PM, Mick  wrote:
>> Hi All,
>>
>> Walter had posted a message about ANSI codes showing up in portage output.  I
>> am getting the same when I run /usr/bin/script and examine the contents of 
>> the
>> resultant file with a text editor; e.g. in Vim I get:
>>
>> ^[[0;32m~ ^[[35m$ ^[[0mtest^H^[[K^H^[[K^H^[[K^H^[[Kecho S^H^[[K|^H^[[K$term^M
>>
>> but when I use less I can see:
>>
>> ~ $ echo $TERM
>>
>> Is there a way of suppressing these characters in gedit, kwrite, vim, etc.?
>> --
>> Regards,
>> Mick
>
> The proper way to approach this is to disable coloring in the program
> generating your output. If there is no flag for it, you can try
> setting your terminal capabilities such that color is not supported
> (e.g. TERM=xterm-old, possibly unsupported on BSDs). However for some
> poorly written programs that may not work. Lastly, you can strip the
> escape sequences from the output.
>
> See http://www.andre-simon.de/doku/ansifilter/en/ansifilter.php if you
> are interested in the latter option. This seems the easiest to do if
> you don't mind the extra step.

Apologies - you should also check your terminal emulator's
documentation to see if color escapes can be disabled as an
alternative to setting TERM, but this is probably the worst of the
three options.

Re: [gentoo-user] How do I turn off ansi (colour) codes in ... script output

2017-06-02 Thread R0b0t1 
On Fri, Jun 2, 2017 at 6:06 PM, Mick  wrote:
> Hi All,
>
> Walter had posted a message about ANSI codes showing up in portage output.  I
> am getting the same when I run /usr/bin/script and examine the contents of the
> resultant file with a text editor; e.g. in Vim I get:
>
> ^[[0;32m~ ^[[35m$ ^[[0mtest^H^[[K^H^[[K^H^[[K^H^[[Kecho S^H^[[K|^H^[[K$term^M
>
> but when I use less I can see:
>
> ~ $ echo $TERM
>
> Is there a way of suppressing these characters in gedit, kwrite, vim, etc.?
> --
> Regards,
> Mick

The proper way to approach this is to disable coloring in the program
generating your output. If there is no flag for it, you can try
setting your terminal capabilities such that color is not supported
(e.g. TERM=xterm-old, possibly unsupported on BSDs). However for some
poorly written programs that may not work. Lastly, you can strip the
escape sequences from the output.

See http://www.andre-simon.de/doku/ansifilter/en/ansifilter.php if you
are interested in the latter option. This seems the easiest to do if
you don't mind the extra step.

[gentoo-user] How do I turn off ansi (colour) codes in ... script output

2017-06-02 Thread Mick 
Hi All,

Walter had posted a message about ANSI codes showing up in portage output.  I 
am getting the same when I run /usr/bin/script and examine the contents of the 
resultant file with a text editor; e.g. in Vim I get:

^[[0;32m~ ^[[35m$ ^[[0mtest^H^[[K^H^[[K^H^[[K^H^[[Kecho S^H^[[K|^H^[[K$term^M

but when I use less I can see:

~ $ echo $TERM

Is there a way of suppressing these characters in gedit, kwrite, vim, etc.?
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

[gentoo-user] app-office/taskcoach-1.4.3-r1 fails to launch

2017-06-02 Thread Mick 
I seem to be having a deja vu with this application.  It won't launch and when 
started from a terminal it spews out this lot:

==
Traceback (most recent call last):
  File "/usr/lib/python-exec/python2.7/taskcoach.py", line 72, in 
start()
  File "/usr/lib/python-exec/python2.7/taskcoach.py", line 63, in start
app = application.Application(options, args)
  File "/usr/lib64/python2.7/site-
packages/taskcoachlib/patterns/singleton.py", line 29, in __call__
class_.instance = super(Singleton, class_).__call__(*args, **kwargs)
  File "/usr/lib64/python2.7/site-
packages/taskcoachlib/application/application.py", line 114, in __init__
self.initTwisted()
  File "/usr/lib64/python2.7/site-
packages/taskcoachlib/application/application.py", line 156, in initTwisted
from twisted.internet import wxreactor
  File "/usr/lib64/python2.7/site-packages/twisted/internet/wxreactor.py", 
line 35, in 
from twisted.internet import _threadedselect
  File "/usr/lib64/python2.7/site-
packages/twisted/internet/_threadedselect.py", line 62, in 
from twisted.internet import posixbase
  File "/usr/lib64/python2.7/site-packages/twisted/internet/posixbase.py", 
line 24, in 
from twisted.internet import error, udp, tcp
  File "/usr/lib64/python2.7/site-packages/twisted/internet/tcp.py", line 29, 
in 
from twisted.internet._newtls import (
  File "/usr/lib64/python2.7/site-packages/twisted/internet/_newtls.py", line 
21, in 
from twisted.protocols.tls import TLSMemoryBIOFactory, 
TLSMemoryBIOProtocol
  File "/usr/lib64/python2.7/site-packages/twisted/protocols/tls.py", line 40, 
in 
from OpenSSL.SSL import Error, ZeroReturnError, WantReadError
  File "/usr/lib64/python2.7/site-packages/OpenSSL/__init__.py", line 8, in 

from OpenSSL import rand, crypto, SSL
  File "/usr/lib64/python2.7/site-packages/OpenSSL/crypto.py", line 13, in 

from cryptography.hazmat.primitives.asymmetric import dsa, rsa
  File "/usr/lib64/python2.7/site-
packages/cryptography/hazmat/primitives/asymmetric/rsa.py", line 14, in 

from cryptography.hazmat.backends.interfaces import RSABackend
  File "/usr/lib64/python2.7/site-
packages/cryptography/hazmat/backends/__init__.py", line 7, in 
import pkg_resources
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 
72, in 
import packaging.requirements
  File "/usr/lib64/python2.7/site-packages/packaging/requirements.py", line 
59, in 
MARKER_EXPR = originalTextFor(MARKER_EXPR())("marker")
TypeError: __call__() takes exactly 2 arguments (1 given)
=

This problem exists with x86 and amd64 installations.  I posted a bug, but a 
dev kindly tested it and it worked fine on his system.  So the bug was closed 
with 'works for some'.

I've rebuilt dev-python/wxpython-3.0.2.0, as well as taskcoach itself, but it 
still refuses to launch.  Last time I recall having similar problems I ended 
up removing TaskCoach.ini from the user's home directory and the application 
was able to launch.  This workaround won't work this time.

Can you see something above that can point me to a solution?

PS. Is there another application, which will work as well as taskcoach for 
keeping a record of billing work and charges?

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

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] conflict with same package, same USE

2017-06-02 Thread Sam Jorna 
On 03/06/17 00:39, Rich Freeman wrote:
> On Fri, Jun 2, 2017 at 9:17 AM, Sam Jorna  wrote:
>> On 02/06/17 23:09, Rich Freeman wrote:
>>> The stage3 make.conf shouldn't include this.  Now, if you copied your
>>> make.conf from some other source like a LiveCD then that could explain
>>> where it came from.  The flag was actually invented mainly for things
>>> like LiveCDs, and these are all built using USE=bindist (we couldn't
>>> legally distribute them otherwise).
>>
>> The stage3 make.conf does include USE=bindist by default, as it includes
>> packages affected by this flag (specifically openssh and openssl). It's
>> required, as I understand, because the stage3 does distribute binaries
>> of these packages, thus must have the patent-encumbered parts disabled.
>>
> 
> Interesting.  It looks like we do set that in make.conf by default now
> - that might be a change from the last time I did an install as I
> didn't have to remove this in the past.

Indeed. I'm not sure when it changed, though it's been this way for a
while. How long that is as compared to your last build... :)

> There is no legal requirement to set bindist in the make.conf
> installed by the stage3.
> 
> There absolutely is a legal requirement to set bindist in the
> make.conf used to BUILD the stage3.  The two do not need to be the
> same.

This is a good point - it's a reasonably common question in #gentoo (or,
more commonly, the conflict it can generate). I think it finds its way
into the stage3's make.conf because it's essentially just the make.conf
used by catalyst, and there's no other significant pressure to change it
since it's bare-bones already, but it might be useful to get it changed.

-- 
Sam Jorna (wraeth) 
GnuPG Key: D6180C26



signature.asc
Description: OpenPGP digital signature

Re: [gentoo-user] conflict with same package, same USE

2017-06-02 Thread Rich Freeman 
On Fri, Jun 2, 2017 at 9:17 AM, Sam Jorna  wrote:
> On 02/06/17 23:09, Rich Freeman wrote:
>> The stage3 make.conf shouldn't include this.  Now, if you copied your
>> make.conf from some other source like a LiveCD then that could explain
>> where it came from.  The flag was actually invented mainly for things
>> like LiveCDs, and these are all built using USE=bindist (we couldn't
>> legally distribute them otherwise).
>
> The stage3 make.conf does include USE=bindist by default, as it includes
> packages affected by this flag (specifically openssh and openssl). It's
> required, as I understand, because the stage3 does distribute binaries
> of these packages, thus must have the patent-encumbered parts disabled.
>

Interesting.  It looks like we do set that in make.conf by default now
- that might be a change from the last time I did an install as I
didn't have to remove this in the past.

There is no legal requirement to set bindist in the make.conf
installed by the stage3.

There absolutely is a legal requirement to set bindist in the
make.conf used to BUILD the stage3.  The two do not need to be the
same.

-- 
Rich

Re: [gentoo-user] conflict with same package, same USE

2017-06-02 Thread Hogren 
I create my make.conf, it's not a copy. (It's make the error more
stupid,  ^^, so be it).


Thank you !

Hogren
On 02/06/2017 15:17, Sam Jorna wrote:
> On 02/06/17 23:09, Rich Freeman wrote:
>> The stage3 make.conf shouldn't include this.  Now, if you copied your
>> make.conf from some other source like a LiveCD then that could explain
>> where it came from.  The flag was actually invented mainly for things
>> like LiveCDs, and these are all built using USE=bindist (we couldn't
>> legally distribute them otherwise).
> The stage3 make.conf does include USE=bindist by default, as it includes
> packages affected by this flag (specifically openssh and openssl). It's
> required, as I understand, because the stage3 does distribute binaries
> of these packages, thus must have the patent-encumbered parts disabled.
>

Re: [gentoo-user] conflict with same package, same USE

2017-06-02 Thread Sam Jorna 
On 02/06/17 23:09, Rich Freeman wrote:
> The stage3 make.conf shouldn't include this.  Now, if you copied your
> make.conf from some other source like a LiveCD then that could explain
> where it came from.  The flag was actually invented mainly for things
> like LiveCDs, and these are all built using USE=bindist (we couldn't
> legally distribute them otherwise).

The stage3 make.conf does include USE=bindist by default, as it includes
packages affected by this flag (specifically openssh and openssl). It's
required, as I understand, because the stage3 does distribute binaries
of these packages, thus must have the patent-encumbered parts disabled.

-- 
Sam Jorna (wraeth) 
GnuPG Key: D6180C26



signature.asc
Description: OpenPGP digital signature

Re: [gentoo-user] conflict with same package, same USE

2017-06-02 Thread Rich Freeman 
On Fri, Jun 2, 2017 at 8:55 AM, Daniel Frey  wrote:
> On 06/02/2017 03:08 AM, Hogren wrote:
>> Thank you all for the help.
>>
>> I saw a "bindist" in my global USE flag !
>>
>> I really don't remember when I had that. May be when I saw it for the
>> first time, I said to me "Hey a weak protocol (EC)? disable it !" …
>>
>> For the moment, no more problem !
>>
>>
>> Thank you 
>>
>
> You probably didn't put it there. When I built a new machine some time
> ago I was having similar issues and noticed that as a default in make.conf.
>

The stage3 make.conf shouldn't include this.  Now, if you copied your
make.conf from some other source like a LiveCD then that could explain
where it came from.  The flag was actually invented mainly for things
like LiveCDs, and these are all built using USE=bindist (we couldn't
legally distribute them otherwise).

-- 
Rich

Re: [gentoo-user] conflict with same package, same USE

2017-06-02 Thread Daniel Frey 
On 06/02/2017 03:08 AM, Hogren wrote:
> Thank you all for the help.
> 
> I saw a "bindist" in my global USE flag !
> 
> I really don't remember when I had that. May be when I saw it for the
> first time, I said to me "Hey a weak protocol (EC)? disable it !" …
> 
> For the moment, no more problem !
> 
> 
> Thank you 
> 

You probably didn't put it there. When I built a new machine some time
ago I was having similar issues and noticed that as a default in make.conf.

Dan

Re: [gentoo-user] conflict with same package, same USE

2017-06-02 Thread Hogren 
Thank you all for the help.

I saw a "bindist" in my global USE flag !

I really don't remember when I had that. May be when I saw it for the
first time, I said to me "Hey a weak protocol (EC)? disable it !" …

For the moment, no more problem !


Thank you 


On 02/06/2017 11:34, Kent Fredric wrote:
> On Fri, 2 Jun 2017 10:55:51 +0200
> Hogren  wrote:
>
>> dev-libs/openssl:0
>>
>>   (dev-libs/openssl-1.0.2k:0/0::gentoo, ebuild scheduled for merge)
>> pulled in by
>> dev-libs/openssl:0[bindist=] required by
>> (dev-qt/qtnetwork-5.6.2:5/5.6::gentoo, ebuild scheduled for merge)
>>   
>>  
>>   
>>
>>
>>   (dev-libs/openssl-1.0.2k:0/0::gentoo, installed) pulled in by
>> >=dev-libs/openssl-0.9.8f:0[bindist=] required by  
>> (net-misc/openssh-7.3_p1-r7:0/0::gentoo, installed)
>>
> The important thing here is not the version, but the use requirement in
> the [ ]
>
> Consulting `man 5 ebuild` , 
>
>>  foo[bar=]  bar? ( foo[bar] ) !bar? ( foo[-bar] )
> So, this means that:
>
>dev-libs/openssl:0[bindist=]  required by 
> net-misc/openssh-7.3_p1-r7:0/0::gentoo
>
> Interprets as:
>
>is net-misc/openssh built with USE=bindist?
>   yes ->
>  require dev-libs/openssl be built with USE=bindist
>   no ->
>  require dev-libs/openssl be built WITHOUT USE=bindist
>
> In short, the USE setting for openssl and openssh must have the same
> value for USE=bindist
>
> And also, dev-qt/qtnetwork also has the same constraint.
>
> Thus, you need to configure the USE=bindist flag for all of:
>
>   dev-libs/openssl
>   dev-qt/qtnetwork
>   net-misc/openssh
>
> Either be all USE=bindist or USE=-bindist
>
> *hopefully* that's enough information for you to solve your issue,
> but if not, I can expand upon request, if you state what parts you
> don't understand
> :)
>

Re: [gentoo-user] conflict with same package, same USE

2017-06-02 Thread Kent Fredric 
On Fri, 2 Jun 2017 10:55:51 +0200
Hogren  wrote:

> dev-libs/openssl:0
> 
>   (dev-libs/openssl-1.0.2k:0/0::gentoo, ebuild scheduled for merge)
> pulled in by
> dev-libs/openssl:0[bindist=] required by
> (dev-qt/qtnetwork-5.6.2:5/5.6::gentoo, ebuild scheduled for merge)
>   
>   
>  
> 
> 
>   (dev-libs/openssl-1.0.2k:0/0::gentoo, installed) pulled in by
> >=dev-libs/openssl-0.9.8f:0[bindist=] required by  
> (net-misc/openssh-7.3_p1-r7:0/0::gentoo, installed)
>

The important thing here is not the version, but the use requirement in
the [ ]

Consulting `man 5 ebuild` , 

>  foo[bar=]  bar? ( foo[bar] ) !bar? ( foo[-bar] )

So, this means that:

   dev-libs/openssl:0[bindist=]  required by 
net-misc/openssh-7.3_p1-r7:0/0::gentoo

Interprets as:

   is net-misc/openssh built with USE=bindist?
  yes ->
 require dev-libs/openssl be built with USE=bindist
  no ->
 require dev-libs/openssl be built WITHOUT USE=bindist

In short, the USE setting for openssl and openssh must have the same
value for USE=bindist

And also, dev-qt/qtnetwork also has the same constraint.

Thus, you need to configure the USE=bindist flag for all of:

  dev-libs/openssl
  dev-qt/qtnetwork
  net-misc/openssh

Either be all USE=bindist or USE=-bindist

*hopefully* that's enough information for you to solve your issue,
but if not, I can expand upon request, if you state what parts you
don't understand
:)



pgpjEyLDkfATC.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] conflict with same package, same USE

2017-06-02 Thread Neil Bothwick 
On Fri, 2 Jun 2017 10:59:51 +0200, Hogren wrote:

> Sorry for the lack of courtesy !!
> 
> I hope that someone can help me.

You've already been given a useful pointer, disable bindist globally.
Unless you are building a distro for redistribution, there is no need
for this flag to be on globally. 

> Thank you very very much for your help !!
> 
> 
> Hogren
> 
> 
> On 02/06/2017 10:55, Hogren wrote:
> > Hello list,
> >
> >
> > It's me again about conflicts.
> >
> >
> > I don't understand this conflict, the two needed openssl are the same.
> > Actually, I don't see the difference.
> >
> >
> > gnugnu # emerge --verbose-conflict @preserved-rebuild
> > Calculating dependencies... done!
> > [ebuild   R] dev-libs/openssl-1.0.2k  USE="bindist*"
> > [ebuild   R] sys-devel/binutils-2.25.1-r1
> > [ebuild U  ] sys-libs/talloc-2.1.9 [2.1.5]
> > [ebuild U  ] sys-libs/tdb-1.3.13 [1.3.8]
> > [ebuild U  ] sys-libs/tevent-0.9.31-r1 [0.9.28]
> > [ebuild  N ] dev-python/subunit-1.2.0-r1  USE="-static-libs
> > {-test}" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python2_7
> > python3_4 (-pypy) (-pypy3) (-python3_5) (-python3_6)"
> > [ebuild  N ] dev-qt/qtnetwork-5.6.2  USE="bindist ssl -connman
> > -debug -libproxy -networkmanager {-test}"
> > [ebuild U  ] sys-libs/ldb-1.1.29-r1 [1.1.26] USE="ldap%* python%*"
> > [ebuild   R] dev-qt/qtxmlpatterns-5.6.2
> > [ebuild   R] dev-qt/qtwebkit-5.6.2
> > [ebuild   R   ~] net-misc/teamviewer-9.0.32150
> > [ebuild U  ] net-fs/samba-4.5.10 [4.2.14] USE="-gpg%
> > (-system-heimdal) -zeroconf%"
> > [ebuild   R] media-gfx/blender-2.72b-r4
> > [ebuild   R   ~] media-gfx/wkhtmltopdf-0.12.4
> > [ebuild U ~] www-client/firefox-53.0.3 [52.0.1-r1]
> > [ebuild U  ] app-office/libreoffice-5.2.7.2 [5.2.3.3-r1]
> > PYTHON_SINGLE_TARGET="python3_4* -python2_7*"
> > [ebuild   R] net-ftp/filezilla-3.12.0.2
> > [ebuild   R] media-gfx/gimp-2.8.14-r2
> > [ebuild  N ] x11-plugins/enigmail-1.9.6.1-r1
> > [ebuild U  ] mail-client/thunderbird-45.8.0 [45.7.0]
> > [blocks b  ] x11-plugins/enigmail ("x11-plugins/enigmail" is
> > blocking mail-client/thunderbird-45.7.0)
> >
> > !!! Multiple package instances within a single package slot have been
> > pulled !!! into the dependency graph, resulting in a slot conflict:
> >
> > dev-libs/openssl:0
> >
> >   (dev-libs/openssl-1.0.2k:0/0::gentoo, ebuild scheduled for merge)
> > pulled in by
> > dev-libs/openssl:0[bindist=] required by
> > (dev-qt/qtnetwork-5.6.2:5/5.6::gentoo, ebuild scheduled for merge)
> >   
> > 
> >
> >
> >
> >   (dev-libs/openssl-1.0.2k:0/0::gentoo, installed) pulled in by  
> > >=dev-libs/openssl-0.9.8f:0[bindist=] required by  
> > (net-misc/openssh-7.3_p1-r7:0/0::gentoo, installed)
> >
> > 
> > 
> >
> >
> >
> > Hogren
> >
> >
> >  
> 
> 




-- 
Neil Bothwick

Suicidal twin kills sister by mistake!


pgpeyfMUEwPRJ.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] conflict with same package, same USE

2017-06-02 Thread Hogren 
Sorry for the lack of courtesy !!

I hope that someone can help me.


Thank you very very much for your help !!


Hogren


On 02/06/2017 10:55, Hogren wrote:
> Hello list,
>
>
> It's me again about conflicts.
>
>
> I don't understand this conflict, the two needed openssl are the same.
> Actually, I don't see the difference.
>
>
> gnugnu # emerge --verbose-conflict @preserved-rebuild
> Calculating dependencies... done!
> [ebuild   R] dev-libs/openssl-1.0.2k  USE="bindist*"
> [ebuild   R] sys-devel/binutils-2.25.1-r1
> [ebuild U  ] sys-libs/talloc-2.1.9 [2.1.5]
> [ebuild U  ] sys-libs/tdb-1.3.13 [1.3.8]
> [ebuild U  ] sys-libs/tevent-0.9.31-r1 [0.9.28]
> [ebuild  N ] dev-python/subunit-1.2.0-r1  USE="-static-libs {-test}"
> ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python2_7 python3_4 (-pypy)
> (-pypy3) (-python3_5) (-python3_6)"
> [ebuild  N ] dev-qt/qtnetwork-5.6.2  USE="bindist ssl -connman
> -debug -libproxy -networkmanager {-test}"
> [ebuild U  ] sys-libs/ldb-1.1.29-r1 [1.1.26] USE="ldap%* python%*"
> [ebuild   R] dev-qt/qtxmlpatterns-5.6.2
> [ebuild   R] dev-qt/qtwebkit-5.6.2
> [ebuild   R   ~] net-misc/teamviewer-9.0.32150
> [ebuild U  ] net-fs/samba-4.5.10 [4.2.14] USE="-gpg%
> (-system-heimdal) -zeroconf%"
> [ebuild   R] media-gfx/blender-2.72b-r4
> [ebuild   R   ~] media-gfx/wkhtmltopdf-0.12.4
> [ebuild U ~] www-client/firefox-53.0.3 [52.0.1-r1]
> [ebuild U  ] app-office/libreoffice-5.2.7.2 [5.2.3.3-r1]
> PYTHON_SINGLE_TARGET="python3_4* -python2_7*"
> [ebuild   R] net-ftp/filezilla-3.12.0.2
> [ebuild   R] media-gfx/gimp-2.8.14-r2
> [ebuild  N ] x11-plugins/enigmail-1.9.6.1-r1
> [ebuild U  ] mail-client/thunderbird-45.8.0 [45.7.0]
> [blocks b  ] x11-plugins/enigmail ("x11-plugins/enigmail" is
> blocking mail-client/thunderbird-45.7.0)
>
> !!! Multiple package instances within a single package slot have been pulled
> !!! into the dependency graph, resulting in a slot conflict:
>
> dev-libs/openssl:0
>
>   (dev-libs/openssl-1.0.2k:0/0::gentoo, ebuild scheduled for merge)
> pulled in by
> dev-libs/openssl:0[bindist=] required by
> (dev-qt/qtnetwork-5.6.2:5/5.6::gentoo, ebuild scheduled for merge)
>   
>   
>  
>
>
>   (dev-libs/openssl-1.0.2k:0/0::gentoo, installed) pulled in by
> >=dev-libs/openssl-0.9.8f:0[bindist=] required by
> (net-misc/openssh-7.3_p1-r7:0/0::gentoo, installed)
>
>   
>   
>
>
>
> Hogren
>
>
>

[gentoo-user] conflict with same package, same USE

2017-06-02 Thread Hogren 
Hello list,


It's me again about conflicts.


I don't understand this conflict, the two needed openssl are the same.
Actually, I don't see the difference.


gnugnu # emerge --verbose-conflict @preserved-rebuild
Calculating dependencies... done!
[ebuild   R] dev-libs/openssl-1.0.2k  USE="bindist*"
[ebuild   R] sys-devel/binutils-2.25.1-r1
[ebuild U  ] sys-libs/talloc-2.1.9 [2.1.5]
[ebuild U  ] sys-libs/tdb-1.3.13 [1.3.8]
[ebuild U  ] sys-libs/tevent-0.9.31-r1 [0.9.28]
[ebuild  N ] dev-python/subunit-1.2.0-r1  USE="-static-libs {-test}"
ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python2_7 python3_4 (-pypy)
(-pypy3) (-python3_5) (-python3_6)"
[ebuild  N ] dev-qt/qtnetwork-5.6.2  USE="bindist ssl -connman
-debug -libproxy -networkmanager {-test}"
[ebuild U  ] sys-libs/ldb-1.1.29-r1 [1.1.26] USE="ldap%* python%*"
[ebuild   R] dev-qt/qtxmlpatterns-5.6.2
[ebuild   R] dev-qt/qtwebkit-5.6.2
[ebuild   R   ~] net-misc/teamviewer-9.0.32150
[ebuild U  ] net-fs/samba-4.5.10 [4.2.14] USE="-gpg%
(-system-heimdal) -zeroconf%"
[ebuild   R] media-gfx/blender-2.72b-r4
[ebuild   R   ~] media-gfx/wkhtmltopdf-0.12.4
[ebuild U ~] www-client/firefox-53.0.3 [52.0.1-r1]
[ebuild U  ] app-office/libreoffice-5.2.7.2 [5.2.3.3-r1]
PYTHON_SINGLE_TARGET="python3_4* -python2_7*"
[ebuild   R] net-ftp/filezilla-3.12.0.2
[ebuild   R] media-gfx/gimp-2.8.14-r2
[ebuild  N ] x11-plugins/enigmail-1.9.6.1-r1
[ebuild U  ] mail-client/thunderbird-45.8.0 [45.7.0]
[blocks b  ] x11-plugins/enigmail ("x11-plugins/enigmail" is
blocking mail-client/thunderbird-45.7.0)

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

dev-libs/openssl:0

  (dev-libs/openssl-1.0.2k:0/0::gentoo, ebuild scheduled for merge)
pulled in by
dev-libs/openssl:0[bindist=] required by
(dev-qt/qtnetwork-5.6.2:5/5.6::gentoo, ebuild scheduled for merge)
  

   


  (dev-libs/openssl-1.0.2k:0/0::gentoo, installed) pulled in by
>=dev-libs/openssl-0.9.8f:0[bindist=] required by
(net-misc/openssh-7.3_p1-r7:0/0::gentoo, installed)
   





Hogren

Re: [gentoo-user] nodejs and qtnetwork = conflict on bindist openssl USE flag

2017-06-02 Thread Hogren 


On 02/06/2017 07:49, Alexander Kapshuk wrote:
> On Fri, Jun 2, 2017 at 8:35 AM, Hogren  wrote:
>> Hello list,
>>
>> When I try to update my system, I have many conflicts.
>>
>> A first conflict which about I need help is this:
>>
>> dev-libs/openssl:0
>>
>>   (dev-libs/openssl-1.0.2k:0/0::gentoo, installed) pulled in by
>> >=dev-libs/openssl-1.0.2g:0=[-bindist] required by
>> (net-libs/nodejs-7.10.0:0/0::gentoo, installed)
>>
>> 
>>
>> >=dev-libs/openssl-1.0.2g:0/0=[-bindist] required by
>> (net-libs/nodejs-7.10.0:0/0::gentoo, installed)
>>
>> 
>>
>> >=dev-libs/openssl-0.9.8f:0[bindist=] required by
>> (net-misc/openssh-7.3_p1-r7:0/0::gentoo, installed)
>>
>> 
>>
>>
>>   (dev-libs/openssl-1.0.2k:0/0::gentoo, ebuild scheduled for merge)
>> pulled in by
>> dev-libs/openssl:0[bindist=] required by
>> (dev-qt/qtnetwork-5.6.2:5/5.6::gentoo, ebuild scheduled for merge)
>>
>> 
>>
>>
>>
>>
>> I tried de make "-ssl" USE flag to nodejs, but I have an error at the
>> emerge time :
>>
> Configuring source in
>> /var/tmp/portage/net-libs/nodejs-7.10.0/work/node-v7.10.0 ...
>> Error: --without-ssl is incompatible with --shared-openssl
>>
>>
>> I look in the ebuild and I see there is apparently no method to drop the
>> --shared-openssl option. So I can't use "-ssl".
>>
>>
>> Did anybody have already the problem ?
>>
>>
>> Thank you for help !
>>
>>
>> Hogren
>>
>>
> On my system, I overcame that by disabling the 'bindist' USE flag
> globally in /etc/portage/make.conf.
>
Ok thanks. With little more search, I find a bug report about that :
https://bugs.gentoo.org/show_bug.cgi?id=615448

I will try without ~amd64 in my accept_keywords file. And after with
this global use flag.

Thanks.


Hogren

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
 *