On 20:57 Sat 24 Jan , Tom Gall wrote:
> Hi All,
>
> This is sort of a CFP in some ways but not quite that formal. I’ve been
> throttled back on arm64 for a bit as the hardware I’ve had access to has all
> been painfully remote and configured in ways that was less than optimal for
> massive
The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2015-01-25 23:59 UTC.
Removals:
dev-ruby/tmail 2015-01-21 05:05:30 mrueg
dev-ruby/refe 2015-01-21 05:05:57 mrueg
dev-
Least speaking for myself I can help you out starting Feb 15th, presuming all
the stars are in alignment. If someone else doesn’t help you before, please
mark it on your calendar and bug me again then cause I’m sure I’ll forget!
Best,
Tom
> On Jan 25, 2015, at 11:43 AM, Sebastian Pipping wrot
Hi!
I got a bug report for arm64 against the test suite of uriparser. If I
could get a temporary arm64 shell somewhere, that could help me
understand the issue.
Best,
Sebastian
Hi,
Michał Górny wrote:
> I see two generic approaches possible here:
>
> 1. proxying distcc from within the build environment, or
>
> 2. moving distcc-spawned processes back to parent's namespace.
>
>
> distcc client/server solution
> -
>
> The most obvious soluti
On 01/24/15 21:57, Tom Gall wrote:
Hi All,
This is sort of a CFP in some ways but not quite that formal. I’ve been
throttled back on arm64 for a bit as the hardware I’ve had access to has all
been painfully remote and configured in ways that was less than optimal for
massive key wording effor
Dnia 2015-01-21, o godz. 11:05:34
Michał Górny napisał(a):
> Generic proxy solution
> --
>
> The simplest solution so far seems to be setting a generic SOCKS proxy
> inside the build environment, and wrapping distcc so that it will use
> it for network access.
>
> Unless we
On Sun, 25 Jan 2015 04:29:43 + (UTC)
Duncan <1i5t5.dun...@cox.net> wrote:
> Alexey Mishustin posted on Sat, 24 Jan 2015 21:54:06 +0400 as
> excerpted:
>
> > 2015-01-20 14:42 GMT+04:00 Róbert Čerňanský :
> >>
> >> I somehow thought that edit the overgrowing package.use
> >> file upon each emer
On 25/01/15 03:57, Tom Gall wrote:
Hi All,
This is sort of a CFP in some ways but not quite that formal. I’ve
been throttled back on arm64 for a bit as the hardware I’ve had access
to has all been painfully remote and configured in ways that was less
than optimal for massive key wording efforts
On 01/22/2015 10:19, Peter Stuge wrote:
> Joshua Kinard wrote:
>> Using seed stage3 stages I built 6 months ago (but never released due
>> to getting sidetracked), I run into errors like this:
>>
>> !!! Multiple package instances within a single package slot have been pulled
>> !!! into the depende
10 matches
Mail list logo
