#8488 go-md2man went missing from the F31 build root, blocking package builds
Closed: Fixed by rishi. Opened by rishi.

  • Describe the issue

go-md2man is an utility used to convert Markdown to UNIX manuals. It's used as a BuildRequires by podman and toolbox. It used to be provided by the golang-github-cpuguy83-go-md2man package, which recently got renamed to golang-github-cpuguy83-md2man. Even though the old package was retired, the new one hasn't made it to the build roots for some time.

Would it be possible to tag the new package into the F31 build root?

  • When do you need this? (YYYY/MM/DD)

As soon as possible to unblock dependent builds.

  • When is this no longer needed or useful? (YYYY/MM/DD)

  • If we cannot complete your request, what is the impact?

Dependent packages can't be built.


For the record based on what I have heard from @eclipseo and @qulogic yesterday at Go SIG meeting this is not the only case of early(prior the side tag got merged back) retirement of packages causing FTBFS/broken deps in rawhide/f31 related to the https://bugzilla.redhat.com/show_bug.cgi?id=1715534 side tag rebuild.

Yes this is temporary, the time to build all packages.

@eclipseo Shouldn't the side tag rebuild shield rawhide from this type of breakages?

The problem is I haven't kept a list of all packages to be retired, so I did it when I process the package to be built in the side tag.

From the IRC conversation, I believe @eclipseo tagged this in to f31; do we need to keep this open then?

From the IRC conversation, I believe @eclipseo tagged this in to f31;
do we need to keep this open then?

Yes, this can be closed now.

Metadata Update from @rishi:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata