#9895 Untag autoconf-2.70-1.fc34 from f34 tag
Closed: Fixed 3 years ago by pbrobinson. Opened 3 years ago by odubaj.

  • Describe the issue
    Hello, many problems with build occured after rebasing autoconf from version 2.69 -> 2.70 today. The update broke many packages and we need to revert it ASAP

  • When do you need this? (YYYY/MM/DD)
    ASAP

  • When is this no longer needed or useful? (YYYY/MM/DD)

  • If we cannot complete your request, what is the impact?
    Break of building multiple packages in fedora-rawhide


But seriously given that it's been 8 years since autoconf 2.69 landed in Fedora why are you surprised about this, why did you build it for F-33 and why isn't it done properly with a Change proposal so this can be properly handled?!?! Did you not do any testing?

Sorry about the issues. I did test but seems not enough properly. Hopefully by untaging nobody will be affected. I will be carefull next time with such changes.

Sorry about the issues. I did test but seems not enough properly. Hopefully by untaging nobody will be affected. I will be carefull next time with such changes.

Please do a change for this for F-34 or even F-35 if necessary before trying to land it again.

Metadata Update from @pbrobinson:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

This was a honest mistake in underestimating the update impact. When realizing the fallout, @odubaj acted quickly to mitigate the damage. We'll work together to make sure this goes via proper communication channels before proceeding further.

Login to comment on this ticket.

Metadata