Re: Getting new tracker service code to go live
Hi, * Nico Golde [2010-01-03 22:58]: > * Michael Gilbert [2010-01-03 19:20]: > > If someone can push the latest updates, I think I've solved the > > problem with the latest commit. > > I updated the tracker svn because I think your fix looks good. > [...] Or not, I can't sudo into the sectracker account as I just updated my ldap password and it seems to take some time before it updates on soler... So if anyone is fast, please pull the trigger. Cheers Nico -- Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0xA0A0 For security reasons, all text in this mail is double-rot13 encrypted. pgppTClnmvj6C.pgp Description: PGP signature
Re: Getting new tracker service code to go live
Hi, * Michael Gilbert [2010-01-03 19:20]: > If someone can push the latest updates, I think I've solved the > problem with the latest commit. I updated the tracker svn because I think your fix looks good. Apart from that... I know I haven't been very active recently, still I wonder why you need to implement undiscussed (excuse me if I missed this) tracker features and Thijs is "blindly" committing them. This is not how we should work in my opinion. Cheers Nico -- Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0xA0A0 For security reasons, all text in this mail is double-rot13 encrypted. pgptY8Z6lGf2v.pgp Description: PGP signature
Re: Getting new tracker service code to go live
If someone can push the latest updates, I think I've solved the problem with the latest commit. Thanks, Mike -- To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Getting new tracker service code to go live
On Sun, 03 Jan 2010 13:51:59 + security tracker role wrote: > The error message was: > > Traceback (most recent call last): > File "bin/update-db", line 73, in > 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 all'. 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 Thanks, Mike -- To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Getting new tracker service code to go live
On snein 3 Jannewaris 2010, Michael Gilbert wrote: > I've updated the sql logic to workaround a bug in lenny's aspw (and > the code is actually now a bit cleaner...for sql anyway). Please push > this new commit to the live tracker. Ulib/python/security_db.py Updated to revision 13701. -- To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Getting new tracker service code to go live
On Sun, 3 Jan 2010 00:08:49 -0500 Michael Gilbert wrote: > On Sat, 02 Jan 2010 16:48:16 -0600 Raphael Geissert wrote: > > > Thijs Kinkhorst wrote: > > > svn up > > > Ulib/python/security_db.py > > > Ulib/python/bugs.py > > > Ubin/tracker_service.py > > > Abin/generate-sequential-cve-ids > > > Ubin/test-web-server > > > Abin/generate-sequential-bugs > > > Ubin/check-new-issues > > > Updated to revision 13699. > > > > > > > > > > Which now completely broke it due to bad SQL. > > Michael, please fix it soon > > I have just been able to reproduce the problem in a lenny vm. It > doesn't exist on sid (where I have been doing development). Lesson > learned: do tracker tracker development on a system running stable. > I'll have a fix ready ASAP. I've updated the sql logic to workaround a bug in lenny's aspw (and the code is actually now a bit cleaner...for sql anyway). Please push this new commit to the live tracker. I appologize for the bad commit. I hadn't considered that the tracker would be running with older (potentially buggy) libraries. In the future, I will be doing my tracker development on stable to avoid such inconsistencies. Mike -- To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Getting new tracker service code to go live
On Sat, 02 Jan 2010 16:48:16 -0600 Raphael Geissert wrote: > Thijs Kinkhorst wrote: > > svn up > > Ulib/python/security_db.py > > Ulib/python/bugs.py > > Ubin/tracker_service.py > > Abin/generate-sequential-cve-ids > > Ubin/test-web-server > > Abin/generate-sequential-bugs > > Ubin/check-new-issues > > Updated to revision 13699. > > > > > > Which now completely broke it due to bad SQL. > Michael, please fix it soon I have just been able to reproduce the problem in a lenny vm. It doesn't exist on sid (where I have been doing development). Lesson learned: do tracker tracker development on a system running stable. I'll have a fix ready ASAP. Mike -- To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Getting new tracker service code to go live
Thijs Kinkhorst wrote: > svn up > Ulib/python/security_db.py > Ulib/python/bugs.py > Ubin/tracker_service.py > Abin/generate-sequential-cve-ids > Ubin/test-web-server > Abin/generate-sequential-bugs > Ubin/check-new-issues > Updated to revision 13699. > > Which now completely broke it due to bad SQL. Michael, please fix it soon . Regards, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Getting new tracker service code to go live
On sneon 2 Jannewaris 2010, Michael Gilbert wrote: > It appears that new commits to the tracker service do not > automatically go live (based on the above syntax checker message > recieved from sectrac...@soler.debian.org). Anyway, can someone with > appropriate permissions update the repo there This is what I did: sectrac...@soler:/srv/security-tracker.debian.org/website/secure-testing$ svn up Ulib/python/security_db.py Ulib/python/bugs.py Ubin/tracker_service.py Abin/generate-sequential-cve-ids Ubin/test-web-server Abin/generate-sequential-bugs Ubin/check-new-issues Updated to revision 13699. Thijs -- To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Getting new tracker service code to go live
On Sat, Jan 2, 2010 at 3:43 PM, security tracker role wrote: > The error message was: > > data/CVE/list:1516: invalid special version '- qt4-x11 (bug > #561760)' in package entry > make: *** [all] Error 1 Hi, It appears that new commits to the tracker service do not automatically go live (based on the above syntax checker message recieved from sectrac...@soler.debian.org). Anyway, can someone with appropriate permissions update the repo there or make it so that commits to secure-testing transition there automatically? Thanks, Mike -- To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
