You are not logged in.
I've been using this guide for creating a clean chroot and building packages for some time.
After doing the same on a machine that uses [testing] and didn't have previously the chroot after the devtools update I am unable to update it because it reports that can't determine the / mountpoint and also that there isn't any space left (I know there are several GiB left on the partition):
0 akai@Arch-alferpal: ~ 12:52 ---> sudo mkarchroot -u $CHROOTDIR/root ;
Password:
:: Synchronising package databases...
testing is up to date
core is up to date
extra is up to date
community-testing is up to date
community is up to date
multilib-testing is up to date
multilib is up to date
heftig is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Targets (1): libpipeline-1.2.0-2
Total Download Size: 0.03 MiB
Total Installed Size: 0.08 MiB
Net Upgrade Size: 0.00 MiB
Proceed with installation? [Y/n]
:: Retrieving packages from testing...
libpipeline-1.2.0-2-x86_64 32.4 KiB 486K/s 00:00 [###############################] 100%
(1/1) checking package integrity [###############################] 100%
(1/1) loading package files [###############################] 100%
(1/1) checking for file conflicts [###############################] 100%
error: could not determine root mount point /
error: not enough free disk space
error: failed to commit transaction (not enough free disk space)
Errors occurred, no packages were upgraded.
The chroot was made following the wiki guide and didn't report any troubles.
Any idea?
Last edited by ethail (2011-11-04 12:45:53)
Best Testing Repo Warning: [testing] means it can eat you hamster, catch fire and you should keep it away from children. And I'm serious here, it's not an April 1st joke.
Offline
Disable CheckSpace in pacman.conf. It does not work in chroots.
Offline
Solved and working. Thank you for your quick answer, Allan.
Best Testing Repo Warning: [testing] means it can eat you hamster, catch fire and you should keep it away from children. And I'm serious here, it's not an April 1st joke.
Offline
Should this info be included in pacman.conf's manual?
Offline
Should this info be included in pacman.conf's manual?
..or should mkarchroot comment that line out automatically?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline