Re: ilisp debian package

2002-04-07 Thread Will Newton
On Saturday 06 Apr 2002 4:16 pm, Will Newton wrote:

I have still not had any response to this. Can anyone tell me the correct 
procedure for getting these bugs closed?

The changelog looks like this:

ilisp (5.11.1-7) unstable; urgency=low

  * well 125744 was fixed, but I put the files in the old place on
accident.
  * Fixed 140049 - bad symlinks
  * Fixed 138669 - typo in ilisp-cmu
  * Fixed 137011 - ilisp-pkg issues

 -- Craig Brozefsky [EMAIL PROTECTED]  Mon, 25 Feb 2002 12:26:21 -0500


 ilisp is being removed from woody because of a bug that is fixed but not
 closed. According to your changelog the following bugs are fixed, but are
 not closed:

 125744
 140049
 138669
 137011
 98132
 128856
 129980
 87652
 123631
 121266


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: ilisp debian package

2002-04-07 Thread Martijn van Oosterhout
On Sun, Apr 07, 2002 at 02:26:30PM +0100, Will Newton wrote:
 On Saturday 06 Apr 2002 4:16 pm, Will Newton wrote:
 
 I have still not had any response to this. Can anyone tell me the correct 
 procedure for getting these bugs closed?
 
 The changelog looks like this:
 
 ilisp (5.11.1-7) unstable; urgency=low
 
   * well 125744 was fixed, but I put the files in the old place on
 accident.
   * Fixed 140049 - bad symlinks
   * Fixed 138669 - typo in ilisp-cmu
   * Fixed 137011 - ilisp-pkg issues

Read up on the BTS docs, but the common ways are:

The phrase Closes: #140049 in the changelog

Email to [EMAIL PROTECTED]

Email to [EMAIL PROTECTED] with body: close 140049

IIRC

check the documentation for full details.

HTH,

  -- Craig Brozefsky [EMAIL PROTECTED]  Mon, 25 Feb 2002 12:26:21 -0500
 
 
  ilisp is being removed from woody because of a bug that is fixed but not
  closed. According to your changelog the following bugs are fixed, but are
  not closed:
 
  125744
  140049
  138669
  137011
  98132
  128856
  129980
  87652
  123631
  121266
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 

-- 
Martijn van Oosterhout kleptog@svana.org   http://svana.org/kleptog/
 Ignorance continues to thrive when intelligent people choose to do
 nothing.  Speaking out against censorship and ignorance is the imperative
 of all intelligent people.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: ilisp debian package

2002-04-07 Thread Josip Rodin
On Sun, Apr 07, 2002 at 02:26:30PM +0100, Will Newton wrote:
 I have still not had any response to this. Can anyone tell me the correct 
 procedure for getting these bugs closed?

Since you're not a maintainer, you shouldn't close them. However, you can
tag them fixed, by sending 'tag  fixed' commands to [EMAIL PROTECTED]

 The changelog looks like this:
 
 ilisp (5.11.1-7) unstable; urgency=low
 
   * well 125744 was fixed, but I put the files in the old place on
 accident.
   * Fixed 140049 - bad symlinks
   * Fixed 138669 - typo in ilisp-cmu
   * Fixed 137011 - ilisp-pkg issues
 
  -- Craig Brozefsky [EMAIL PROTECTED]  Mon, 25 Feb 2002 12:26:21 -0500

Craig's syntax is incorrect, it should be 'Closes: #140049' etc.

-- 
 2. That which causes joy or happiness.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: ilisp debian package

2002-04-07 Thread Josip Rodin
On Sun, Apr 07, 2002 at 11:34:13PM +1000, Martijn van Oosterhout wrote:
 Read up on the BTS docs, but the common ways are:
 
 Email to [EMAIL PROTECTED] with body: close 140049

No! Don't fucking do that!

Geez, how many times does one have to repeat that.

-- 
 2. That which causes joy or happiness.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: ilisp debian package

2002-04-07 Thread Will Newton
On Sunday 07 Apr 2002 2:44 pm, Josip Rodin wrote:

 Since you're not a maintainer, you shouldn't close them. However, you can
 tag them fixed, by sending 'tag  fixed' commands to [EMAIL PROTECTED]

OK, if Craig hasn't done it by the end of today I will do that.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: ilisp debian package

2002-04-07 Thread David Starner
On Sun, Apr 07, 2002 at 03:04:43PM +0100, Will Newton wrote:
 On Sunday 07 Apr 2002 2:44 pm, Josip Rodin wrote:
 
  Since you're not a maintainer, you shouldn't close them. However, you can
  tag them fixed, by sending 'tag  fixed' commands to [EMAIL PROTECTED]
 
 OK, if Craig hasn't done it by the end of today I will do that.

Why? Considering how close to the release we are, and how easy it is,
why not do it now? It certainly won't interfer with the maintainer
closing them.

-- 
David Starner - [EMAIL PROTECTED]
It's not a habit; it's cool; I feel alive. 
If you don't have it you're on the other side. 
- K's Choice (probably referring to the Internet)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: ilisp debian package

2002-04-07 Thread Will Newton
On Sunday 07 Apr 2002 3:20 pm, David Starner wrote:

 Why? Considering how close to the release we are, and how easy it is,
 why not do it now? It certainly won't interfer with the maintainer
 closing them.

OK, done. I just don't want to step on anyone's toes.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: ilisp debian package

2002-04-07 Thread Craig Brozefsky
Will Newton [EMAIL PROTECTED] writes:

 On Sunday 07 Apr 2002 3:20 pm, David Starner wrote:
 
  Why? Considering how close to the release we are, and how easy it is,
  why not do it now? It certainly won't interfer with the maintainer
  closing them.
 
 OK, done. I just don't want to step on anyone's toes.

My sincerest apologies for the delay.  I have had hard time keeping up
with devel and devel-announce for reasons of my own stupidty in
configuring gnus and since I had done the [EMAIL PROTECTED] with the body
containing closes BUGID in it, which apparently is not supported
anymore (I was going from docs) I assumed the bugs were all closed
out properly.

-- 
Craig Brozefsky   [EMAIL PROTECTED]
Free Software Sociopath(tm) http://www.red-bean.com/~craig
Ask me about Common Lisp Enterprise Eggplants at Red Bean!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]