On i386, it doesn't segfault if using the -Write_Phonemes option or
the undocumented -Write_Klatt option, but does segfault when using
-Write_Ulaw, so the error looks to be in the conversion from the klatt
representation to ulaw.
--
Neil Muller
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
like Adding the -verbose flag may
provide more information about this error could be added to the
currrent text.
Arguably, wodim should ignore the dev=... option when used with
-devices or -scanbus .
--
Neil Muller
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
It looks like this is a numpy bug, although the way pylint imports
submodules, which exposes the bug, may cause issues with other
packages.
The upstream bugs for this issue are:
pylint: http://www.logilab.org/ticket/23009
numpy: http://projects.scipy.org/numpy/ticket/1462
--
Neil Muller
This has been fixed upstream with a slightly different patch. See
http://sourceforge.net/mailarchive/message.php?msg_id=27799824
The fix will be included in the next version of SQLObject - see
http://sourceforge.net/mailarchive/message.php?msg_id=28310875
--
Neil Muller
--
To UNSUBSCRIBE
This has been reported to SQLObject upstream. The issue appears to be
due to a change in behaviour with sqlite 3.8, but the best approach to
fixing it is still being investigated.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
a8362b2b9cca0b81ac49056de780b8d218b452c8
Author: Neil Muller <drnlmuller+deb...@gmail.com>
Date: Thu Sep 1 11:24:29 2016 +0200
Update changelog
diff --git a/debian/changelog b/debian/changelog
index 339195c..06675dd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+sqlobject (3.1.0+
Control: severity -1 minor
Removing support for user deletion was specifically asked for when the
package was adopted into PAPT. I also don't see any compelling reason
to re-add it from policy, so I'm downgrading this bug.
If there are files being left after the package is purged, please
This is due to a change in sqlite 3.15 which breaks a incorrect, but
previously harmless, assumption made by sqlobject.
A possible fix has been submitted upstream.
78e7ea0770a792b768e2b45a76df6b6d60985168
Author: Neil Muller <drnlmuller+deb...@gmail.com>
Date: Wed Nov 2 18:34:30 2016 +0200
Add changelog entry
diff --git a/debian/changelog b/debian/changelog
index b1b5936..f4718f0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+sqlobject
This specific failure has been fixed in SQLObject 3.3.0 .
However, 3.3.0 fails sporadically with python 3.6 and python 3.5 due
to a different error. This is still being investigated (See
https://github.com/sqlobject/sqlobject/issues/135 ). Once that issue
has been solved, I'll look at uploading
28af1242d64524d4e5057b8d4311ba41e1140d23
Author: Neil Muller <drnlmuller+deb...@gmail.com>
Date: Thu Aug 3 16:45:13 2017 +0200
Update for sqlobject 3.3.0
Drop obsolete patches.
Change to using sphinx to build docs.
Backport upstream patch needed to run tests with python 3.6.
diff
11 matches
Mail list logo