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