On Fri Feb 3, 2023 at 02:00 +0100, Miro HronĨok wrote:
On 02. 02. 23 17:06, Ben Cotton wrote:
> # Create a blank ''blocker'' package that Conflicts with the to be
> removed packages.
> # Create a new Copr with the blocker package in its default buildroot.
> This will simulate the actual removal of these packages.
Was this verified to actually work that way? Isn't the conflicting
default-installed package removed when something that is conflicting is about
to be installed?
Yes, I did confirm it. You're right that just adding the package to the
buildroot doesn't work. I also built a modified go-rpm-macros to ensure
that blocker is pulled in (see the attachment); %gometa explicitly adds
`BuildRequires: blocker` to specfiles and every go-rpm-macros subpackage
has `Requires: blocker`. I already found a couple false positives.
--
Maxwell G (@gotmax23)
Pronouns: He/Him/His