On Thu, Aug 27, 2020 at 9:42 AM Mohan Boddu mboddu@bhujji.com wrote:
On Wed, Aug 26, 2020 at 1:53 PM kevin kevin@scrye.com wrote:
On Wed, Aug 26, 2020 at 07:18:49PM +0200, Fabio Valentini wrote:
Hrm. It looks like at least some of those issues were transient, yes. However, two issues are still left:
- libdkimpp-2.0.0-6.fc33 is tagged with f33 and f34 but 2.0.0-3.fc32
is in the f33 repos
f34 should have been fine... f33 the newer one was only tagged in this morning:
Wed Aug 26 03:25:54 2020 libdkimpp-2.0.0-6.fc33 tagged into f33 by humaton [still active]
So it should be in today's f33 compose, but indeed I don't see it there. Odd.
oh. Man. I sure hate timezones. ;)
It was tagged after the f33 compose started.
- swift-lang-5.2.5-1.fc33 is tagged with f33 and f34 but 5.2.4-3.fc33
is in the f33 repos
Same here. Tagged in this morning, should be fixed tomorrow.
I untagged them since they are directly tagged to f33 tag without getting right with fedora-33 key. I am tagging them to f33-updates-candidate to let bodhi take care of the process flow since we are in freeze now.
And its not possible, since there is a update with the same build that got pushed to f34, sigh.
I will work with adamw in creating a FBR to push these updates directly to the f33 tag.
Both these packages were built ~two weeks ago, so maybe they were screwed up by the mass branching somehow?
Yeah, possibly so.
kevin _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@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