Building packages in chroot

IICore · 2015-01-06 20:11:55

Hi Guys,

i wan't to build some packages, e.g. teamviewer, in a clean chroot ... as even in the last years.
So i followed this wiki article: https://wiki.archlinux.org/index.php/De … ean_Chroot

If i run 'makechrootpkg -c -r /opt/arch64' as root, i got the error:

root@toaster ~/teamviewer # makechrootpkg -c -r /opt/arch64                                                 :(
==> Creating clean working copy [copy]...done
makepkg: invalid option '--asroot'
==> ERROR: Could not download sources.

Without root privileges i was asked for the root password and got later the same error.
I will not install base-devel on my live system and i know that the --asroot option was removed from makepkg.

Is the way by using a virtual maschine the only one?

Sorry for my english :-)

Greetz
IICore

clfarron4 · 2015-01-06 20:31:44

If I'm not mistaken, running makepkg as a root user, be it with the --asroot flag or as the root user is supposed to fail because of the changes to makepkg. It's been removed because the issues with fakeroot (which caused the --asroot flag to appear) have been fixed.

If you create a normal user and then build in the chroot, it should work normally.

EDIT: There's also something to do with sudo-ing to nobody somewhere in this thread.

Last edited by clfarron4 (2015-01-06 20:46:13)

graysky · 2015-01-06 20:50:23

Does it build with ccm?

ccm = https://aur.archlinux.org/packages/clea … t-manager/

IICore · 2015-01-06 21:34:45

Hi graysky,

i will test ccm later ... currently there are some problems, which are important to me (e.g. cups: Unable to get list of printer drivers)

I installed Arch Linux with KDE after 2 month again on my pc but currently there are so many problems, so i indent to install Fedora or an other distribution

asdil12 · 2015-01-13 12:32:30

Reported a bug: https://bugs.archlinux.org/task/43432

Allan · 2015-01-13 12:58:59

If you run makechrootpkg using sudo, everything works fine.

asdil12 · 2015-01-13 13:05:50

If I would run makechrootpkg as nobody, it wouldn't be able to get into the chroot as the chroot files are owned by root.
I could set the SUDO_USER env var to "nobody" but that requires the pwd to be writeabke by user nobody.
Still the asroot option is not there anymore so makechrootpkg must not use that option.

Actually makechrootpkg should also automaticly take care of this on its own. It's kind of hackish to let the user chown the pwd to nobody and let makechrootpkg call with env SUDO_USER=99.

Last edited by asdil12 (2015-01-13 13:06:37)

Allan · 2015-01-14 00:29:46

Are you only running as root?

asdil12 · 2015-01-14 05:33:02

I'm running a tool via cron (see aur pkg aurbs) that automaticly builds aur pkgs.
I want to prevent editing any security related files (like sudoers) if I can prevent it.

The tool is rin via cron or via ssh. Both don't elevate priviliges so the SUDO_USERS var is not set.

Arch Linux

#1 2015-01-06 20:11:55

Building packages in chroot

#2 2015-01-06 20:31:44

Re: Building packages in chroot

#3 2015-01-06 20:50:23

Re: Building packages in chroot

#4 2015-01-06 21:34:45

Re: Building packages in chroot

#5 2015-01-13 12:32:30

Re: Building packages in chroot

#6 2015-01-13 12:58:59

Re: Building packages in chroot

#7 2015-01-13 13:05:50

Re: Building packages in chroot

#8 2015-01-14 00:29:46

Re: Building packages in chroot

#9 2015-01-14 05:33:02

Re: Building packages in chroot

Board footer