On 10. 03. 21 10:47, Fabio Valentini wrote:
> On Wed, Mar 10, 2021 at 10:27 AM Ondrej Dubaj <odubaj@redhat.com> wrote:
>>
>> Hello,
>>
>> Thank you for your suggestions, but as you might understand, I do not have the capacity to resolve problems of dependent packages when building with autoconf-2.71.
>>
>> I can only prepare autoconf-2.71 and compat package autoconf2.69-2.69 for other maintainers, so they are able to make appropriate changes and test them in copr. Testing is possible by pushing the changes to a new created branch "rawhide-autoconf-2.71", where in your package you can use autoconf dependency (autoconf-2.71) or autoconf2.69 dependency (compat package for autoconf-2.69). After pushing to the given branch, the package will be built automatically in copr and you can test the update of your package. You can do this many times until you are certain your package works good.
>>
>> Thanks for understanding and cooperation.
>
> Please don't do branches like this in "official" dist-git
> repositories. It's a big PITA to clean up such branches.

I concur.

Set the committish of the packages in your copr to "rawhide". Packagers can send
pull requests with changes and the results will appear in your Copr e.g. in:

https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/builds/?dirname=autoconf-2.70:pr:18

Pull requests, unlike arbitrary branches, can be safely rebased until the result
is good. Once merged, they are "gone" (technically, they remain in your fork,
but that should not bother anybody and can be deleted if needed).

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok