On 12/8/24 12:57 PM, Dr Rainer Woitok wrote: > 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.
It is definitely downloaded by emerge --pretend --getbinpkg. It is not downloaded by emaint sync. If neither FEATURES="getbinpkg" nor EMERGE_DEFAULT_OPTS="--getbinpkg" are set, then you have to manually pass --getbinpkg on the CLI every time you want binpackages -- correspondingly, it will only download the Packages file when you manually pass --getbinpkg (as root). In theory, this should mean you always have a fresh cached index any time you actually check for binary updates... It also will check the timestamp to figure out whether to redownload. The downloaded file will have a new "DOWNLOAD_TIMESTAMP:" field but you can ignore that specific line. A timestamp of December 2 is definitely way too old. ... So the two possibilities I can think of are that: - you ran --pretend as non-root, so emerge couldn't update the index - you usually update with -uDU --getbinpkg, and didn't pass --getbinpkg with --pretend -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
