Thank you Allen. We could now debate about all kind of theories how the GC/serialization changes in https://go.dev/doc/go1.18#runtime might cause this like in https://github.com/kubernetes/kubernetes/issues/108357 - but that would not get us anywhere.
Since your upload was targeting jammy-security I was unsure if building with 1.17 again is ok. But your message seems t indicate that you would be ok to go that way. If that is true, then making that dependency explicit in regard to the version seems to be the way to go. Since the breaking build was targeting jammy-security I assume the fix also needs to go there and therefore via the security upload workflow. BTW I checked 1.5 in noble, it is not affected by the same, marking bug tasks accordingly ** Bug watch added: github.com/kubernetes/kubernetes/issues #108357 https://github.com/kubernetes/kubernetes/issues/108357 ** Also affects: aptly (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: aptly (Ubuntu Jammy) Assignee: (unassigned) => Allen Huang (allenpthuang) ** Changed in: aptly (Ubuntu) Assignee: Allen Huang (allenpthuang) => (unassigned) ** Changed in: aptly (Ubuntu) Status: Confirmed => Fix Released ** Changed in: aptly (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2140498 Title: aptly fails to create new mirrors or decode previous mirror data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptly/+bug/2140498/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
