[10:27] <michael-vb> Hello.  Is there any easy way to ping people to suggest a package update?  I would specifically love libsane to be updated to latest git (they are actually hoping to do a release soon) before Wily is released, as it fixes a timing bug and makes my scanner work.
[10:29] <michael-vb> Reference bug 1184699 if it interests anyone.  I just subscribed rather opportunistically, as I suspect that bug covers lots of related but different issues.
[10:41] <rbasak> michael-vb: are you asking for a package update for Wily, or for Trusty?
[10:41] <michael-vb> Oh sorry, for Wily.
[10:42] <rbasak> michael-vb: unfortunately Wily has just entered feature freeze, so package updates that add features are no longer permitted without a release team exception
[10:42] <rbasak> michael-vb: we can cherry-pick bugfixes without an issue though
[10:43] <rbasak> michael-vb: see https://wiki.ubuntu.com/SponsorshipProcess for details on getting a proposed package upload into the sponsorship queue
[10:45] <michael-vb> To be honest if I can't get this through with low hassle I will just rebuild the package.  I spend a huge effort half a year ago getting an absolutely obvious typo in Compiz fixed with was breaking VirtualBox.  I just hoped that it would be simpler for a not-yet-released distribution.
[10:45] <michael-vb> s/with/which/
[10:46] <michael-vb> But the commits are 09daef4 and 425edc7.
[10:47] <michael-vb> http://anonscm.debian.org/cgit/sane/sane-backends.git/commit/?id=09daef4a681e43a411b14389ceee9292ffbc29fc
[10:47] <michael-vb> http://anonscm.debian.org/cgit/sane/sane-backends.git/commit/?id=425edc705e6323353bf99f58c277dc4f0fe47deb
[10:47] <michael-vb> I just need the second, but the first made another bug ticket subscriber happy.
[10:49] <rbasak> It is simpler for the development release - submit a debdiff, get it sponsored. No need for SRU paperwork etc.
[10:50] <michael-vb> Will take a quick look then.
[10:51] <rbasak> If cherry-picking, please include dep3 headers in the quilt patches inside the debdiff though. Helps with future maintenance by being able to track where the patches came from and if they have been included upstream.
[10:55] <michael-vb> Now it starts getting fun.  I have no clue about your versioning systems.
[11:12] <michael-vb> Right, test building with patch.
[11:14] <michael-vb> Let's see if I can install the packages on Vivid, as I haven't yet upgraded.
[11:17] <michael-vb> Doesn't quite finish building the package on Vivid, though it finishes compiling.  How much time do I have?  My conscience won't let me upload an untested patch, but it will be a few weeks before I get round to upgrading.
[11:18] <rbasak> michael-vb: basically, just add git-format-patch output to files in debian/patches/, annotate with dep3 (http://dep.debian.net/deps/dep3/), add the names to debian/patches/series and add an entry to debian/changelog.
[11:19] <rbasak> You have until final freeze - Oct 15th - to get it uploaded. But you'll need to upload to the sponsorship queue well in advance of that. I'd say at least a month.
[11:19] <rbasak> So ASAP really please.
[11:20] <michael-vb> Then I will upload the patch to the ticket for now and test when I get the chance.  How do I update the change log anyway?
[11:25] <rbasak> dch is a tool for editing debian/changelog, but for a one-off it might be easier just use a text editor and follow the format of the previous entry exactly.
[11:26] <michael-vb> For now I attached the patch to https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1184699/comments/34
[11:27] <michael-vb> I will need more time to understand this process than I have free just now.  If I don't find the time I will just rebuild the package locally again.
[11:27] <michael-vb> Thanks anyway.
[11:33] <rbasak> michael-vb: no problem. If you need any help, feel free to ping me.