On 2022-01-12, Neil Bothwick <[email protected]> wrote: > On Wed, 12 Jan 2022 14:53:06 -0000 (UTC), Grant Edwards wrote: > >> Then it must have been ipkg-utils itself that required the older >> python_exec, but there was no ebuild present for it. > > If it was installed through portage, there would have been an ebuild > for it, in /var/db/pkg.
Yes, correct past tense. There was at some point in the past when ipkg-utils was installed. > That's what portage was referencing when if made the dependency > calculations. There was no ipkg ebuild. There had been in the past, but it was removed during an emerge --sync a while back. Last rites on 1 Aug 2020, removal 30 days later: https://www.mail-archive.com/[email protected]/msg90135.html My conclusion was that dependency info for currently installed packages is also stored somewhere else, since emerge still knew that python-2.7 was required for ipkg-utils. -- Grant
