On Thu, 14 Sep 2017 08:28:23 +0100
Sergei Trofimovich wrote:
> On Wed, 13 Sep 2017 22:44:23 -0400
> Yury German wrote:
>
> Thank you! That's very helpful. A few clarifying questions below
> to be absolutely clear.
>
> > OK so let me repeat the comments that were made on @dev (and expand a bit
Update...
So I asked ntirpc upstream, and they do not intend to remain compatible with
sunrpc / libtirpc. Meaning we only have two RPC alternatives, one of which
will go away, and things get a lot easier.
> 1) About RPC.
https://wiki.gentoo.org/wiki/Project:Toolchain/RPC_implementation
^ pl
On Fri, Sep 22, 2017 at 7:43 PM, James McMechan
wrote:
> Hello,
> I thought a example of how a overlay sandbox could work was in order.
>
> ###
> # load the overlayfs filesystem for this test
> modprobe overlay
>
> # make the directories for the test
> mkdir -p /var/tmp/upper /var/tmp/work /mnt/g
On Sat, Sep 23, 2017 at 7:42 PM, Alec Warner wrote:
>
> We could try forcing failures (say, by not having / mounted as lowerdir, so
> syscalls against the rootfs would just fail as E_NOENT) but then we are
> still stuck with the tricky part; which is that sometimes things *do* need
> to read / wri
# Andreas K. Huettel (23 Sep 2017)
# Broken on Perl 5.26 (bug 623096), no fix in sight. No consumers.
# Removal in 30 days.
dev-perl/rpm-build-perl
pgpb_78D4NCaV.pgp
Description: OpenPGP digital signature
On Tue, 19 Sep 2017 17:23:50 +1200
Kent Fredric wrote:
> # Kent Fredric (19 Sep 2017)
> # Dead upstream, broken on Perl 5.26. Bugs #631302, #623116
> # Masked for removal in 30 days.
> dev-perl/Syntax-Highlight-Engine-Simple-Perl
Just as a follow up, this one got reneged on as some kind Gentoo
On 2017-09-22 22:26, Rich Freeman wrote:
> So, we're drifting in topic, but as long as we're coming up with
> nice-to-have utilities it would be lovely if our install CDs had
> something similar to systemd-nspawn to set up a container instead of a
> chroot for performing the install. If nothing el
On 2017-09-23 19:59, Rich Freeman wrote:
> A read-only container is a much simpler solution and generates the
> same kinds of errors as the current sandbox approach, but likely with
> fewer compatibility issues. I'm not really sure what tracing gets us
> that containers don't, other than having to
