Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 43 |
Nodes: | 6 (0 / 6) |
Uptime: | 96:18:55 |
Calls: | 290 |
Files: | 904 |
Messages: | 76,426 |
Greetings,
off and on my attempts to coax Portage into installing a binary package fail. Current example: "sys-libs/readline-8.2_p13" was installed as bi-
nary some weeks ago, while my current attempts to install "sys-libs/ readline-8.2_p13-r1" as binary are ignored, "emerge" insists in install-
ing it as an ebuild. Same happened with a few more packages.
I downloaded file "Packages" from my binhost mirror which provides quite
some information and helped me specifying the correct USE flags for se- veral packages. But not for all -- apparently Portage's decicions are based on different information.
Where should I look?
Eli,
On Sun, 8 Dec 2024 10:24:42 -0500 you wrote:
...
By the way you don't need to download the Packages file manually. It
will be in /var/cache/edb/binhost/ using a directory structure based on
your binhost uri.
Great. Thankyou for this pointer!
But: the file "/var/cache/edb/binhost/**/Packages" has a time stamp from December 2-nd and differs from the "Packages" file I downloaded manually yesterday. So when does Portage sync it? I ran "emaint sync -A" yes- terday and then experimented with "emerge --pretend". But this did not update file "/var/cache/edb/binhost/**/Packages".
In any case the differences between these two files could well explain
my problems.