Hi Chris, On Tue, 28 Mar 2023 at 12:51, Christopher Baines <[email protected]> wrote:
> This is probably connected with package replacements, maybe the original > package definition should be marked as hidden? Anyway, I think the > bigger point here is I'm not sure what's meant to be done when adding > replacements for a package, and I don't know how to find out what's > meant to be done? The issue is ’define-public’ which is unexpected for a replacement. It should be only ’define python-pillow/security-fixes’ or hides it. Aside, I agree that grep in the source with ’/fixed’ to find examples how to write grafts and replacement is not the best documentation. :-) Cheers, simon
