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

Re: Getting new tracker service code to go live

On Sun, 03 Jan 2010 13:51:59 +0000 security tracker role wrote:

> The error message was:
> Traceback (most recent call last):
>   File "bin/update-db", line 73, in <module>
>     warnings = db.calculateVulnerabilities(cursor)
>   File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 1159, in calculateVulnerabilities
>     self._calcTesting(c, bug_name, 'oldstable', 'etch')
>   File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 1288, in _calcTesting
>     (bug_name, suite, status, pkgs))
>   File "apsw.c", line 4238, in resetcursor
> apsw.ConstraintError: ConstraintError: constraint failed
> make: *** [all] Error 1

I can't reproduce this problem with the local tracker data that I have
(on lenny or sid). My best guess is that there is a corner case in
the live tracker where 'status' is not getting assigned, but I don't see
the hole for that to happen.

I've commited a fix that may resolve the issue.  It may also be that
the current database needs to be fully regenerated due to the new
code.  So maybe try deleting data/security.db and then running 'make

If not, can someone insert the following line above line 1285 in
security_db.py and send me the output of 'make all' on the live tracker?

    print bug_name , suite , status , pkgs


Reply to: