You want to file this over at releng -> https://pagure.io/releng/issues

You can of course do a dynamic side tag with 'fedpkg request-side-tag --base-tag f39-build' but then it will have a dynamic name, so I guess you probibly do want to request f39-boost?

Anyhow, refile over at releng and we will get you setup. :)

While this is a question for releng and not FESCo, I am concerned that the side tag will be open for so long. Do releng managed side tags have collision detection at merge time as well, or does this only happen in bodhi? I assume that there will be merge conflicts of the side tag will be open for so long.

I have an external dependency on getting a proven packager to do the
rpmdev-bumpspec && push dance, because, well
https://pagure.io/fesco/issue/2774

I have Florian Weimer lined up to do that work for me (and Jonathan Wakely
as a backup), I anticipate that to happen on or about the date I said I
needed the side-tag (2022/02/13).

I will start the builds immediately after that is completed, so it is
however long it takes to churn through a majority of the packages. As a
data point, the f37-boost side tag was open ~1week.

On Thu, Feb 9, 2023 at 4:57 PM Fabio Valentini pagure@pagure.io wrote:

decathorpe added a new comment to an issue you are following:
While this is a question for releng and not FESCo, I *am* concerned that the side tag will be open for so long. Do releng managed side tags have collision detection at merge time as well, or does this only happen in bodhi? I assume that there *will* be merge conflicts of the side tag will be open for so long.

To reply, visit the link below or just reply to this email
https://pagure.io/fesco/issue/2953

Yes, the releng tooling uses a script that checks if there is a newer build in the dest tag...

I updated the releng issue to shorten the expected time to 1wk.