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
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 dependency graph,
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 solution to me
Add a minimal SOCKSv5-over-UNIX-socket proxy to Portage, and start it
whenever ebuilds are started with network-sandbox enabled. Pass the
socket address in PORTAGE_SOCKS5_PROXY and DISTCC_SOCKS_PROXY variables.
The proxy can be used to escape the network sandbox whenever network
access is really
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
Add a minimal SOCKSv5-over-UNIX-socket proxy to Portage, and start it
whenever ebuilds are started with network-sandbox enabled. Pass the
socket address in PORTAGE_SOCKS5_PROXY and DISTCC_SOCKS_PROXY variables.
The proxy can be used to escape the network sandbox whenever network
access is really
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 key
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
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
On Sun, 25 Jan 2015 17:23:38 -0800
Zac Medico zmed...@gentoo.org wrote:
On 01/25/2015 02:34 PM, Michał Górny wrote:
diff --git a/bin/socks5-server.py b/bin/socks5-server.py
new file mode 100644
index 000..45cf76b
--- /dev/null
+++ b/bin/socks5-server.py
@@ -0,0 +1,233 @@
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ý ope...@tightmail.com:
I somehow thought that edit the overgrowing package.use
file upon each
Dnia 2015-01-21, o godz. 11:05:34
Michał Górny mgo...@gentoo.org 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.
Report bound socket name as requested by the protocol. Supports both
IPv4 and IPv6 sockets.
---
bin/socks5-server.py | 21 +
1 file changed, 17 insertions(+), 4 deletions(-)
diff --git a/bin/socks5-server.py b/bin/socks5-server.py
index 4795dcc..78a6751 100644
---
Dnia 2015-01-25, o godz. 12:29:54
Michał Górny mgo...@gentoo.org napisał(a):
Add a minimal SOCKSv5-over-UNIX-socket proxy to Portage, and start it
whenever ebuilds are started with network-sandbox enabled. Pass the
socket address in PORTAGE_SOCKS5_PROXY and DISTCC_SOCKS_PROXY variables.
The
Dnia 2015-01-25, o godz. 13:19:37
Michał Górny mgo...@gentoo.org napisał(a):
Report bound socket name as requested by the protocol. Supports both
IPv4 and IPv6 sockets.
Now included (with fixes) in:
[PATCH v2] Support escaping network-sandbox through SOCKSv5 proxy
--
Best regards,
Michał
On 01/25/2015 06:00 AM, Michał Górny wrote:
diff --git a/bin/socks5-server.py b/bin/socks5-server.py
new file mode 100644
index 000..c079018
--- /dev/null
+++ b/bin/socks5-server.py
@@ -0,0 +1,218 @@
+#!/usr/bin/env python
+# SOCKSv5 proxy server for network-sandbox
+# Copyright 2015
On 01/25/2015 06:00 AM, Michał Górny wrote:
diff --git a/bin/socks5-server.py b/bin/socks5-server.py
new file mode 100644
index 000..c079018
--- /dev/null
+++ b/bin/socks5-server.py
@@ -0,0 +1,218 @@
+#!/usr/bin/env python
+# SOCKSv5 proxy server for network-sandbox
+# Copyright 2015
On 01/25/2015 06:00 AM, Michał Górny wrote:
+ def __bool__(self):a
+ return self.socket_path is not None
You should also implement __nonzero__ for python-2.x.
--
Thanks,
Zac
Dnia 2015-01-25, o godz. 13:43:14
Zac Medico zmed...@gentoo.org napisał(a):
On 01/25/2015 06:00 AM, Michał Górny wrote:
diff --git a/bin/socks5-server.py b/bin/socks5-server.py
new file mode 100644
index 000..c079018
--- /dev/null
+++ b/bin/socks5-server.py
@@ -0,0 +1,218 @@
On 01/25/2015 02:34 PM, Michał Górny wrote:
diff --git a/bin/socks5-server.py b/bin/socks5-server.py
new file mode 100644
index 000..45cf76b
--- /dev/null
+++ b/bin/socks5-server.py
@@ -0,0 +1,233 @@
+#!/usr/bin/env python
+# SOCKSv5 proxy server for network-sandbox
+# Copyright 2015
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
On 01/25/2015 03:42 AM, Michał Górny wrote:
---
pym/portage/package/ebuild/doebuild.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pym/portage/package/ebuild/doebuild.py
b/pym/portage/package/ebuild/doebuild.py
index 0d71f01..050f6c4 100644
---
22 matches
Mail list logo