On Fri, Nov 07, 2014 at 05:11:42PM +0100, Martin Stigge wrote: > I have looked into the code and prepared the relevant diff (from > upstream 2.14 actually) that fixes the problem in version 2.13. For the > record, I'll attach it to this mail. It might serve as a minimal > targeted fix to get into testing during the freeze.
That doesn't look too bad. I suggest creating a version 2.13-2+jessie1 which just includes this particular patch and prepare an upload for "testing-proposed-updates". The version number is necessary to indicate the update affects Jessie only. Then file a bug report against the pseudo-package "release.debian.org" requesting an unblock of the bug. Please include the full debdiff for the updated package to document your changes. Your changes should include this particular patch for the bug fix only, the entry in the debian/patches/series file plus the changelog entry for the version 2.13-2+jessie1, see [1] for an example. > However, looking at the code, I'm not sure severity "grave" is > justified, maybe the bug only manifests under certain circumstances? Do > you experience the bug? Therefore, downgrading to "important" for now. I'm not using wmweather+ myself, but I was just skimming through the list of RC bugs. I still think it would be nice to have this issue fixed for Jessie as the bug seems to render the package unusable. And if you follow my proposed procedure above, I am pretty sure you can have the fixed version unblocked by the release team. Adrian > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697092 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
