[arch-dev-public] [signoff] db-5.1.25-1
Upstream bug fix release. Signoff both, Allan BTW, if anyone wants to take over maintainership of this package, then let me know.
Le 3 février 2011 08:16:02, Allan McRae a écrit :
Upstream bug fix release.
Signoff both, Allan
BTW, if anyone wants to take over maintainership of this package, then let me know.
Tested using the python 2 bsddb interface. Signoff x86_64. Stéphane
On 04/02/11 00:59, Stéphane Gaudreault wrote:
Le 3 février 2011 08:16:02, Allan McRae a écrit :
Upstream bug fix release.
Signoff both, Allan
BTW, if anyone wants to take over maintainership of this package, then let me know.
Tested using the python 2 bsddb interface. Signoff x86_64.
Stéphane
Anyone for i686?
[2011-02-07 18:21:42 +1000] Allan McRae:
On 04/02/11 00:59, Stéphane Gaudreault wrote:
Le 3 février 2011 08:16:02, Allan McRae a écrit :
Upstream bug fix release.
Signoff both, Allan
BTW, if anyone wants to take over maintainership of this package, then let me know.
Tested using the python 2 bsddb interface. Signoff x86_64.
Stéphane
Anyone for i686?
Here on i686, `python2 /usr/lib/python2.7/bsddb/test/test_all.py` outputs many more errors than on x86_64, errors that weren't there with db-5.1.19-3 (and, in fact, the test suite crashes). Other than that, I have noticed nothing weird on my i686 system running the new db for a few days (not that I use it intensively, though). -- Gaetan
[2011-02-07 10:27:23 +0100] Gaetan Bisson:
`python2 /usr/lib/python2.7/bsddb/test/test_all.py`
Output on i686 with db-5.1.19-3: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Berkeley DB 5.1.19: (August 27, 2010) bsddb.db.version(): (5, 1, 19) bsddb.db.__version__: 4.8.4.1 bsddb.db.cvsid: $Id: _bsddb.c 86317 2010-11-08 12:57:59Z jesus.cea $ py module: /usr/lib/python2.7/bsddb/__init__.py extension module: /usr/lib/python2.7/bsddb/__init__.py python version: 2.7.1 (r271:86832, Jan 6 2011, 11:51:37) [GCC 4.5.2] My pid: 15650 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ................................................................................................................................................................................................................................................................................................................................F............................................................................................................................................................... ====================================================================== FAIL: test_setget_cachesize (test_dbenv.DBEnv_general) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.7/bsddb/test/test_dbenv.py", line 176, in test_setget_cachesize self.assertEqual(cachesize2, self.env.get_cachesize()) AssertionError: Tuples differ: (0, 1312348, 5) != (0, 1351680, 5) First differing element 1: 1312348 1351680 - (0, 1312348, 5) ? ^^^ + (0, 1351680, 5) ? + ^ + ---------------------------------------------------------------------- Ran 480 tests in 107.399s FAILED (failures=1) Output on x86_64 with db-5.1.25-1: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Berkeley DB 5.1.19: (August 27, 2010) bsddb.db.version(): (5, 1, 25) bsddb.db.__version__: 4.8.4.1 bsddb.db.cvsid: $Id: _bsddb.c 86317 2010-11-08 12:57:59Z jesus.cea $ py module: /usr/lib/python2.7/bsddb/__init__.py extension module: /usr/lib/python2.7/bsddb/__init__.py python version: 2.7.1 (r271:86832, Jan 6 2011, 11:45:30) [GCC 4.5.2] My pid: 12211 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ..........................................F.....................................................................................................................................................................................................................................................................................F............................................................................................................................................................... ====================================================================== FAIL: test00_version (test_basics.VersionTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.7/bsddb/test/test_basics.py", line 30, in test00_version db.DB_VERSION_PATCH)) AssertionError: Tuples differ: (5, 1, 25) != (5, 1, 19) First differing element 2: 25 19 - (5, 1, 25) ? ^^ + (5, 1, 19) ? ^^ ====================================================================== FAIL: test_setget_cachesize (test_dbenv.DBEnv_general) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.7/bsddb/test/test_dbenv.py", line 176, in test_setget_cachesize self.assertEqual(cachesize2, self.env.get_cachesize()) AssertionError: Tuples differ: (0, 1312792, 5) != (0, 1351680, 5) First differing element 1: 1312792 1351680 - (0, 1312792, 5) + (0, 1351680, 5) ---------------------------------------------------------------------- Ran 480 tests in 83.698s FAILED (failures=2) Output on i686 with db-5.1.25-1: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Berkeley DB 5.1.19: (August 27, 2010) bsddb.db.version(): (5, 1, 25) bsddb.db.__version__: 4.8.4.1 bsddb.db.cvsid: $Id: _bsddb.c 86317 2010-11-08 12:57:59Z jesus.cea $ py module: /usr/lib/python2.7/bsddb/__init__.py extension module: /usr/lib/python2.7/bsddb/__init__.py python version: 2.7.1 (r271:86832, Jan 6 2011, 11:51:37) [GCC 4.5.2] My pid: 16066 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= .................EE........................F......................................................................................EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE.....................................................................................................................................................F........EEEEEEEE...EE.........................................................................EException bsddb.db.DBRunRecoveryError: (-30973, 'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: fatal region error detected; run recovery') in <bound method bsdTableDB.__del__ of <bsddb.dbtables.bsdTableDB instance at 0x9285acc>> ignored EException bsddb.db.DBRunRecoveryError: (-30973, 'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: fatal region error detected; run recovery') in <bound method bsdTableDB.__del__ of <bsddb.dbtables.bsdTableDB instance at 0x9285acc>> ignored EException bsddb.db.DBRunRecoveryError: (-30973, 'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: fatal region error detected; run recovery') in <bound method bsdTableDB.__del__ of <bsddb.dbtables.bsdTableDB instance at 0x9285acc>> ignored EException bsddb.db.DBRunRecoveryError: (-30973, 'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: fatal region error detected; run recovery') in <bound method bsdTableDB.__del__ of <bsddb.dbtables.bsdTableDB instance at 0x9285acc>> ignored EException bsddb.db.DBRunRecoveryError: (-30973, 'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: fatal region error detected; run recovery') in <bound method bsdTableDB.__del__ of <bsddb.dbtables.bsdTableDB instance at 0x9285acc>> ignored EException bsddb.db.DBRunRecoveryError: (-30973, 'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: fatal region error detected; run recovery') in <bound method bsdTableDB.__del__ of <bsddb.dbtables.bsdTableDB instance at 0x9285acc>> ignored EException bsddb.db.DBRunRecoveryError: (-30973, 'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: fatal region error detected; run recovery') in <bound method bsdTableDB.__del__ of <bsddb.dbtables.bsdTableDB instance at 0x9285acc>> ignored EException bsddb.db.DBRunRecoveryError: (-30973, 'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: fatal region error detected; run recovery') in <bound method bsdTableDB.__del__ of <bsddb.dbtables.bsdTableDB instance at 0x9285acc>> ignored EEEE.....E........................EEEE..................Exception in thread writer 0: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 530, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 483, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.7/bsddb/test/test_thread.py", line 408, in writerThread txn.commit() DBRunRecoveryError: (-30973, 'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: Invalid argument') -- Gaetan
Le 7 février 2011 04:27:23, Gaetan Bisson a écrit :
[2011-02-07 18:21:42 +1000] Allan McRae:
On 04/02/11 00:59, Stéphane Gaudreault wrote:
Le 3 février 2011 08:16:02, Allan McRae a écrit :
Upstream bug fix release.
Signoff both, Allan
BTW, if anyone wants to take over maintainership of this package, then let me know.
Tested using the python 2 bsddb interface. Signoff x86_64.
Stéphane
Anyone for i686?
Here on i686, `python2 /usr/lib/python2.7/bsddb/test/test_all.py` outputs many more errors than on x86_64, errors that weren't there with db-5.1.19-3 (and, in fact, the test suite crashes). Other than that, I have noticed nothing weird on my i686 system running the new db for a few days (not that I use it intensively, though).
I previously tested on x86_64 with a very simple script. If I try with python2 /usr/lib/python2.7/bsddb/test/test_all.py * db 5.1.19-3 : Only one test fail : test_setget_cachesize * db 5.1.25-1 : Two tests fails : test00_version and test_setget_cachesize. If I rebuild python2, test00_version pass on x86_64. Stéphane -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Berkeley DB 5.1.19: (August 27, 2010) bsddb.db.version(): (5, 1, 19) bsddb.db.__version__: 4.8.4.1 bsddb.db.cvsid: $Id: _bsddb.c 86317 2010-11-08 12:57:59Z jesus.cea $ py module: /usr/lib/python2.7/bsddb/__init__.py extension module: /usr/lib/python2.7/bsddb/__init__.py python version: 2.7.1 (r271:86832, Jan 6 2011, 11:45:30) [GCC 4.5.2] My pid: 4599 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ................................................................................................................................................................................................................................................................................................................................F............................................................................................................................................................... ====================================================================== FAIL: test_setget_cachesize (test_dbenv.DBEnv_general) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.7/bsddb/test/test_dbenv.py", line 176, in test_setget_cachesize self.assertEqual(cachesize2, self.env.get_cachesize()) AssertionError: Tuples differ: (0, 1312792, 5) != (0, 1351680, 5) First differing element 1: 1312792 1351680 - (0, 1312792, 5) + (0, 1351680, 5) ---------------------------------------------------------------------- Ran 480 tests in 15.355s FAILED (failures=1)
Le 7 février 2011 14:24:28, Stéphane Gaudreault a écrit :
Le 7 février 2011 04:27:23, Gaetan Bisson a écrit :
[2011-02-07 18:21:42 +1000] Allan McRae:
On 04/02/11 00:59, Stéphane Gaudreault wrote:
Le 3 février 2011 08:16:02, Allan McRae a écrit :
Upstream bug fix release.
Signoff both, Allan
BTW, if anyone wants to take over maintainership of this package, then let me know.
Tested using the python 2 bsddb interface. Signoff x86_64.
Stéphane
Anyone for i686?
Here on i686, `python2 /usr/lib/python2.7/bsddb/test/test_all.py` outputs many more errors than on x86_64, errors that weren't there with db-5.1.19-3 (and, in fact, the test suite crashes). Other than that, I have noticed nothing weird on my i686 system running the new db for a few days (not that I use it intensively, though).
I previously tested on x86_64 with a very simple script. If I try with python2 /usr/lib/python2.7/bsddb/test/test_all.py
* db 5.1.19-3 : Only one test fail : test_setget_cachesize * db 5.1.25-1 : Two tests fails : test00_version and test_setget_cachesize.
If I rebuild python2, test00_version pass on x86_64.
Stéphane
python2-2.7.1-5 is in testing. Gaetan confirmed that this update fixed the issue on i686. Other interface (python-bsddb, ruby, etc) might also need to be tested. Stéphane
On 08/02/11 06:47, Stéphane Gaudreault wrote:
Le 7 février 2011 14:24:28, Stéphane Gaudreault a écrit :
Le 7 février 2011 04:27:23, Gaetan Bisson a écrit :
[2011-02-07 18:21:42 +1000] Allan McRae:
On 04/02/11 00:59, Stéphane Gaudreault wrote:
Le 3 février 2011 08:16:02, Allan McRae a écrit :
Upstream bug fix release.
Signoff both, Allan
BTW, if anyone wants to take over maintainership of this package, then let me know.
Tested using the python 2 bsddb interface. Signoff x86_64.
Stéphane
Anyone for i686?
Here on i686, `python2 /usr/lib/python2.7/bsddb/test/test_all.py` outputs many more errors than on x86_64, errors that weren't there with db-5.1.19-3 (and, in fact, the test suite crashes). Other than that, I have noticed nothing weird on my i686 system running the new db for a few days (not that I use it intensively, though).
I previously tested on x86_64 with a very simple script. If I try with python2 /usr/lib/python2.7/bsddb/test/test_all.py
* db 5.1.19-3 : Only one test fail : test_setget_cachesize * db 5.1.25-1 : Two tests fails : test00_version and test_setget_cachesize.
If I rebuild python2, test00_version pass on x86_64.
Stéphane
python2-2.7.1-5 is in testing. Gaetan confirmed that this update fixed the issue on i686.
Other interface (python-bsddb, ruby, etc) might also need to be tested.
Great - thanks for figuring this out. I will leave db in [testing] for another week or so and then move it and python2 if no further issues are reported. Allan
Le 7 février 2011 23:18:57, Allan McRae a écrit :
On 08/02/11 06:47, Stéphane Gaudreault wrote:
Le 7 février 2011 14:24:28, Stéphane Gaudreault a écrit :
Le 7 février 2011 04:27:23, Gaetan Bisson a écrit :
[2011-02-07 18:21:42 +1000] Allan McRae:
On 04/02/11 00:59, Stéphane Gaudreault wrote:
Le 3 février 2011 08:16:02, Allan McRae a écrit : > Upstream bug fix release. > > Signoff both, > Allan > > > BTW, if anyone wants to take over maintainership of this package, > then let me know.
Tested using the python 2 bsddb interface. Signoff x86_64.
Stéphane
Anyone for i686?
Here on i686, `python2 /usr/lib/python2.7/bsddb/test/test_all.py` outputs many more errors than on x86_64, errors that weren't there with db-5.1.19-3 (and, in fact, the test suite crashes). Other than that, I have noticed nothing weird on my i686 system running the new db for a few days (not that I use it intensively, though).
I previously tested on x86_64 with a very simple script. If I try with python2 /usr/lib/python2.7/bsddb/test/test_all.py
* db 5.1.19-3 : Only one test fail : test_setget_cachesize * db 5.1.25-1 : Two tests fails : test00_version and test_setget_cachesize.
If I rebuild python2, test00_version pass on x86_64.
Stéphane
python2-2.7.1-5 is in testing. Gaetan confirmed that this update fixed the issue on i686.
Other interface (python-bsddb, ruby, etc) might also need to be tested.
Great - thanks for figuring this out.
I will leave db in [testing] for another week or so and then move it and python2 if no further issues are reported.
Allan
There is a similar issue with python-bsddb. This pkg will needs to be rebuilded with python 3.2.0 very soon, so I will wait a little before rebuilding it. Stéphane
participants (3)
-
Allan McRae
-
Gaetan Bisson
-
Stéphane Gaudreault