Bug#743612: pu: package libxml2/2.8.0+dfsg1-7+nmu3

2014-04-14 Thread Josselin Mouette
Le dimanche 13 avril 2014 à 18:32 +0100, Adam D. Barratt a écrit : On Fri, 2014-04-04 at 10:03 +0200, Josselin Mouette wrote: I think I have found the likely cause for some (most?) of the infamous “oops! something has gone wrong” error messages in wheezy. Please consider accepting this

Bug#743612: pu: package libxml2/2.8.0+dfsg1-7+nmu3

2014-04-14 Thread Adam D. Barratt
Control: tags -1 + pending On Mon, 2014-04-14 at 12:31 +0200, Josselin Mouette wrote: Le dimanche 13 avril 2014 à 18:32 +0100, Adam D. Barratt a écrit : On Fri, 2014-04-04 at 10:03 +0200, Josselin Mouette wrote: I think I have found the likely cause for some (most?) of the infamous

Bug#743612: pu: package libxml2/2.8.0+dfsg1-7+nmu3

2014-04-13 Thread Adam D. Barratt
Control: tags -1 + confirmed On Fri, 2014-04-04 at 10:03 +0200, Josselin Mouette wrote: I think I have found the likely cause for some (most?) of the infamous “oops! something has gone wrong” error messages in wheezy. Please consider accepting this new version of libxml2. Please go ahead;

Bug#743612: pu: package libxml2/2.8.0+dfsg1-7+nmu3

2014-04-04 Thread Josselin Mouette
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: debian-xml-sgml-p...@lists.alioth.debian.org Hi, I think I have found the likely cause for some (most?) of the infamous “oops! something has gone wrong” error messages in wheezy.