So, for a while now my standard protocol for testing the effects of updating a package has been to build it and its deps in a copr. However, this is becoming more and more obviously unreliable because later builds can use older version of packages from the main Fedora repos instead of from the copr.

I have filed https://github.com/fedora-copr/copr/issues/3819 to try to deal with that in copr.

In the mean time, what other options do I have? Is it possible to have a scratch side tag? I'd rather not commit changes to the rawhide branch until I know things are fairly stable.

I guess I could do everything manually locally in mock - but that is a pain, and I actually don't have a machine capable of building VTK reliably at the moment.


--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager                         720-772-5637
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       or...@nwra.com
Boulder, CO 80301                 https://www.nwra.com/

--
_______________________________________________
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

Reply via email to