Hi Pali, See https://wiki.ubuntu.com/StableReleaseUpdates:
"7. New upstream microreleases In some cases, when upstream fixes bugs, they do a new microrelease instead of just sending patches. If all of the changes are appropriate for an SRU by the criteria above, then it is acceptable (and usually easier) to just upload the complete new upstream microrelease instead of backporting the individual patches. Note that some noise introduced by autoreconf is okay, but making structural changes to the build system (such as introducing new library dependencies) is generally not." Since your package doesn't currently have a micro release exception in Ubuntu, the SRU team will need to examine the entire diff to decide whether each individual fix meets the criteria for inclusion in a stable release update. I'm sure they're capable of generating the diff themselves, but making life easier for them and providing some specific commentary to them on what is going on will probably be useful. Please still submit a debdiff against Vivid that provides the change to debian/changelog so a sponsor can review and upload exactly what you want. I'd expect a new entry in debian/changelog at a minimum, with a description of what the update does and why, a reference to this bug, targetting the release(s) you want and with a version number that works (see https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging for a guide). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1462602 Title: Update 0xffff to stable version 0.6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/0xffff/+bug/1462602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
