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
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
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$ ^[[
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^
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/pytho
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 de
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
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
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
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 usi
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
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 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 w
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)
>
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.
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
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="bindis
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,
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
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
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 p
21 matches
Mail list logo
