On Sat, 2022-08-27 at 14:58 -0500, Maxwell G via epel-devel wrote:
n 22/08/27 04:03PM, Frank Crawford wrote:
> While building two related new packages for EPEL9 with a
> chainbuild,
> the second one failed, however, now I am trying to work out how to
> specify the completed package in the build for the second package.
>
> I have tried creating a side-tag and add the completed build to the
> side-tag, then building the second package in that side-tag, but it
> still claims that it can't find the first package, which it
> requires to
> build.
Can you please provide more information? What are the
builds/packages?
What commands did you run? How did you add the first package to the
side
tag? Did you wait for the side tag repo to refresh before trying to
build the second package?
I think you answered my issue here, I did not allow sufficient time for
the repo to refresh before submitting the second build.
For reference, the packages were python-zipp-0.5.1-1.el9 and python-
importlib-metadata-4.6.3-2.el9 and the commands I ran were:
fedpkg request-side-tag
koji wait-repo <tag>
koji tag-pkg <tag> python-zipp-0.5.1-1.el9
fedpkg build --target=<tag>
It looks like I needed to do another "koji wait-repo <tag>" between the
tag-pkg and build, but I will say that it is not obvious in any of the
documentation I could find, that this needed.
> do I have to wait until the first package gets pushed to the
stable
> before I can now build the second?
No, that is not necessary. There are multiple ways to build against
packages that have not yet reached stable.
Anyway, thanks for your help.
Regards
Frank