On Wed, Mar 10, 2021 at 10:27 AM Ondrej Dubaj <odu...@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. Fabio _______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
