On Tue, Apr 01, 2008 at 01:39:19AM -0700, Steve Langasek wrote:
> Still reproducible.
Any oddness with
./test_mutex -t 5
in the obj/ directory of a 4.6.21-7 source tree after a
debian/rules build ?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contac
On Thu, Mar 27, 2008 at 07:41:58AM -0400, Clint Adams wrote:
> On Thu, Mar 06, 2008 at 09:51:00PM +, Steve Langasek wrote:
> > I'm afraid it's still reproducible for me with 4.6.21-6.
> How about 4.6.21-7?
Still reproducible.
--
Steve Langasek Give me a lever long enough a
On Thu, Mar 06, 2008 at 09:51:00PM +, Steve Langasek wrote:
> I'm afraid it's still reproducible for me with 4.6.21-6.
How about 4.6.21-7?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Mar 10, 2008 at 09:31:52PM -0400, Clint Adams wrote:
> On Fri, Mar 07, 2008 at 05:03:54PM -0800, Steve Langasek wrote:
> > For my part, I don't know. A search on bugs.python.org does turn up this
> > entry, which looks like it might be related:
> >http://bugs.python.org/issue834461
>
On Fri, Mar 07, 2008 at 05:03:54PM -0800, Steve Langasek wrote:
> For my part, I don't know. A search on bugs.python.org does turn up this
> entry, which looks like it might be related:
>
>http://bugs.python.org/issue834461
>
> I don't know that this explains the empty results from d.get(),
On Fri, Mar 07, 2008 at 10:49:47AM -0500, Clint Adams wrote:
> On Fri, Mar 07, 2008 at 12:40:08AM -0800, Steve Langasek wrote:
> > The failing test is "HashSimpleThreaded.test02_SimpleLocks"; it starts five
> > threads that try to write to a database of (python) type "db.DB_HASH" using
> > no trans
On Fri, Mar 07, 2008 at 12:40:08AM -0800, Steve Langasek wrote:
> The failing test is "HashSimpleThreaded.test02_SimpleLocks"; it starts five
> threads that try to write to a database of (python) type "db.DB_HASH" using
> no transactions, and occasionally reads back the results. The reading fails
On Thu, Mar 06, 2008 at 05:39:19PM -0500, Clint Adams wrote:
> On Thu, Mar 06, 2008 at 09:51:00PM +, Steve Langasek wrote:
> > I'm afraid it's still reproducible for me with 4.6.21-6.
> Okay. Do we know what's happening unexpectedly?
The failing test is "HashSimpleThreaded.test02_SimpleLocks"
On Thu, Mar 06, 2008 at 09:51:00PM +, Steve Langasek wrote:
> I'm afraid it's still reproducible for me with 4.6.21-6.
Okay. Do we know what's happening unexpectedly?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, Mar 06, 2008 at 03:12:04PM -0500, Clint Adams wrote:
> On Wed, Mar 05, 2008 at 01:31:00PM -0800, Steve Langasek wrote:
> > Overriding this check and building against db4.6 leads to the following
> > (intermittent) test failure on SMP systems:
> Can someone with an SMP system that exhibits
On Wed, Mar 05, 2008 at 01:31:00PM -0800, Steve Langasek wrote:
> Overriding this check and building against db4.6 leads to the following
> (intermittent) test failure on SMP systems:
Can someone with an SMP system that exhibits this behavior try the
python testsuite with libdb4.6 4.6.21-6 in case
FWIW, here's the problem with db4.6 in python.
Upstream has disabled building python2.5 with db4.6 in setup.py with the
following explanation:
max_db_ver = (4, 5)
# NOTE: while the _bsddb.c code links against BerkeleyDB 4.6.x
# we leave that version disabled by default as
reassign 469221 apt-listchanges
thanks
there's no bug about this in python; it's unfortunate that we had to
downgrade the db version, but it has to be handled in apt-listchanges.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
reassing 469221 python2.4
# breaks other packages.
severity 469221 grave
thanks
On Tue, Mar 04, 2008 at 02:19:48AM +, Mark Robinson wrote:
> This update worked fine, but the dist-upgrade immediately following failed:
The bug is the fact that python downgraded its libdb version, breaking
eve
This update worked fine, but the dist-upgrade immediately following failed:
> Tue Mar 04 12:44:12 [EMAIL PROTECTED]:~# aptitude -vV upgrade
> W: The "upgrade" command is deprecated; use "safe-upgrade" instead.
> Reading package lists... Done
> Building dependency tree
> Reading state information..
Package: apt-listchanges
Version: 2.82
Severity: normal
Hi Pierre!
Today while upgrading my system, I saw this:
Reading changelogs... Done
Traceback (most recent call last):
File "/usr/bin/apt-listchanges", line 227, in ?
main()
File "/usr/bin/apt-listchanges", line 148, in main
seen
16 matches
Mail list logo
