| 1 |
On Wed, 16 Jan 2019 09:50:58 +0000, Peter Humphrey wrote: |
| 2 |
|
| 3 |
> This box acts as an emerge server for a 32-bit Atom. So I NFS-mount the |
| 4 |
> Atom's portage tree in a 32-bit chroot, build the packages it needs and |
| 5 |
> then emerge the packages on the Atom. |
| 6 |
> |
| 7 |
> This morning I found something odd: the Atom wanted to emerge perl |
| 8 |
> 5.24, even though 5.26 was already present, so I got a long list of |
| 9 |
> clashes. This is the emerge command on the Atom: |
| 10 |
> |
| 11 |
> emerge -auDvUK --jobs=2 --load-average=4 --changed-use --changed-deps \ |
| 12 |
> --with-bdeps=y --nospinner --keep-going world |
| 13 |
> |
| 14 |
> The solution was to delete the 5.24 package left over from an earlier |
| 15 |
> emerge. All was then well. |
| 16 |
> |
| 17 |
> It looks as though the -K switch caused portage to want to emerge the |
| 18 |
> package even though it wasn't indicated by the update. Is it supposed |
| 19 |
> to do that? |
| 20 |
|
| 21 |
Was there a suitable package for 5.26 in $PKGDIR? The -K switch forces |
| 22 |
portage to use a package, unlike -k, so if the exact 5.26 version you had |
| 23 |
installed had been removed from the tree in favour of an updated/fixed |
| 24 |
version, portage would have to downgrade if you hadn't built the new |
| 25 |
package. |
| 26 |
|
| 27 |
|
| 28 |
-- |
| 29 |
Neil Bothwick |
| 30 |
|
| 31 |
Weird enough for government work. |
Archives