18 Sep
2018
18 Sep
'18
3:37 p.m.
On 9/17/18 12:26 PM, ProgAndy wrote:
This might be a use case for remakepkg to remove the replaces-entry in the java10 packages.
The package in the sync database, which is a different database record than the package in the local (installed) database, will still contain the replaces entry and will therefore act as a replacement. Meanwhile, replaces don't even do what a lot of people seem to think. They're only ever read from sync databases, they're only ever accounted for in an -Su operation, and the field is completely inert in either an installed package or a *.pkg.tar.xz file. -- Eli Schwartz Bug Wrangler and Trusted User