Search Criteria
Package Details: clean-chroot-manager 2.222-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: | 57 |
Popularity: | 0.010330 |
First Submitted: | 2013-08-18 16:52 (UTC) |
Last Updated: | 2022-05-05 18:19 (UTC) |
Latest Comments
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 :(
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:
dmp1ce commented on 2018-12-11 00:30 (UTC)
I ended up adding a line in
/etc/fstab
copying what was intmp.service
without thenosuid
. Works great!dmp1ce commented on 2018-12-10 23:23 (UTC)
I'm using the
tmp.mount
mount with systemd to create/tmp
. When I setCHROOTPATH64=/tmp/.chroot64
I get the errorsudo: 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 removenosuid
from/tmp
?graysky commented on 2018-10-25 19:39 (UTC)
@Dark-sky - Glad you're up and running.
Dark-Sky commented on 2018-08-28 14:02 (UTC)
I solved my problem by copying over pacman.conf-pacnew to pacman.conf.
Dark-Sky commented on 2018-08-28 03:29 (UTC) (edited on 2018-08-28 13:51 (UTC) by Dark-Sky)
I tried to follow the directions here:
https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot
I thought I was pretty good w/ copy/paste and decided maybe I was not. So I ran across this package and running into the same issue of it bombing out with a million warnings and nothing getting installed:
[ray@arch chroot64]$ sudo ccm64 c ==> Creating install root at /home/ray/src/chroot64/root ==> Installing packages to /home/ray/src/chroot64/root :: Synchronizing package databases... core 131.4 KiB 684K/s 00:00 [----------------------] 100% extra 1645.2 KiB 1277K/s 00:01 [----------------------] 100% community 4.5 MiB 1555K/s 00:03 [----------------------] 100% multilib 171.7 KiB 1590K/s 00:00 [----------------------] 100% :: There are 26 members in group base-devel: :: Repository core 1) autoconf 2) automake 3) binutils 4) bison 5) fakeroot 6) file 7) findutils 8) flex 9) gawk 10) gcc 11) gettext 12) grep 13) groff 14) gzip 15) libtool 16) m4 17) make 18) pacman 19) patch 20) pkgconf 21) sed 22) sudo 23) systemd 24) texinfo 25) util-linux 26) which
Enter a selection (default=all): resolving dependencies... warning: ignoring package linux-api-headers-4.17.11-1 warning: cannot resolve "linux-api-headers>=4.10", a dependency of "glibc" warning: cannot resolve "glibc", a dependency of "readline" warning: ignoring package linux-api-headers-4.17.11-1
bronek commented on 2018-05-31 09:52 (UTC) (edited on 2018-05-31 09:53 (UTC) by bronek)
@ProfessorKaos64 arch-bootstrap will not build any packages. It will perform a part of the installation of a new ArchLinux system in a bootstrap directory (which later would be the root filesystem of the new system). For this purpose, it will download an earlier prepared minimum set of packages, from a given URL. This package clean-chroot-manager can be used to build packages (on an existing ArchLinux system) which will be used for a subsequent installation of a new system, or (most likely) upgrades. You could use these two packages together to create your own fork of ArchLinux if you were really keen
(I know it is almost a year after the question was asked, but perhaps someone will find this answer useful)
ProfessorKaos64 commented on 2017-07-17 16:21 (UTC)
graysky commented on 2016-08-23 23:05 (UTC)
bronek commented on 2016-08-23 12:38 (UTC) (edited on 2016-08-23 12:43 (UTC) by bronek)
francoism90 commented on 2016-04-03 16:18 (UTC) (edited on 2016-04-03 16:19 (UTC) by francoism90)
graysky commented on 2016-04-03 15:28 (UTC)
francoism90 commented on 2016-04-03 15:14 (UTC) (edited on 2016-04-03 15:15 (UTC) by francoism90)
graysky commented on 2016-01-29 20:06 (UTC)
alpha.niner commented on 2016-01-29 17:33 (UTC)
graysky commented on 2016-01-29 00:21 (UTC)
alpha.niner commented on 2016-01-28 21:46 (UTC) (edited on 2016-01-28 21:54 (UTC) by alpha.niner)
graysky commented on 2016-01-28 18:59 (UTC)
alpha.niner commented on 2016-01-28 14:33 (UTC)
graysky commented on 2016-01-27 20:56 (UTC)
alpha.niner commented on 2016-01-26 21:18 (UTC)
graysky commented on 2016-01-26 20:44 (UTC)
alpha.niner commented on 2016-01-26 20:35 (UTC)
graysky commented on 2016-01-26 19:57 (UTC)
alpha.niner commented on 2016-01-26 15:25 (UTC)
graysky commented on 2016-01-26 13:43 (UTC)
alpha.niner commented on 2016-01-26 05:04 (UTC)
graysky commented on 2015-11-14 16:31 (UTC)
ilusi0n commented on 2015-10-10 22:57 (UTC)
graysky commented on 2015-10-10 11:42 (UTC)
ilusi0n commented on 2015-10-10 09:04 (UTC)
graysky commented on 2015-10-08 19:55 (UTC)
graysky commented on 2015-09-24 15:26 (UTC)
graysky commented on 2015-07-09 19:37 (UTC)
graysky commented on 2015-05-14 20:32 (UTC)
graysky commented on 2015-03-29 11:56 (UTC)
graysky commented on 2015-02-05 22:53 (UTC)
graysky commented on 2015-01-27 12:33 (UTC)
graysky commented on 2015-01-24 16:07 (UTC)
graysky commented on 2015-01-15 21:37 (UTC)
ceri commented on 2015-01-15 21:33 (UTC)
graysky commented on 2015-01-15 20:58 (UTC)
coderkun commented on 2015-01-15 16:27 (UTC)
graysky commented on 2015-01-15 15:22 (UTC)
ceri commented on 2015-01-15 13:06 (UTC)
graysky commented on 2015-01-07 14:53 (UTC)
graysky commented on 2015-01-06 20:49 (UTC)
BeepDog commented on 2015-01-04 22:46 (UTC)
graysky commented on 2014-11-17 20:05 (UTC)
graysky commented on 2014-11-17 12:31 (UTC)
graysky commented on 2014-11-13 00:20 (UTC)
graysky commented on 2014-11-09 04:11 (UTC)
graysky commented on 2014-09-23 23:29 (UTC)
graysky commented on 2014-06-09 22:01 (UTC)
graysky commented on 2014-05-04 12:19 (UTC)