[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#873332: stretch-pu: package pyosmium/2.11.3-1



On Fri, Sep 15, 2017 at 09:21:06PM +0200, Sebastiaan Couwenberg wrote:
> On 09/09/2017 03:42 PM, Julien Cristau wrote:
> > On Sat, Aug 26, 2017 at 17:43:26 +0200, Bas Couwenberg wrote:
> > 
> >> Upstream has released a new stable release of pyosmium fixing important
> >> bugs which I'd like to propose for inclusion in the next stable update.
> >>
> >> Kind Regards,
> >>
> >> Bas
> > 
> >> diff -Nru pyosmium-2.11.1/debian/changelog pyosmium-2.11.3/debian/changelog
> >> --- pyosmium-2.11.1/debian/changelog	2017-05-05 09:51:21.000000000 +0200
> >> +++ pyosmium-2.11.3/debian/changelog	2017-08-26 15:10:04.000000000 +0200
> >> @@ -1,3 +1,11 @@
> >> +pyosmium (2.11.3-1) stretch; urgency=medium
> >> +
> >> +  * New upstream bugfix release.
> >> +    - handler functions not called when using replication service (#38)
> >> +    - handler functions not called when using Reader instead of file
> >> +
> >> + -- Bas Couwenberg <sebastic@debian.org>  Sat, 26 Aug 2017 15:10:04 +0200
> >> +
> >>  pyosmium (2.11.1-1) unstable; urgency=medium
> >>  
> >>    * New upstream bugfix release.
> > 
> > Can you elaborate on the user or reverse-dependency impact of those
> > bugs, and what are the risks and mitigations for the changes you're
> > proposing?  Are there any related automated or manual tests?
> 
> pyosmium doesn't have reverse dependencies (yet), it does have some
> users. For these issues there are no tests.
> 
> I've added one of the upstream authors to the CC, who can hopefully
> elaborate further.

2.11.1 fixed an important bug affecting all users. That's already in
stable. Unfortunately there were two (smaller) bugs in the fix which are
now fixed in 2.11.3.

These changes have been backported from the 2.13/master branch which we
are currently developing on. They now have tests there, but to keep the
changes in the 2.11 branch to a minimum, the tests have not been
backported.

We, the upstream maintainers, are well aware of the Debian policy
concerning backwards compatibility and only allowing bugfixes in Debian
stable. These releases were specifically made to support Debian stable.
We want to help the Debian maintainers this way who would otherwise have
to follow and backport the changes we are doing in 2.13.

Jochen
-- 
Jochen Topf  jochen@remote.org  https://www.jochentopf.com/  +49-351-31778688


Reply to: