Search Criteria
Package Details: clean-chroot-manager 2.230-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/clean-chroot-manager.git (read-only, click to copy) |
---|---|
Package Base: | clean-chroot-manager |
Description: | Wrapper for managing clean chroot builds with local repo therein. |
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: | 66 |
Popularity: | 0.73 |
First Submitted: | 2013-08-18 16:52 (UTC) |
Last Updated: | 2024-09-29 11:18 (UTC) |
Dependencies (4)
- devtools (devtools32-gitAUR, devtools-gitAUR, devtools-doasAUR)
- libarchive (libarchive-gitAUR)
- pacman (pacman-gitAUR)
- rsync (rsync-gitAUR, rsync-reflinkAUR, rsync-reflink-gitAUR)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 .. 10 Next › Last »
graysky commented on 2019-10-10 19:09 (UTC)
@gill - Yes, it should be fixed. Can you nuke your build root and try again?
gillecaluim commented on 2019-10-10 18:57 (UTC)
I'm still getting the same problem with stat /repo. System is up to date, devtools = 20190912-1, clean-chroot-manager = 2.97-1 I can build the first package ok, but after that I get Failed to stat /repo You seemed to close the discussion on the github page as if this problem was fixed? If so, how can I fix this?
graysky commented on 2019-09-04 16:49 (UTC) (edited on 2019-09-07 11:35 (UTC) by graysky)
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.
EDIT: https://github.com/graysky2/clean-chroot-manager/issues/57
adsun commented on 2019-09-04 16:30 (UTC) (edited on 2019-09-04 16:31 (UTC) by adsun)
@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 (UTC) (edited on 2019-09-04 13:34 (UTC) by adsun)
This needs to be fixed with the new
devtools
version 20190821. Otherwise:xuanruiqi commented on 2019-06-17 00:04 (UTC)
The new release now supports chroots on Btrfs!
graysky commented on 2019-01-20 10:10 (UTC) (edited on 2019-01-20 10:10 (UTC) by graysky)
@jtmb - If you follow Arch upstream, update to match.
https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/pacman&id=c81d3556e03d4b3da79779a4804ba8bf8b127cb3
https://bugs.archlinux.org/task/54736
jtmb commented on 2019-01-19 23:00 (UTC)
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 (UTC)
@dmp1ce - I just used the nodev option and I get no errors:
« First ‹ Previous 1 2 3 4 5 6 7 .. 10 Next › Last »