gnats_4.0-2_i386.changes ACCEPTED

Accepted: gnats-user_4.0-2_i386.deb to pool/main/g/gnats/gnats-user_4.0-2_i386.deb gnats_4.0-2.diff.gz to pool/main/g/gnats/gnats_4.0-2.diff.gz gnats_4.0-2.dsc to pool/main/g/gnats/gnats_4.0-2.dsc gnats_4.0-2_i386.deb to pool/main/g/gnats/gnats_4.0-2_i386.deb Announcing to debian-devel-cha

libghttp_1.0.9-13_i386.changes ACCEPTED

Accepted: libghttp-dev_1.0.9-13_i386.deb to pool/main/libg/libghttp/libghttp-dev_1.0.9-13_i386.deb libghttp1_1.0.9-13_i386.deb to pool/main/libg/libghttp/libghttp1_1.0.9-13_i386.deb libghttp_1.0.9-13.diff.gz to pool/main/libg/libghttp/libghttp_1.0.9-13.diff.gz libghttp_1.0.9-13.dsc to pool

libhttp-ghttp-perl_1.07-6_i386.changes ACCEPTED

Accepted: libhttp-ghttp-perl_1.07-6.diff.gz to pool/main/libh/libhttp-ghttp-perl/libhttp-ghttp-perl_1.07-6.diff.gz libhttp-ghttp-perl_1.07-6.dsc to pool/main/libh/libhttp-ghttp-perl/libhttp-ghttp-perl_1.07-6.dsc libhttp-ghttp-perl_1.07-6_i386.deb to pool/main/libh/libhttp-ghttp-perl/libhttp-

Bug#184828: (no subject)

Hello Tobias, There was actually a manpage for bibview that came with the source, it was just never installed. It's actually pretty comprehensive, so I'm going to use that. There's a german translation for it too, so that helps. Thanks for writing the manpage though. If you notice that the upstr

Bug#214225: marked as done (crash while loading module)

Your message dated Mon, 13 Oct 2003 14:21:48 +1000 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 the case it is now your responsibility to reopen t

Bug#212838: marked as done (/etc/ppp/ip-up.d/0xisp-dns not disabled on package removal)

Your message dated Mon, 13 Oct 2003 14:20:51 +1000 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 the case it is now your responsibility to reopen t

Bug#212841: marked as done (xisp: Please support resolvconf)

Your message dated Mon, 13 Oct 2003 14:20:51 +1000 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 the case it is now your responsibility to reopen t

Bug#212842: marked as done (xisp: Can now use dh_installppp)

Your message dated Mon, 13 Oct 2003 14:20:51 +1000 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 the case it is now your responsibility to reopen t

Bug#202496: marked as done (dotfile: make dotfile working with tk8.4)

Your message dated Mon, 13 Oct 2003 14:21:48 +1000 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 the case it is now your responsibility to reopen t

Bug#206505: marked as done (dotfile: crash immediately after startup)

Your message dated Mon, 13 Oct 2003 14:21:48 +1000 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 the case it is now your responsibility to reopen t

Bug#29949: marked as done (xisp: interactions with fvwm are not working properly.)

Your message dated Mon, 13 Oct 2003 14:20:51 +1000 with message-id <[EMAIL PROTECTED]> and subject line Removed 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 the case it is now your responsibility to reopen t