Package: wnpp
Version: N/A; reported 2002-03-30
I don't think you gain allot by waiting on librte. The ftp master certainly
won't install librte any faster in the archive. The only effect it has
has is that your users don't have a zapping package ready to apt-get
install anymore.
Sjoerd
-- Sy
Your message dated Sat, 30 Mar 2002 04:15:19 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Package Uploaded
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
Processing commands for [EMAIL PROTECTED]:
> retitle 91883 RFP: xscrabble -- X version of the popular board game, for 1 to
> 4 players
Bug#91883: ITP: xscrabble -- X version of the popular board game, for 1 to 4
players
Changed Bug title.
> thanks
Stopping processing here.
Please contact me if
Processing commands for [EMAIL PROTECTED]:
> retitle 138796 ITP: SpiderMonkey, the Mozilla JavaScript engine
Bug#138796: wnpp: ITP: SpiderMonkey, the Mozilla JavaScript engine
Changed Bug title.
> retitle 138978 RFP: ficl -- Forth Inspired Command Language
Bug#138978: [RFP]: ficl -- Forth Inspire
Package: wnpp
Severity: normal
I'd like to pass knews on to somebody who actually uses it. It's a nice
enough little newsreader, but I'm too attached to trn. There are a
couple of non-serious bugs I'd like to see fixed, but I don't really
have the time or inclination to debug them myself.
*
Processing commands for [EMAIL PROTECTED]:
> severity 87816 normal
Bug#87816: ITA: wily -- clone of plan9 `acme' text editor
Severity set to `normal'.
> severity 136125 wishlist
Bug#136125: ITP: cban -- Displays current traffic on a selected interface
Severity set to `wishlist'.
> thanks
Stoppin
Your message dated Sat, 30 Mar 2002 13:12:33 +
with message-id <[EMAIL PROTECTED]>
and subject line Closing NMU-fixed wnpp bugs
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 respon
Your message dated Sat, 30 Mar 2002 13:12:33 +
with message-id <[EMAIL PROTECTED]>
and subject line Closing NMU-fixed wnpp bugs
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 respon
Your message dated Sat, 30 Mar 2002 13:12:33 +
with message-id <[EMAIL PROTECTED]>
and subject line Closing NMU-fixed wnpp bugs
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 respon
Your message dated Sat, 30 Mar 2002 13:12:33 +
with message-id <[EMAIL PROTECTED]>
and subject line Closing NMU-fixed wnpp bugs
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 respon
Your message dated Sat, 30 Mar 2002 13:01:00 +
with message-id <[EMAIL PROTECTED]>
and subject line libparse-yapp-perl already in Debian
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 yo
Your message dated Sat, 30 Mar 2002 13:01:00 +
with message-id <[EMAIL PROTECTED]>
and subject line libparse-yapp-perl already in Debian
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 yo
Your message dated Sat, 30 Mar 2002 13:06:21 +
with message-id <[EMAIL PROTECTED]>
and subject line ndiff in Debian
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
Your message dated Sat, 30 Mar 2002 13:14:14 +
with message-id <[EMAIL PROTECTED]>
and subject line remstats in Debian
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
Your message dated Sat, 30 Mar 2002 13:20:32 +
with message-id <[EMAIL PROTECTED]>
and subject line glaxium removed from Debian
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 respon
Your message dated Sat, 30 Mar 2002 13:26:05 +
with message-id <[EMAIL PROTECTED]>
and subject line kismet in Debian
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
Your message dated Sat, 30 Mar 2002 13:15:38 +
with message-id <[EMAIL PROTECTED]>
and subject line minpack in Debian
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 t
Your message dated Sat, 30 Mar 2002 13:16:33 +
with message-id <[EMAIL PROTECTED]>
and subject line yencode in Debian
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 t
Your message dated Sat, 30 Mar 2002 13:27:14 +
with message-id <[EMAIL PROTECTED]>
and subject line liboop in Debian
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
Colin Watson wrote:
> (Actually, it looks like all of these bugs were
> maintainer uploads that got treated as NMUs because a sponsor used the
> -m flag to dpkg-buildpackage.)
So they were all NMUs by Chris Hanson.
The maintainer is Avery Pennarun.
--
Thomas
signature.asc
Description: This is a
On Sat, Mar 30, 2002 at 08:41:20AM -0500, Thomas Hood wrote:
> Colin Watson wrote:
> > (Actually, it looks like all of these bugs were maintainer uploads
> > that got treated as NMUs because a sponsor used the -m flag to
> > dpkg-buildpackage.)
>
> So they were all NMUs by Chris Hanson.
> The main
On Sat, Mar 30, 2002 at 08:41:20AM -0500, Thomas Hood wrote:
> Colin Watson wrote:
> > (Actually, it looks like all of these bugs were maintainer uploads
> > that got treated as NMUs because a sponsor used the -m flag to
> > dpkg-buildpackage.)
>
> So they were all NMUs by Chris Hanson.
Oh, and t
On Sat, 2002-03-30 at 08:59, Colin Watson wrote:
> Er, right, OK. That's not what the Maintainer: field in powermgmt-base
> says though.
You're right: I am listed as the maintainer on powermgmt-base.
However it was Chris Hanson who did the upload for me. He has also
been doing all the recent apm
Processing commands for [EMAIL PROTECTED]:
> close 138441
Bug#138441: ITP: kernel-patch-usagi -- Another IPv6 implementation for Linux
Bug closed, send any further explanations to Masahito Omote <[EMAIL PROTECTED]>
> thanks
Stopping processing here.
Please contact me if you need assistance.
Deb
Package: wnpp
Severity: normal
I'm orphaning junkbuster since it hasn't been maintained adequately by
its maintainer in the last few months. If you want to be the new
maintainer, please take it -- retitle this bug from 'O:' to 'ITA:',
fix the outstanding bugs and upload a new version with your na
Package: wnpp
Version: N/A; reported 2002-03-30
Severity: wishlist
* Package name: privoxy
Version : 2.9.13-beta
Upstream Author : [EMAIL PROTECTED]
* URL : http://www.privoxy.org/
* License : GPL
Description : Privacy enhancing HTTP Proxy
Privoxy is an
Your message dated Sat, 30 Mar 2002 16:47:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134842: fixed in logtrend-ftpagent 0.81-4
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
Your message dated Sat, 30 Mar 2002 17:02:29 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134844: fixed in logtrend-doc 0.81-3
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 no
Your message dated Sat, 30 Mar 2002 17:02:36 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134846: fixed in logtrend-httpagent 0.81-4
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
Your message dated Sat, 30 Mar 2002 17:02:57 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134848: fixed in logtrend-snmpagent 0.81-4
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
Your message dated Sat, 30 Mar 2002 17:02:43 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134847: fixed in logtrend-linuxagent 0.81-4
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 i
Your message dated Sat, 30 Mar 2002 17:03:04 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134851: fixed in logtrend-snortagent 0.81-4
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 i
Your message dated Sat, 30 Mar 2002 17:03:11 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134852: fixed in logtrend-storageserver 0.81-4
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 cas
Your message dated Sat, 30 Mar 2002 17:32:14 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#120691: fixed in crystalspace 0.93.20020318-5
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
Package: wnpp
Severity: normal
kdebase-crypto is orphaned, but it seems nobody filed a bug about it
in WNPP. If you want to be the new maintainer, please take it --
retitle this bug from 'O:' to 'ITA:', fix the outstanding bugs and
upload a new version with your name in the Maintainer: field and
Package: wnpp
Severity: normal
kdelibs-crypto is orphaned, but it seems nobody filed a bug about it in WNPP.
If you want to be the new maintainer, please take it -- retitle
this bug from 'O:' to 'ITA:', fix the outstanding bugs and upload a new
version with your name in the Maintainer: field and a
Processing commands for [EMAIL PROTECTED]:
> close 134845
Bug#134845: ITA: logtrend-ftpagent -- Perl daemon for ftpd monitoring
Bug closed, send any further explanations to [EMAIL PROTECTED]
> close 135850
Bug number 135850 not found.
> close 134853
Bug#134853: ITA: logtrend-visuapache -- logtre
Your message dated Sun, 31 Mar 2002 09:15:50 +1000
with message-id <[EMAIL PROTECTED]>
and subject line fixed in new maintainer upload
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 res
Your message dated Sun, 31 Mar 2002 09:15:01 +1000
with message-id <[EMAIL PROTECTED]>
and subject line fixed in new maintainer upload
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 res
Processing commands for [EMAIL PROTECTED]:
> retitle 130267 ITA
Bug#130267: RFA: aspell-pt -- Portuguese dictionary for aspell
Changed Bug title.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian
Processing commands for [EMAIL PROTECTED]:
> retitle 130267 ITA: aspell-pt -- Portuguese dictionary for aspell
Bug#130267: ITA
Changed Bug title.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debia
41 matches
Mail list logo
