Bug#209873: marked as done (The package description does not follow Debian policy)

2004-06-18 Thread Debian Bug Tracking System
Your message dated Fri, 18 Jun 2004 21:25:34 +0200 with message-id <[EMAIL PROTECTED]> and subject line The bugs don't apply to the version currently in unstable has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#128609: marked as done (dcopperl: long description should be more describing)

2004-06-18 Thread Debian Bug Tracking System
Your message dated Fri, 18 Jun 2004 21:25:34 +0200 with message-id <[EMAIL PROTECTED]> and subject line The bugs don't apply to the version currently in unstable has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#209983: marked as done (The package description does not follow Debian policy)

2004-06-18 Thread Debian Bug Tracking System
Your message dated Fri, 18 Jun 2004 21:25:34 +0200 with message-id <[EMAIL PROTECTED]> and subject line The bugs don't apply to the version currently in unstable has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#104540: marked as done (Bad description?)

2004-06-18 Thread Debian Bug Tracking System
Your message dated Fri, 18 Jun 2004 21:25:34 +0200 with message-id <[EMAIL PROTECTED]> and subject line The bugs don't apply to the version currently in unstable has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#209566: marked as done (The package description does not follow Debian policy)

2004-06-18 Thread Debian Bug Tracking System
Your message dated Fri, 18 Jun 2004 21:25:34 +0200 with message-id <[EMAIL PROTECTED]> and subject line The bugs don't apply to the version currently in unstable has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#128608: marked as done (libdcopc1: long description should be more describeable)

2004-06-18 Thread Debian Bug Tracking System
Your message dated Fri, 18 Jun 2004 21:25:34 +0200 with message-id <[EMAIL PROTECTED]> and subject line The bugs don't apply to the version currently in unstable has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#209729: marked as done (The package description does not follow Debian policy)

2004-06-18 Thread Debian Bug Tracking System
Your message dated Fri, 18 Jun 2004 21:25:34 +0200 with message-id <[EMAIL PROTECTED]> and subject line The bugs don't apply to the version currently in unstable has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not

How to update Squid and SquidGuard configuration file

2004-06-18 Thread Hilaire Fernandes
Hello, I am looking at building a small .deb package for the skolelinux project. This package will just: 1. update the /etc/squid/conf and /etc/squid/squidGuard.conf files with our prefered setting 2. update nightly the blacklist. I am wondering how such a .deb package should cleanly update t

kidnap alhambra

2004-06-18 Thread Ebony Judd
GET your   U N IVERSI T Y     D I PL0 M A Do you want a prosperous future, increased earning powermore money and the respect of all? Ca l l   this number: 1- 315-546-9663 (24 hours) There are no required tests, classes, books, or interviews! Get a   B a chelors, Masters,   M BA, and   D o ctorat