Re: Bug reports missing

2003-12-14 Thread Branden Robinson
On Sun, Dec 14, 2003 at 11:52:15PM +1100, Hamish Moffatt wrote: > On Fri, Dec 12, 2003 at 11:22:48AM -0500, Branden Robinson wrote: > > On Wed, Dec 10, 2003 at 11:20:30PM +1100, Hamish Moffatt wrote: > > > It's your punishment for using the close command. DON'T! > > > There is no need and no excuse

Re: Bug reports missing

2003-12-14 Thread Hamish Moffatt
On Fri, Dec 12, 2003 at 11:22:48AM -0500, Branden Robinson wrote: > On Wed, Dec 10, 2003 at 11:20:30PM +1100, Hamish Moffatt wrote: > > On Wed, Dec 10, 2003 at 08:30:49AM +0100, Andreas Tille wrote: > > > mailx -s "Merge" [EMAIL PROTECTED] <<... > > > merge 219863 223355 > > > close 223355 >

Re: Bug reports missing

2003-12-12 Thread Andreas Tille
On Fri, 12 Dec 2003, Branden Robinson wrote: > > It's your punishment for using the close command. DON'T! > > There is no need and no excuse. > > I disagree. See situations like #214865 or #218038. > > "close" *can* be handled responsibly. Thanks for this support. I'm generally aware that "close

Re: Bug reports missing

2003-12-12 Thread Branden Robinson
On Wed, Dec 10, 2003 at 11:20:30PM +1100, Hamish Moffatt wrote: > On Wed, Dec 10, 2003 at 08:30:49AM +0100, Andreas Tille wrote: > > mailx -s "Merge" [EMAIL PROTECTED] <<... > > merge 219863 223355 > > close 223355 > > thanks > > > > and got the answer mentioned below. > > It's your pun

Re: Bug reports missing

2003-12-10 Thread Colin Watson
On Wed, Dec 10, 2003 at 01:19:57PM +0100, Andreas Tille wrote: > On Wed, 10 Dec 2003, Anthony Towns wrote: > > What research? It certainly shows up in http://bugs.debian.org/219863 . > > Not when I tried it some hours ago. I can't reproduce this, sorry. > > Moreover I wonder why it is missing fr

Re: Bug reports missing

2003-12-10 Thread Hamish Moffatt
On Wed, Dec 10, 2003 at 08:30:49AM +0100, Andreas Tille wrote: > mailx -s "Merge" [EMAIL PROTECTED] <<... > merge 219863 223355 > close 223355 > thanks > > and got the answer mentioned below. It's your punishment for using the close command. DON'T! There is no need and no excuse. thank

Re: Bug reports missing

2003-12-10 Thread Andreas Tille
On Wed, 10 Dec 2003, Anthony Towns wrote: > What research? It certainly shows up in http://bugs.debian.org/219863 . Not when I tried it some hours ago. I can't reproduce this, sorry. Moreover I wonder why it is missing from http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=pkg&data=tipptra

Re: Bug reports missing

2003-12-10 Thread Anthony Towns
On Wed, Dec 10, 2003 at 08:30:49AM +0100, Andreas Tille wrote: > I just sendet > mailx -s "Merge" [EMAIL PROTECTED] <<... > merge 219863 223355 ] Debian Bug report logs - #219863 ] Bug is archived. No further changes may be made. > close 223355 You also can't merge an open bug and a closed

Re: Bug reports missing

2003-12-10 Thread Colin Watson
On Wed, Dec 10, 2003 at 11:22:42AM +0100, Andreas Tille wrote: > On Wed, 10 Dec 2003, Colin Watson wrote: > > On Wed, Dec 10, 2003 at 08:30:49AM +0100, Andreas Tille wrote: > > > I just sendet > > > > > > mailx -s "Merge" [EMAIL PROTECTED] <<... > > > merge 219863 223355 > > > close 223355 >

Re: Bug reports missing

2003-12-10 Thread Andreas Tille
On Wed, 10 Dec 2003, Colin Watson wrote: > On Wed, Dec 10, 2003 at 08:30:49AM +0100, Andreas Tille wrote: > > I just sendet > > > > mailx -s "Merge" [EMAIL PROTECTED] <<... > > merge 219863 223355 > > close 223355 > > thanks > > > > and got the answer mentioned below. In fact my research

Re: Bug reports missing

2003-12-10 Thread Colin Watson
On Wed, Dec 10, 2003 at 08:30:49AM +0100, Andreas Tille wrote: > I just sendet > > mailx -s "Merge" [EMAIL PROTECTED] <<... > merge 219863 223355 > close 223355 > thanks > > and got the answer mentioned below. In fact my research showed that #219863 > does not exist in the BTS. #219863

Bug reports missing

2003-12-10 Thread Andreas Tille
Hi, I just sendet mailx -s "Merge" [EMAIL PROTECTED] <<... merge 219863 223355 close 223355 thanks and got the answer mentioned below. In fact my research showed that #219863 does not exist in the BTS. If this is a known issue (probably caused by the current administration issues) forg