Package Details: clean-chroot-manager 2.91-1

Git Clone URL: https://aur.archlinux.org/clean-chroot-manager.git (read-only)
Package Base: clean-chroot-manager
Description: Wrapper scripts for managing clean chroots.
Upstream URL: https://github.com/graysky2/clean-chroot-manager
Licenses: MIT
Conflicts: clean_chroot_manager
Replaces: clean_chroot_manager
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 52
Popularity: 1.362696
First Submitted: 2013-08-18 16:52
Last Updated: 2018-12-02 11:49

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

1 2 3 4 5 6 Next › Last »

graysky commented on 2018-12-11 04:17

@dmp1ce - I just used the nodev option and I get no errors:

tmpfs  /scratch  tmpfs size=27G,nodev  0  0

dmp1ce commented on 2018-12-11 00:30

I ended up adding a line in /etc/fstab copying what was in tmp.service without the nosuid. Works great!

# Development chroot
tmpfs   /mnt/chroot64   tmpfs   mode=1777,strictatime,nodev,size=8G 0 0

dmp1ce commented on 2018-12-10 23:23

I'm using the tmp.mount mount with systemd to create /tmp. When I set CHROOTPATH64=/tmp/.chroot64 I get the error sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?.

What do you recommend? I would like to use tmpfs because it is much faster for testing builds. Should I edit the tmp.mount file to remove nosuid from /tmp?

graysky commented on 2018-10-25 19:39

@Dark-sky - Glad you're up and running.

Dark-Sky commented on 2018-08-28 14:02

I solved my problem by copying over pacman.conf-pacnew to pacman.conf.

Dark-Sky commented on 2018-08-28 03:29

I tried to follow the directions here:

https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot

I thought I was pretty good w/ copy/paste and decided maybe I was not. So I ran across this package and running into the same issue of it bombing out with a million warnings and nothing getting installed:

[ray@arch chroot64]$ sudo ccm64 c ==> Creating install root at /home/ray/src/chroot64/root ==> Installing packages to /home/ray/src/chroot64/root :: Synchronizing package databases... core 131.4 KiB 684K/s 00:00 [----------------------] 100% extra 1645.2 KiB 1277K/s 00:01 [----------------------] 100% community 4.5 MiB 1555K/s 00:03 [----------------------] 100% multilib 171.7 KiB 1590K/s 00:00 [----------------------] 100% :: There are 26 members in group base-devel: :: Repository core 1) autoconf 2) automake 3) binutils 4) bison 5) fakeroot 6) file 7) findutils 8) flex 9) gawk 10) gcc 11) gettext 12) grep 13) groff 14) gzip 15) libtool 16) m4 17) make 18) pacman 19) patch 20) pkgconf 21) sed 22) sudo 23) systemd 24) texinfo 25) util-linux 26) which

Enter a selection (default=all): resolving dependencies... warning: ignoring package linux-api-headers-4.17.11-1 warning: cannot resolve "linux-api-headers>=4.10", a dependency of "glibc" warning: cannot resolve "glibc", a dependency of "readline" warning: ignoring package linux-api-headers-4.17.11-1

bronek commented on 2018-05-31 09:52

@ProfessorKaos64 arch-bootstrap will not build any packages. It will perform a part of the installation of a new ArchLinux system in a bootstrap directory (which later would be the root filesystem of the new system). For this purpose, it will download an earlier prepared minimum set of packages, from a given URL. This package clean-chroot-manager can be used to build packages (on an existing ArchLinux system) which will be used for a subsequent installation of a new system, or (most likely) upgrades. You could use these two packages together to create your own fork of ArchLinux if you were really keen

(I know it is almost a year after the question was asked, but perhaps someone will find this answer useful)

ProfessorKaos64 commented on 2017-07-17 16:21

How does this compare to https://github.com/tokland/arch-bootstrap ?

graysky commented on 2016-08-23 23:05

I will check into this... I use ccm all the time on my i7-4790 (9 threads) and see all 8 cores used up. Isn't the default values for MAKEFLAGS 2? Is the bug causing it to use /etc/makepkg.conf on the live filesystem or the default one installed by pacman?

bronek commented on 2016-08-23 12:38

@graysky many thanks for providing this package. I think it had been broken by change in devtools , perhaps this one https://bugs.archlinux.org/task/44827 , which results in makechrootpkg removing MAKEFLAGS set in root/etc/makepkg.conf . The result of this is that THREADS set in ~/.config/clean-chroot-manager.conf is ignored. The working workaround is hinted at in comments to #44827 , which is to create/update ~/.makepkg.conf like this:
MAKEFLAGS='-j17'

I would suggest that, given the availability of a workaround, the proper fix would be to entirely remove THREADS from ~/.config/clean-chroot-manager.conf and scripts, and instead advice user to create/update ~/.makepkg.conf with MAKEFLAGS option.