Void Linux discussion
 help / Atom feed
* xbps-src reposync error
@ 2018-12-25  5:23 Jonathan Schultz
  2018-12-25 14:05 ` Leah Neukirchen
  0 siblings, 1 reply; 5+ messages in thread
From: Jonathan Schultz @ 2018-12-25  5:23 UTC (permalink / raw)
  To: voidlinux

Hello all,

I'm a newcomer to voidlinux, which I'm running under Docker for the purpose of building some packages with musl.

Today I tried for the first time to build a package (fontconfig-devel) following the instructions here: https://wiki.voidlinux.org/Xbps-src

But when I get to the stage of trying to actually build the package (which at this stage is still completely unmodified) I get the following output:

> $ ./xbps-src pkg fontconfig-devel
> [*] Updating `https://alpha.de.repo.voidlinux.org/current/musl/x86_64-musl-repodata' ...
> x86_64-musl-repodata: 1636KB [avg rate: 811KB/s]
> [*] Updating `https://alpha.de.repo.voidlinux.org/current/musl/nonfree/x86_64-musl-repodata' ...
> [*] Updating `https://alpha.de.repo.voidlinux.org/current/x86_64-musl-repodata' ...
> ERROR: [reposync] failed to fetch file `https://alpha.de.repo.voidlinux.org/current/x86_64-musl-repodata': Not Found
> [*] Updating `https://alpha.de.repo.voidlinux.org/current/nonfree/x86_64-musl-repodata' ...
> ERROR: [reposync] failed to fetch file `https://alpha.de.repo.voidlinux.org/current/nonfree/x86_64-musl-repodata': Not Found
> [*] Updating `https://alpha.de.repo.voidlinux.org/current/aarch64/x86_64-musl-repodata' ...
> ERROR: [reposync] failed to fetch file `https://alpha.de.repo.voidlinux.org/current/aarch64/x86_64-musl-repodata': Not Found
> ERROR unshare (Operation not permitted)

It seems that for some reason the script is trying to sync with the wrong repository URL?

Many thanks for any help or pointers.

Jonathan

-- 
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/ebb0b4ac-7864-0757-7abb-71684df95d75%40schultz.la.
For more options, visit https://groups.google.com/d/optout.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: xbps-src reposync error
  2018-12-25  5:23 xbps-src reposync error Jonathan Schultz
@ 2018-12-25 14:05 ` Leah Neukirchen
  2018-12-26  5:34   ` Jonathan Schultz
  0 siblings, 1 reply; 5+ messages in thread
From: Leah Neukirchen @ 2018-12-25 14:05 UTC (permalink / raw)
  To: voidlinux

Jonathan Schultz <jonathan@schultz.la> writes:

> Hello all,
>
> I'm a newcomer to voidlinux, which I'm running under Docker for the
> purpose of building some packages with musl.
>
> Today I tried for the first time to build a package (fontconfig-devel)
> following the instructions here: https://wiki.voidlinux.org/Xbps-src
>
> But when I get to the stage of trying to actually build the package
> (which at this stage is still completely unmodified) I get the
> following output:
>
>> $ ./xbps-src pkg fontconfig-devel
>> [*] Updating
>> `https://alpha.de.repo.voidlinux.org/current/musl/x86_64-musl-repodata'
>> ...
>> x86_64-musl-repodata: 1636KB [avg rate: 811KB/s]
>> [*] Updating
>> `https://alpha.de.repo.voidlinux.org/current/musl/nonfree/x86_64-musl-repodata'
>> ...
>> [*] Updating
>> `https://alpha.de.repo.voidlinux.org/current/x86_64-musl-repodata'
>> ...
>> ERROR: [reposync] failed to fetch file
>> `https://alpha.de.repo.voidlinux.org/current/x86_64-musl-repodata':
>> Not Found
>> [*] Updating
>> `https://alpha.de.repo.voidlinux.org/current/nonfree/x86_64-musl-repodata'
>> ...
>> ERROR: [reposync] failed to fetch file
>> `https://alpha.de.repo.voidlinux.org/current/nonfree/x86_64-musl-repodata':
>> Not Found
>> [*] Updating
>> `https://alpha.de.repo.voidlinux.org/current/aarch64/x86_64-musl-repodata'
>> ...
>> ERROR: [reposync] failed to fetch file
>> `https://alpha.de.repo.voidlinux.org/current/aarch64/x86_64-musl-repodata':
>> Not Found

These errors are irrelevant.

>> ERROR unshare (Operation not permitted)

This is the actual error: unshare does not have setgid (or you are not
in the group).

> It seems that for some reason the script is trying to sync with the
> wrong repository URL?
>
> Many thanks for any help or pointers.
>
> Jonathan

hth,
-- 
Leah Neukirchen  <leah@vuxu.org>  http://leah.zone

-- 
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/871s65og6a.fsf%40vuxu.org.
For more options, visit https://groups.google.com/d/optout.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: xbps-src reposync error
  2018-12-25 14:05 ` Leah Neukirchen
@ 2018-12-26  5:34   ` Jonathan Schultz
  2018-12-26 15:30     ` Aleksey Tulinov
  0 siblings, 1 reply; 5+ messages in thread
From: Jonathan Schultz @ 2018-12-26  5:34 UTC (permalink / raw)
  To: Leah Neukirchen; +Cc: voidlinux

[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]

>> 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.

[-- Attachment #2: Type: text/html, Size: 2521 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: xbps-src reposync error
  2018-12-26  5:34   ` Jonathan Schultz
@ 2018-12-26 15:30     ` Aleksey Tulinov
  2018-12-27 14:40       ` Jonathan Schultz
  0 siblings, 1 reply; 5+ messages in thread
From: Aleksey Tulinov @ 2018-12-26 15:30 UTC (permalink / raw)
  To: Jonathan Schultz; +Cc: Leah Neukirchen, voidlinux

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.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: xbps-src reposync error
  2018-12-26 15:30     ` Aleksey Tulinov
@ 2018-12-27 14:40       ` Jonathan Schultz
  0 siblings, 0 replies; 5+ messages in thread
From: Jonathan Schultz @ 2018-12-27 14:40 UTC (permalink / raw)
  To: Aleksey Tulinov, Jonathan Schultz; +Cc: Leah Neukirchen, voidlinux

OK so I found the problem with proot. It's been fixed (very recently) upstream: https://github.com/proot-me/PRoot/pull/149 But as the discussion here: https://github.com/proot-me/PRoot/issues/127 reveals, they have some sticking points on making new releases, so the fix won't find its way downstream until those have been resolved.

I've applied the patches myself (using the work-around described below), and sure enough I can now use proot to build void packages as a non-privileged user under Docker.

If anyone thinks its worthwhile I can submit the patches as a pull request to void-linux, but otherwise probably just wait for things to work themselves out upstream.

Cheers, Jonathan

On 12/26/18 11:30 PM, Aleksey Tulinov wrote:
> 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>:
>>
>>Not sure whether to make a pull request with patches, or wait until a fixed version gets released upstream. Anyway it's documented for
>>>>> 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/378ee8b8-2fb6-b041-fc5c-9821166cc79f%40schultz.la.
For more options, visit https://groups.google.com/d/optout.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, back to index

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-12-25  5:23 xbps-src reposync error Jonathan Schultz
2018-12-25 14:05 ` Leah Neukirchen
2018-12-26  5:34   ` Jonathan Schultz
2018-12-26 15:30     ` Aleksey Tulinov
2018-12-27 14:40       ` Jonathan Schultz

Void Linux discussion

Archives are clonable: git clone --mirror http://inbox.vuxu.org/voidlinux

Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.voidlinux


AGPL code for this site: git clone https://public-inbox.org/ public-inbox