Package Details: clean-chroot-manager 2.226-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.79
First Submitted: 2013-08-18 16:52 (UTC)
Last Updated: 2023-05-24 19:34 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »

alpha.niner commented on 2016-01-28 14:33 (UTC)

Thanks, I'll try it out before the end of the day.

graysky commented on 2016-01-27 20:56 (UTC)

@alpha - Would you trying version 2.74? Please modify this PKGBUILD to that pkgver, update the sums and build. I don't want to bump formally to 2.74 until I get some feedback from you. In my test cases, it seems to solve the issue.

alpha.niner commented on 2016-01-26 21:18 (UTC)

As an interim solution I just modified the buildnc function to cp the necessary things from $CHROOTPATH64/root to $CHROOTPATH64/$USER. I didn't realize at first that pacman.conf may also need updating. @@ -247,6 +247,11 @@ local mesg="Attempting to build package..." echo -e "${YELLOW}---->${ALL_OFF}${BOLD} ${mesg}${ALL_OFF}" + local mesg="Updating user chroot local repo..." + echo -e "${YELLOW}---->${ALL_OFF}${BOLD} ${mesg}${ALL_OFF}" + /usr/bin/cp -a "$CHROOTPATH64/root/etc/pacman.conf" "$CHROOTPATH64/$USER/etc" + /usr/bin/cp -a "$CHROOTPATH64/root/repo/" "$CHROOTPATH64/$USER" + if [[ -z "$RUNNAMCAP" ]]; then nice -19 $CHROOTPATH64/root/makechrootpkg-mod -u -r $CHROOTPATH64 else

graysky commented on 2016-01-26 20:44 (UTC)

Yes, I couldn't read the difference between s and S on my phone when I saw your original post and that error propagated... perhaps adjusting that behavior when calling with the S (capital S) option would be in order here... That would be two calls to update as I think through it thought... one to $CHROOTPATH64/root/repo and another to $CHROOTPATH64/$USER/repo or perhaps an rsync call or the like.

alpha.niner commented on 2016-01-26 20:35 (UTC)

I don't think it's anything to do with my PKGBULIDs. Looking at the script (specifically clean-chroot-manager64) it seems that building packages updates the local repo at "$CHROOTPATH64/root/repo" but not "$CHROOTPATH64/$USER/repo". It's running makechrootpkg-mod with -c that causes "$USER/repo" to be 'updated', and of course -c is the "clean" flag so it's not used when makechrootpkg-mod is called in the case of 'ccm S'.

graysky commented on 2016-01-26 19:57 (UTC)

Not sure what to say... is there something odd in the respective PKGBUILD files for the git packages such that they wouldn't be visible as providing themselves? I cannot find any of these three in the AUR so I am assuming you modified them for your needs.

alpha.niner commented on 2016-01-26 15:25 (UTC)

$ sudo ccm l ==> Listing out packages in chroot repo... -rw-r--r-- 1 root root 51K Jan 26 10:19 python-configshell-fb-git-1.1.fb19.r0.g7d537ea-1-any.pkg.tar.xz -rw-r--r-- 1 root root 65K Jan 26 10:19 python-rtslib-fb-git-2.1.fb59.r10.g2b12785-1-any.pkg.tar.xz $ sudo ccm S ... error: target not found: python-rtslib-fb-git error: target not found: python-configshell-fb-git ==> ERROR: 'pacman' failed to install missing dependencies. ==> ERROR: Build failed, check /mnt/scratch/service/build $ ls -a /mnt/scratch/service/build . .. $ sudo ccm s <success>

graysky commented on 2016-01-26 13:43 (UTC)

Are the packages in the local repo? What is the output of: ccm l

alpha.niner commented on 2016-01-26 05:04 (UTC)

When I try to build a package with 'ccm S' that depends on packages already built with ccm (also 'ccm S') the build fails: ==> Making package: targetcli-fb-git <snip> ==> Checking runtime dependencies... ==> Installing missing dependencies... error: target not found: python-rtslib-fb-git error: target not found: python-configshell-fb-git ==> ERROR: 'pacman' failed to install missing dependencies. The build succeeds when using 'ccm s'. Note the deps (and the pkg I'm building) are modified-for-git versions of AUR packages so you won't find them anywhere.

graysky commented on 2015-11-14 16:31 (UTC)

Bump to v2.73-1 Changelog: Better distcc integration. Commit: https://github.com/graysky2/clean-chroot-manager/compare/v2.72...v2.73

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »