| 1 |
On Thursday, 6 August 2020 16:07:12 BST Peter Humphrey wrote: |
| 2 |
> On Wednesday, 5 August 2020 17:04:35 BST Peter Humphrey wrote: |
| 3 |
> > Well, I don't know what's going on. Today it all works perfectly. |
| 4 |
> |
| 5 |
> ...and today it's up to its tricks again, even after a reboot. |
| 6 |
> |
| 7 |
> If I 'emerge -uaDvNK' in the chroot, portage wants to emerge every package |
| 8 |
> of which a binpkg exists, but it omits postfix and says it's found a USE |
| 9 |
> flag mismatch. If I 'emerge -uaDvNk' it only updates the existing installed |
| 10 |
> packages, but it still complains about the postfix mismatch. |
| 11 |
> |
| 12 |
> But postfix isn't installed in the chroot system. |
| 13 |
> |
| 14 |
> Remember: I bind-mount the packages directory of the host to the same place |
| 15 |
> in the chroot, so it contains the full set of packages, from which I want |
| 16 |
> to update just those that are installed in the chroot system. |
| 17 |
> |
| 18 |
> And I have even less idea what's going wrong than ever. |
| 19 |
|
| 20 |
A thought: is there a reason not to bind-mount a single directory to two |
| 21 |
others at the same time? Or should I chain them instead? I have this in the |
| 22 |
host's /etc/fstab: |
| 23 |
|
| 24 |
# NFS-export portage to the compile host: |
| 25 |
/var/db/repos/gentoo /mnt/nfs/portage none bind 0 0 |
| 26 |
/var/cache/packages /mnt/nfs/portage.packages none bind 0 0 |
| 27 |
/var/cache/distfiles /mnt/nfs/portage.distfiles none bind 0 0 |
| 28 |
|
| 29 |
# Use the same packages and distfiles on the local rescue system: |
| 30 |
/var/cache/packages /mnt/rescue/var/cache/packages none noauto,bind 0 0 |
| 31 |
/var/cache/distfiles /mnt/rescue/var/cache/distfiles none noauto,bind 0 0 |
| 32 |
|
| 33 |
-- |
| 34 |
Regards, |
| 35 |
Peter. |
Archives