Re: Adding Package to side-tag

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Aug 28, 2022 at 07:38:31PM +1000, Frank Crawford wrote:
> 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.

:( Which documentation were you looking at for this?
We should try and update it...

The wait repo is needed because you added a build and now it needs to
regenerate the repodata to include it.

kevin

Attachment: signature.asc
Description: PGP signature

_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux