On Monday, July 6, 2020 10:24:44 PM CEST Iñaki Ucar wrote:
> El lun., 6 jul. 2020 21:33, James Cassell <[email protected]>
> escribió:
> 
> >
> > On Mon, Jul 6, 2020, at 1:31 PM, Iñaki Ucar wrote:
> > > Hi,
> > >
> > > Is there any mechanism similar to a side-tag in Koji to rebuild a
> > > bunch of packages without causing trouble in users' machines? Maybe a
> > > way to "disable" or "freeze" the chroot for the users while being able
> > > to continue building stuff?

One option is that you can toggle off the "auto createrepo" feature.  As
long as this is off, you will build the repository in separate directory
named "devel".  When you toggle it ON back again, the repository should be
regenerated with the new packages.

https://docs.pagure.org/copr.copr/user_documentation.html#i-see-some-strange-error-about-devel-repodata-in-logs

> > Fork it and rebuild there. Once you've got the order, rebuild in the
> > original. Not sure if it's possible to merge a forked COPR, though.
> >
> 
> I don't think it's possible, but forking is not an option in this case (too
> big). Besides, I've got the order, that's not the problem.

Another possibility is the fork, but forking such large project would be
storage-expensive.

Actually another possibility is to build in **separate** project against
the main, large project (build time additional repo).  Then, when ready,
you could "fork back" the new project into the main existing project (we
should call this "merge" in future).  There's at least this small bug

  https://bugzilla.redhat.com/show_bug.cgi?id=1851827

so honestly, this isn't well known and tested feature and I'd encourage you to
test this first on something smaller.

Pavel


_______________________________________________
copr-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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.fedorahosted.org/archives/list/[email protected]

Reply via email to