Having a proper upstream fix is way more involved, because we can't *know* what the time_t size is on any random system. It's probably a good idea to open a bug in their tracker to let them figure it out, though ;).
While the version in your Noble debdiff is technically OK since we already have a 0.40.1-3 in Oracular, we usually expect SRUs to use the schema documented there https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging (which I'm sure you're already familiar with ;) ). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059156 Title: proposed-migration for m2crypto 0.40.1-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/m2crypto/+bug/2059156/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
