Em dezembro 22, 2017 15:01 Leonid Isaev via arch-general escreveu:
I'm sorry for an unrelated question, but why is it really necessary to make a
new container for each pkg? It seems lots of unnecessary copies (I think
rsync(1) call in makechrootpkg doesn't do hardlinks)...
A new container is
On 12/20/2017 09:45 AM, David Rosenstrauch wrote:
> More of a workaround than a solution, but I stopped using grub
> altogether once they upgraded to grub2. (The complexity of the grub2
> config file as compared to the simplicity of the grub-legacy menu.lst
> file is what eventually turned me away
On Fri, Dec 22, 2017 at 02:36:17PM -0300, Giancarlo Razzolini via arch-general
wrote:
> Em dezembro 22, 2017 13:55 Manuel Reimer escreveu:
> > On 12/22/2017 03:17 PM, Giancarlo Razzolini via arch-general wrote:
> > I have an existing build system that I call with root permissions and
> > from this
Em dezembro 22, 2017 14:15 David Rosenstrauch escreveu:
1) Wifi router reports an IPv6 address on both the WAN and the LAN
sides. (In the 2607: range.)
That's a global address range, for sure.
2) Mac desktop behind the router successfully gets assigned an ipv6
address.
3) Linux laptop (run
Em dezembro 22, 2017 13:55 Manuel Reimer escreveu:
On 12/22/2017 03:17 PM, Giancarlo Razzolini via arch-general wrote:
Well, so far you said you want to autobuild some packages and that it
MUST run
as root, with no good reason why.
I have a set of PKGBUILD's (around 40) and a self-made "build
Having a weird situation going on with IPv6. Every machine on my
network can successfully get an ipv6 address except for one. (My main
server.) What's even weirder is that ipv6 was working on that machine
up until probably about a week ago. Not sure what the problem is, and
hoping someone h
On 12/22/2017 03:17 PM, Giancarlo Razzolini via arch-general wrote:
Well, so far you said you want to autobuild some packages and that it
MUST run
as root, with no good reason why.
I have a set of PKGBUILD's (around 40) and a self-made "build system":
http://repo-make.tuxfamily.org/
The auto
Hi,
just a guess, since you've mentioned `dd` - did you do
> # wipefs -a /dev/sdX
where X is the USB stick? Distro ISOs always left the USB sticks in an
unusable state until I execute the above.
On 21.12.2017 09:27, n...@contrepoison.ch wrote:
> Le 2017-12-20 15:45, David Rosenstrauch a écrit :
Em dezembro 22, 2017 10:31 Manuel Reimer escreveu:
Question is: What is the intended goal. I guess it is not what I want to do?
Well, so far you said you want to autobuild some packages and that it MUST run
as root, with no good reason why.
My autobuild process runs as root. It also directly
On 12/22/2017 08:31 AM, Manuel Reimer wrote:
> My autobuild process runs as root. It also directly updates the chroot
> which also needs root permissions so it's the best to start with "root"
> and then drop privileges for the tasks that shouldn't run with root
> privileges. The whole system is a d
On 12/22/2017 02:26 PM, Eli Schwartz via arch-general wrote:
AFAIK this should work fine, for its intended goal. Though I don't think
it gets a lot of testing.
Question is: What is the intended goal. I guess it is not what I want to do?
makechrootpkg elevates to root if needed, using sudo.
2017-12-22 14:20 GMT+01:00 Manuel Reimer :
> Yes, of course, but then "makechrootpkg" at some point wants to call
> "pacman" which will fail or will cause some unwanted sudo prompt to appear.
Yes, because makechrootpkg uses sudo for some operations. You can set
the NOPASSWD option in sudoers to av
On 12/22/2017 08:02 AM, Manuel Reimer wrote:
> Hello,
>
> I want to autobuild a set of packages. For this process, it is not
> acceptable to use "sudo" as I don't want to enter some passwords and my
> autobuild program also has to do some other stuff with root privileges.
>
> The help page of "ma
On 12/22/2017 02:16 PM, Óscar García Amor wrote:
# su - user -c "command"
In this case:
# su - user -c "makechrootpkg -c -r /var/cache/PATH_TO_MY_CHROOT"
Yes, of course, but then "makechrootpkg" at some point wants to call
"pacman" which will fail or will cause some unwanted sudo prompt to a
2017-12-22 14:02 GMT+01:00 Manuel Reimer :
> Hello,
Hi!
> I [..] was:
>
> # makechrootpkg -c -U build -r /var/cache/PATH_TO_MY_CHROOT
You can do the following:
# su - user -c "command"
In this case:
# su - user -c "makechrootpkg -c -r /var/cache/PATH_TO_MY_CHROOT"
Greetings
--
Óscar García
Hello,
I want to autobuild a set of packages. For this process, it is not
acceptable to use "sudo" as I don't want to enter some passwords and my
autobuild program also has to do some other stuff with root privileges.
The help page of "makechrootpkg" suggests, that there is an option for me:
16 matches
Mail list logo
