From: Aleksey Tulinov <aleksey.tulinov@gmail.com>
To: Jonathan Schultz <jonathan@imatix.com>
Cc: Leah Neukirchen <leah@vuxu.org>, voidlinux@googlegroups.com
Subject: Re: xbps-src reposync error
Date: Wed, 26 Dec 2018 18:30:12 +0300 [thread overview]
Message-ID: <CAMteYTZHt8LOeBukf1ahZc1qyD7tbLU9oMD9n_=p43SzF6Oh9w@mail.gmail.com> (raw)
In-Reply-To: <CAN_yh5FT6-KeR4SDKT0=XU9=QoqaV18=cr3ust0wsksVsKTtnQ@mail.gmail.com>
I saw something similar before: https://github.com/Microsoft/WSL/issues/2981
Although it was WSL-related, user namespaces something something.
ср, 26 дек. 2018 г. в 08:34, Jonathan Schultz <jonathan@imatix.com>:
>
>
>> >> ERROR unshare (Operation not permitted)
>>
>> This is the actual error: unshare does not have setgid (or you are not
>> in the group).
>
>
> I believe the error is actually related to running xbps-src inside a Docker container, as setting setgid, or running as root make no difference. For the record, after much trial-and-error I have managed to find a combination that works. It required running the container as user root, and with both the --privileged and --cap-add=SYS_ADMIN options.
>
> However I have not entirely given up on finding a simpler solution. One promising route seemed to be to use the proot utility, which works in userspace, thus potentially avoiding all these permission problems. However when I try building using proot I see the following:
>
> > configure: creating ./config.status
> > config.status: creating MakefileI the following:
> > mv: cannot move './confT6XesZ/out' to 'Makefile': No such file or directory
> > config.status: error: could not create Makefileerrors
>
> I've had a bit of a go at reverse engineering the xbps-src build process, but found it all a bit confusing, so wondering if anyone might have seen something like this before.
>
> Thanks as always.
>
> --
> You received this message because you are subscribed to the Google Groups "voidlinux" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
> To post to this group, send email to voidlinux@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/CAN_yh5FT6-KeR4SDKT0%3DXU9%3DQoqaV18%3Dcr3ust0wsksVsKTtnQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To post to this group, send email to voidlinux@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/CAMteYTZHt8LOeBukf1ahZc1qyD7tbLU9oMD9n_%3Dp43SzF6Oh9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2018-12-26 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-25 5:23 Jonathan Schultz
2018-12-25 14:05 ` Leah Neukirchen
2018-12-26 5:34 ` Jonathan Schultz
2018-12-26 15:30 ` Aleksey Tulinov [this message]
2018-12-27 14:40 ` Jonathan Schultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMteYTZHt8LOeBukf1ahZc1qyD7tbLU9oMD9n_=p43SzF6Oh9w@mail.gmail.com' \
--to=aleksey.tulinov@gmail.com \
--cc=jonathan@imatix.com \
--cc=leah@vuxu.org \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).