Package Details: clean-chroot-manager 2.209-1

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: 57
Popularity: 0.036740
First Submitted: 2013-08-18 16:52
Last Updated: 2020-06-21 12:17

Required by (0)

Sources (1)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

graysky commented on 2019-10-23 22:28

All - I added support for an external makepkg.conf and pacman.conf in 2.201-1 ... lots of internals changed so please test and use the github page to report any issues.

graysky commented on 2019-10-23 17:42

@artafinde - Yes, ETA 9 min ago :p

artafinde commented on 2019-10-23 08:21

@graysky any ETA on pacman >= 5.2 support? This already hit stable repos today.

graysky commented on 2019-10-16 18:25

I replied to the closed ticket, https://github.com/graysky2/clean-chroot-manager/issues/57

gillecaluim commented on 2019-10-16 18:13

t really doesn’t matter what packages I’m building I have to nuke and create after the first package which completely defeats the purpose of ccm for me

jpapadopoulos commented on 2019-10-16 08:36

Hi, I'm also getting that error(Failed to stat /repo: No such file or directory) after building llvm-minimal-git and then trying to build mesa-git with "ccm64 S". This happened with a freshly nuked chroot. Trying to use "ccm64 s" for mesa-git instead gives me the following error "Failed to resolve /home/user/Data/chroot/user//home/user/Data/chroot//root/repo: No such file or directory"

https://github.com/graysky2/clean-chroot-manager/issues/57

graysky commented on 2019-10-10 20:59

Please post to the closed github issue, give me the example packages you're building so I can try to recreate.

gillecaluim commented on 2019-10-10 20:14

been there, done that, even removed and reinstalled ccm :(

graysky commented on 2019-10-10 19:09

@gill - Yes, it should be fixed. Can you nuke your build root and try again?

gillecaluim commented on 2019-10-10 18:57

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?