Package Details: clean-chroot-manager 2.227-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: 64
Popularity: 0.26
First Submitted: 2013-08-18 16:52 (UTC)
Last Updated: 2024-05-16 16:47 (UTC)

Latest Comments

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

Lone_Wolf commented on 2024-03-09 12:57 (UTC)

I had some issues and decided to give ccm another try.

It's working fine now using my own pacman & makepkg settings, including the ccache data sharing. I especially like that you have put the chroot_local repo above all others.

That has saved me some headaches were I had to add packages manually to prevent pacman from using repo packages when using devtools..

graysky commented on 2019-10-23 22:28 (UTC)

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 (UTC)

@artafinde - Yes, ETA 9 min ago :p

artafinde commented on 2019-10-23 08:21 (UTC)

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

graysky commented on 2019-10-16 18:25 (UTC)

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

gillecaluim commented on 2019-10-16 18:13 (UTC)

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 (UTC) (edited on 2019-10-16 08:46 (UTC) by jpapadopoulos)

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 (UTC)

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 (UTC)

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