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

Bug#924772: marked as done (unblock: lxml/4.3.2-1)



Your message dated Sun, 17 Mar 2019 19:36:00 +0000
with message-id <582a124c-f62f-99a8-2216-525f3a3186f9@thykier.net>
and subject line Re: Bug#924772: unblock: lxml/4.3.2-1
has caused the Debian Bug report #924772,
regarding unblock: lxml/4.3.2-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
924772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924772
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock lxml, fixing exactly one segfault.  The diff is large because
upstream rebuilt with a new cython version.

==============
lxml changelog
==============

4.3.2 (2019-02-29)
==================

Bugs fixed
----------

* Crash in 4.3.1 when appending a child subtree with certain text nodes.

Other changes
-------------

* Built with Cython 0.29.6.

--- End Message ---
--- Begin Message ---
Matthias Klose:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> 
> Please unblock lxml, fixing exactly one segfault.  The diff is large because
> upstream rebuilt with a new cython version.
> 
> ==============
> lxml changelog
> ==============
> 
> 4.3.2 (2019-02-29)
> ==================
> 
> Bugs fixed
> ----------
> 
> * Crash in 4.3.1 when appending a child subtree with certain text nodes.
> 
> Other changes
> -------------
> 
> * Built with Cython 0.29.6.
> 

Unblocked, thanks.
~Niels

--- End Message ---

Reply to: