[Secure-testing-commits] Processing r14165 failed

2010-02-28 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14165 failed

2010-02-28 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14165 failed

2010-02-28 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14165 failed

2010-02-28 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14165 failed

2010-02-28 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14165 failed

2010-02-28 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14165 failed

2010-02-28 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14165 failed

2010-02-28 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14165 failed

2010-02-28 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14165 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14165 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14166 failed

2010-03-01 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2004-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14308 failed

2010-03-20 Thread security tracker role
The error message was: data/DSA/list: 3: error: bug name DSA-2020-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14308 failed

2010-03-20 Thread security tracker role
The error message was: data/DSA/list: 3: error: bug name DSA-2020-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14308 failed

2010-03-20 Thread security tracker role
The error message was: data/DSA/list: 3: error: bug name DSA-2020-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14400 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14400 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14401 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14402 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14402 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14402 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14402 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14402 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14402 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14402 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14402 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14403 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14403 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14403 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14403 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14403 failed

2010-04-04 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14403 failed

2010-04-05 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14403 failed

2010-04-05 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14403 failed

2010-04-05 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14404 failed

2010-04-05 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14404 failed

2010-04-05 Thread security tracker role
The error message was: data/CVE/list:1: ITPed package chromium is in the archive data/CVE/list:8: ITPed package chromium is in the archive data/CVE/list:15: ITPed package chromium is in the archive data/CVE/list:18: ITPed package chromium is in the archive data/CVE/list:21: ITPed package chromium

[Secure-testing-commits] Processing r14604 failed

2010-05-05 Thread security tracker role
The error message was: data/CVE/list:447: ITPed package chromium-browser is in the archive data/CVE/list:451: ITPed package chromium-browser is in the archive data/CVE/list:455: ITPed package chromium-browser is in the archive data/CVE/list:459: ITPed package chromium-browser is in the archive dat

[Secure-testing-commits] Processing r14604 failed

2010-05-05 Thread security tracker role
The error message was: data/CVE/list:447: ITPed package chromium-browser is in the archive data/CVE/list:451: ITPed package chromium-browser is in the archive data/CVE/list:455: ITPed package chromium-browser is in the archive data/CVE/list:459: ITPed package chromium-browser is in the archive dat

[Secure-testing-commits] Processing r14616 failed

2010-05-06 Thread security tracker role
The error message was: data/CVE/list:19653: ITPed package jbig2dec is in the archive make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-te

[Secure-testing-commits] Processing r14731 failed

2010-05-23 Thread security tracker role
The error message was: data/DSA/list: 379: error: cross reference to CVE-2009-1829 appears multiple times make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mail

[Secure-testing-commits] Processing r14741 failed

2010-05-24 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2052-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r14741 failed

2010-05-24 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2052-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15082 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15082 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15082 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15082 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15082 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15082 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15082 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15082 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15082 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15082 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15083 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15083 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15083 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15083 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15083 failed

2010-07-31 Thread security tracker role
The error message was: data/DSA/list: 4: error: bug name DSA-2078-1 is not unique make: *** [all] Error 1 ___ Secure-testing-commits mailing list Secure-testing-commits@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/secure-testi

[Secure-testing-commits] Processing r15183 failed

2010-08-22 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 834, in readBugs raise InsertError(errors) File "/srv/

[Secure-testing-commits] Processing r15183 failed

2010-08-22 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 834, in readBugs raise InsertError(errors) File "/srv/

[Secure-testing-commits] Processing r15183 failed

2010-08-22 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 834, in readBugs raise InsertError(errors) File "/srv/

[Secure-testing-commits] Processing r15184 failed

2010-08-22 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 834, in readBugs raise InsertError(errors) File "/srv/

[Secure-testing-commits] Processing r15184 failed

2010-08-22 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 834, in readBugs raise InsertError(errors) File "/srv/

[Secure-testing-commits] Processing r15184 failed

2010-08-22 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 834, in readBugs raise InsertError(errors) File "/srv/

[Secure-testing-commits] Processing r15184 failed

2010-08-22 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 834, in readBugs raise InsertError(errors) File "/srv/

[Secure-testing-commits] Processing r15184 failed

2010-08-22 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 834, in readBugs raise InsertError(errors) File "/srv/

[Secure-testing-commits] Processing r15184 failed

2010-08-22 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 834, in readBugs raise InsertError(errors) File "/srv/

[Secure-testing-commits] Processing r15184 failed

2010-08-22 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 834, in readBugs raise InsertError(errors) File "/srv/

[Secure-testing-commits] Processing r15184 failed

2010-08-22 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 834, in readBugs raise InsertError(errors) File "/srv/

[Secure-testing-commits] Processing r15184 failed

2010-08-22 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 834, in readBugs raise InsertError(errors) File "/srv/

[Secure-testing-commits] Processing r15455 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15455 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15455 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15456 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15457 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15458 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15458 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15458 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15458 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15458 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15458 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15458 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15458 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15458 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15458 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

[Secure-testing-commits] Processing r15458 failed

2010-10-11 Thread security tracker role
The error message was: Traceback (most recent call last): File "bin/update-db", line 40, in warnings = db.readBugs(cursor, 'data') File "/srv/security-tracker.debian.org/website/secure-testing/lib/python/security_db.py", line 764, in readBugs read_one(cls(path + name)) File "/srv

  1   2   3   4   5   6   7   8   9   10   >