On Fri, 2025-05-16 at 23:00 -0700, Adam Williamson wrote:
> On Fri, 2025-05-16 at 21:14 -0700, Tom Stellard wrote:
> > On 5/16/25 9:07 PM, Tom Stellard wrote:
> > > On 5/16/25 6:55 PM, Frank Crawford wrote:
> > > > So, after searching, reading and trying stuff, I still can't
> > > > get
> > > > sidetags to work correctly. It doesn't help that most of the
> > > > documentation refers to older versions of koji, etc.
> > > >
> > > > Anyway, I want to create a sidetag, add a recent build and then
> > > > build
> > > > some other related packages in there. Certainly this is for
> > > > EPEL10,
> > > > but that shouldn't matter.
> > > >
> > > > I've created a side tag ("fedpkg request-side-tag"), tried to
> > > > add my
> > > > package ("koji add-pkg --owner frankcrawford epel10.1-build-
> > > > side-112102
> > > > c-icap-devel-0.6.3-2.el10_1" plus others) and added appropriate
> > > > wait-
> > > > repo commands ("koji wait-repo -v --build=c-icap-devel-0.6.3-
> > > > 2.el10_1
> > > > epel10.1-build-side-112102 --request") yet the repo never has
> > > > the added
> > > > packages, and looks to never get rebuilt.
> > > >
> > > > I can see the packages tagged appropriately ("koji list-pkgs --
> > > > tag=epel10.1-build-side-112102") but when I build using the
> > > > sidetag
> > > > they are not there.
> > > >
> > > > So in summary what I did was:
> > > >
> > > > fedpkg request-side-tag
> > > > koji wait-repo epel10.1-build-side-112102
> > > > koji add-pkg --owner frankcrawford epel10.1-build-side-112102
> > > > c-icap-devel-0.6.3-2.el10_1
> > >
> > > I don't think this part is correct or at least I don't do this
> > > with side-tags.
> > >
> > > The `fedpkg request-side-tag` and `koji wait-repo` are correct,
> > > but after that
> > > all you need to do is build the packages you want into the side-
> > > tag.
> > >
> >
> > I see now what you were trying to do, c-icap-0.6.3-2.el10_1, is in
> > epel10.1-testing, which is why it is not in the side tag.
Okay, that is understandable, but it is not documented any where that a
novice can understand.
Now you state it explicitly I will remember for future.
> >
> > You should use `koji tag` to add it to the side-tag, not `koji add-
> > pkg`
> >
> > koji tag epel10.1-build-side-112102 c-icap-0.6.3-2.el10_1
Where I found it was from the help from koji, as it was the closest to
any explanation. I could not find anything that actually listed what
all the options actually do and where you would use them.
>
> This won't ultimately achieve what you want, though, because c-icap-
> 0.6.3-2.el10_1 is already in an update:
>
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-5227245027
>
> builds can only be in one update at a time, and you can't remove the
> last build from an existing update. So if a build is the sole package
> in an existing update, it's 'trapped' in that update. If you actually
> need a multi-package update, you have to do a bump/rebuild in the
> side
> tag - you have to do a c-icap-0.6.3-3.el10_1 build in the side tag.
>
> Basically, if you first do a 'normal' build and create an update (or
> one is automatically created for you, on a Rawhide-like branch), then
> realize you *actually* needed to do a multi-package side tag update,
> you'll have to do a bump/rebuild. You can only 'escape' if you did
> the
> build but didn't create an update (or have one auto-created).
Fair enough. I can understand the issue now it is listed, but could
not find it noted anywhere previously.
>
> Aside from that, though, Benson and Tom are right: after creating a
> side tag you either do builds to it with `fedpkg build --target` or
> tag
> existing builds in with `koji tag-build`. `add-pkg` is not the right
> thing to use here, I'm not sure where you came across it.
And I did suspect this was the case, but again, it couldn't find it
stated anywhere.
BTW, I chose "add-pkg" entirely because it seem kind of right in the
koji help info, and match closest to some old documents (10+ years ago)
on how to use side-tags. This was where my comment came from that
finding any recent documentation is hard to do.
>
> https://docs.fedoraproject.org/en-US/package-
> maintainers/Package_Update_Guide/#multiple_packages
> is the doc for this.
Sorry, this doesn't cut it, I've read it multiple times, but really it
just lists the commands with little or no background on what they do
and more importantly, what they don't do.
But anyway, thanks all for the quick comments, as you have shown me
what I did wrong. Hopefully I will remember all the details in a years
time when I try to do something similar.
Regards
Frank
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
