Re: Squeeze release vs. tracker

2011-02-13 Thread Florian Weimer
* Thijs Kinkhorst:

 I've changed the code right after squeeze's release. I've also
 restarted the tracker service. Apparently this is not enough -
 Florian, can you help?

Changing the views required a schema update.  I've switched to
temporary views, and it should work now.

I also fixed the makefile to consider the correct architecture list
for the backports, so the tracker should be updated again.


-- 
To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87zkpzej58@mid.deneb.enyo.de



Re: Squeeze release vs. tracker

2011-02-13 Thread Francesco Poli
On Sun, 13 Feb 2011 22:09:39 +0100 Florian Weimer wrote:

 * Thijs Kinkhorst:
 
  I've changed the code right after squeeze's release. I've also
  restarted the tracker service. Apparently this is not enough -
  Florian, can you help?
 
 Changing the views required a schema update.  I've switched to
 temporary views, and it should work now.
 
 I also fixed the makefile to consider the correct architecture list
 for the backports, so the tracker should be updated again.

Mmmmh: the following URL leads me to a 502 error:

http://security-tracker.debian.org/tracker/status/release/stable


| Proxy Error
| 
| The proxy server received an invalid response from an upstream server.
| The proxy server could not handle the request GET 
/tracker/status/release/stable.
| 
| Reason: Error reading from remote server
| 
| Apache Server at security-tracker.debian.org Port 80



-- 
 http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
 New GnuPG key, see the transition document!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpKFsk7Eqfm6.pgp
Description: PGP signature


Re: Squeeze release vs. tracker

2011-02-13 Thread Michael Gilbert
On Sun, 13 Feb 2011 22:26:07 +0100 Francesco Poli wrote:

 On Sun, 13 Feb 2011 22:09:39 +0100 Florian Weimer wrote:
 
  * Thijs Kinkhorst:
  
   I've changed the code right after squeeze's release. I've also
   restarted the tracker service. Apparently this is not enough -
   Florian, can you help?
  
  Changing the views required a schema update.  I've switched to
  temporary views, and it should work now.
  
  I also fixed the makefile to consider the correct architecture list
  for the backports, so the tracker should be updated again.
 
 Mmmmh: the following URL leads me to a 502 error:
 
 http://security-tracker.debian.org/tracker/status/release/stable
 
 
 | Proxy Error
 | 
 | The proxy server received an invalid response from an upstream server.
 | The proxy server could not handle the request GET 
 /tracker/status/release/stable.
 | 
 | Reason: Error reading from remote server
 | 
 | Apache Server at security-tracker.debian.org Port 80

This is also affecting testing and oldstable, but not unstable for some
reason.  Florian made some other changes today that may have broken
this, but I don't immediately see why.

Mike


-- 
To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20110213163439.75d3a92b.michael.s.gilb...@gmail.com



Re: Squeeze release vs. tracker

2011-02-13 Thread Michael Gilbert
On Sun, 13 Feb 2011 16:34:39 -0500 Michael Gilbert wrote:

 On Sun, 13 Feb 2011 22:26:07 +0100 Francesco Poli wrote:
 
  On Sun, 13 Feb 2011 22:09:39 +0100 Florian Weimer wrote:
  
   * Thijs Kinkhorst:
   
I've changed the code right after squeeze's release. I've also
restarted the tracker service. Apparently this is not enough -
Florian, can you help?
   
   Changing the views required a schema update.  I've switched to
   temporary views, and it should work now.
   
   I also fixed the makefile to consider the correct architecture list
   for the backports, so the tracker should be updated again.
  
  Mmmmh: the following URL leads me to a 502 error:
  
  http://security-tracker.debian.org/tracker/status/release/stable
  
  
  | Proxy Error
  | 
  | The proxy server received an invalid response from an upstream server.
  | The proxy server could not handle the request GET 
  /tracker/status/release/stable.
  | 
  | Reason: Error reading from remote server
  | 
  | Apache Server at security-tracker.debian.org Port 80
 
 This is also affecting testing and oldstable, but not unstable for some
 reason.  Florian made some other changes today that may have broken
 this, but I don't immediately see why.

Nevermind, the pages now exist again.  They must just have been missing
while the database was updated.

Best wishes,
Mike


-- 
To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20110213163606.a9669ba9.michael.s.gilb...@gmail.com



Re: Squeeze release vs. tracker

2011-02-13 Thread Francesco Poli
On Sun, 13 Feb 2011 16:36:06 -0500 Michael Gilbert wrote:

[...]
 Nevermind, the pages now exist again.  They must just have been missing
 while the database was updated.

Yes, it seems so.
And the number of bugs for the various releases seems to be reasonable.

Thanks a lot to everyone involved in the fix!
Bye.

-- 
 http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
 New GnuPG key, see the transition document!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpOa5XnEBqSE.pgp
Description: PGP signature


Bug#507303: marked as done (security-tracker: please provide a per-maintainer report)

2011-02-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Feb 2011 20:57:01 -0500
with message-id 20110213205701.42b85a9d.michael.s.gilb...@gmail.com
and subject line re: security-tracker: please provide a per-maintainer report
has caused the Debian Bug report #507303,
regarding security-tracker: please provide a per-maintainer report
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
507303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: security-tracker
Severity: wishlist

It would be great to provide such report, as to have a link to it on the DDPO.

Cheers,
-- 
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net


signature.asc
Description: This is a digitally signed message part.
---End Message---
---BeginMessage---
I think the work you did a while back fixed this bug, so I'm closing it.

Best wishes,
Mike

---End Message---


Bug#507303: security-tracker: please provide a per-maintainer report

2011-02-13 Thread Raphael Geissert
reopen 507303
thanks

On Sunday 13 February 2011 19:57:01 Michael Gilbert wrote:
 I think the work you did a while back fixed this bug, so I'm closing it.

Er, what work? there's still no per maintainer report, and the data isn't 
being exported to UDD so it can't be implemented that way either.

Cheers,
-- 
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
Archive: http://lists.debian.org/201102132012.39397.geiss...@debian.org



Processed: Re: security-tracker: please provide a per-maintainer report

2011-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reopen 507303
Bug #507303 {Done: Michael Gilbert michael.s.gilb...@gmail.com} 
[security-tracker] security-tracker: please provide a per-maintainer report
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
507303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-security-tracker-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.129764957818116.transcr...@bugs.debian.org



Bug#352954: marked as done (debsecan: please give suite selector on idssi.enyo.de)

2011-02-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Feb 2011 21:19:38 -0500
with message-id 20110213211938.d1f56266.michael.s.gilb...@gmail.com
and subject line re: debsecan: please give suite selector
has caused the Debian Bug report #352954,
regarding debsecan: please give suite selector on idssi.enyo.de
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
352954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: debsecan
Version: 0.4.1
Severity: wishlist

Please add a possibility to idssi.enyo.de/tracker/$ID to specify a
suite to filter out package versions that are not applicable for the
given suite. After this has been implemented, debsecan --suite foo
--format report should give out URLs that restrict the output to the
selected suite.

Greetings
Marc

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.4-zgsrv
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)

Versions of packages debsecan depends on:
ii  debconf [debconf-2.0] 1.4.70 Debian configuration management sy
ii  python2.3.5-5An interactive high-level object-o

Versions of packages debsecan recommends:
ii  cron  3.0pl1-92  management of regular background p
ii  exim4-daemon-light [mail-tran 4.60-3+zg1 lightweight exim MTA (v4) daemon

-- debconf information excluded

---End Message---
---BeginMessage---
 Please add a possibility to idssi.enyo.de/tracker/$ID to specify a
 suite to filter out package versions that are not applicable for the
 given suite. After this has been implemented, debsecan --suite foo
 --format report should give out URLs that restrict the output to the
 selected suite.

this has been available for a while now, try:
$ debsecan --suite squeeze

best wishes,
mike

---End Message---


Bug#479594: marked as done (security-tracker: Modify suite-overview of the web site to not show no-dsa issues by default)

2011-02-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Feb 2011 21:22:43 -0500
with message-id 20110213212243.82972e0a.michael.s.gilb...@gmail.com
and subject line re: security-tracker: Modify suite-overview of the web site to 
not show no-dsa
has caused the Debian Bug report #479594,
regarding security-tracker: Modify suite-overview of the web site to not show 
no-dsa issues by default
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
479594: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: security-tracker
Version: Modify suite-overview of the web site to not show no-dsa issues by 
default
Severity: normal

http://idssi.enyo.de/tracker/status/release/stable lists all no-dsa issues by 
default,
which is confusing for users. They can still be displayed through the link.

Cheers,
Moritz

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=de_DE.UTF-8@euro, LC_CTYPE=de_DE.UTF-8@euro (charmap=UTF-8)


---End Message---
---BeginMessage---
I don't think the defaults should be changed.  If users want to exclude
no-dsa issues, they can click the link.

Best wishes,
Mike

---End Message---