Package Details: clean-chroot-manager 2.209-1

Git Clone URL: (read-only, click to copy)
Package Base: clean-chroot-manager
Description: Wrapper for managing clean chroot builds with local repo therein.
Upstream URL:
Licenses: MIT
Conflicts: clean_chroot_manager
Replaces: clean_chroot_manager
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 57
Popularity: 0.007096
First Submitted: 2013-08-18 16:52
Last Updated: 2020-06-21 12:17

Dependencies (4)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

graysky commented on 2019-09-04 16:49

Do you mind taking this to the issue section on github so we don't pollute the AUR page with comments? Steps to reproduce there will be helpful for me to see what you're seeing.


adsun commented on 2019-09-04 16:30

@graysky I nuked the existing chroot: while it works when initially building a first package, the "stat" error starts occurring after the package is added to the repo directory of the chroot for the first time.

adsun commented on 2019-09-04 13:32

This needs to be fixed with the new devtools version 20190821. Otherwise:

Failed to stat /repo: No such file or directory

xuanruiqi commented on 2019-06-17 00:04

The new release now supports chroots on Btrfs!

graysky commented on 2019-01-20 10:10

@jtmb - If you follow Arch upstream, update to match.

jtmb commented on 2019-01-19 23:00

I did a little cursory googling, but I was curious the reasoning in updating the CFLAGS in 2.93. Should I update my conf to match the skel? any advantages/disadvantages that we're looking at?

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.