On Wednesday, January 18, 2006 1:55 PM, Henrique de Moraes Holschuh
<[EMAIL PROTECTED]> wrote:
> On Wed, 18 Jan 2006, Steve Langasek wrote:
[...]
>> need close or -done (and yes, katie would implement this using
>> -done, just as it already does for maintainer uploads to unstable).
>
> If the BTS w
On Wed, 18 Jan 2006, Henrique de Moraes Holschuh wrote:
> On Wed, 18 Jan 2006, Thijs Kinkhorst wrote:
> > There's currently no other way to specify a fixed-version other than
> > mailing '-done' or using 'close. Mailing -done is not always
>
> Refer to the "found" and "notfound" commands in the BT
On Wed, 18 Jan 2006, Steve Langasek wrote:
> > AFAIK, [EMAIL PROTECTED] should be used for unstable uploads (it already
> > is, I
> > think), and notfound commands to [EMAIL PROTECTED] should be used instead of
> > fixed-in-experimental tags.
>
> Wrong. notfound commands don't do anything that's
On Wed, 18 Jan 2006, Thijs Kinkhorst wrote:
> There's currently no other way to specify a fixed-version other than
> mailing '-done' or using 'close. Mailing -done is not always
Refer to the "found" and "notfound" commands in the BTS reference.
"notfound" seems to do what you want, to me. Or mayb
On Wed, 18 Jan 2006, Frank Küster wrote:
> Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
> > No, as close commands ARE clearly deprecated as well, and not at all
> > equivalent to adding a tag. We are taliking about uploads to experimental,
> > after all.
> >
> > AFAIK, [EMAIL PROTECTED]
Thomas Viehmann wrote:
> Note that about everyone suggested to include Version: information which
> you didn't use (at least for #332783).
> But then, there must always be room for improvement.
:)
Yes, I know. That's what I learned today :)
Will do it next time.
Bye
Armin
--
To UNSUBSCRIBE, em
Armin Berres wrote:
> Thijs Kinkhorst wrote:
>>So, the correct way to handle this is to mail to
>>[EMAIL PROTECTED] with on the first line of your message
>>"Version: ". You should close bugs like this for any you
>>fix, regardless of in which distribution the fix will end up.
> OK, that's what I
On Wed, 2006-01-18 at 10:00 -0200, Henrique de Moraes Holschuh wrote:
> > You mean "close" commands...
>
> No, as close commands ARE clearly deprecated as well, and not at all
> equivalent to adding a tag. We are taliking about uploads to experimental,
> after all.
The close command was indeed d
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
> No, as close commands ARE clearly deprecated as well, and not at all
> equivalent to adding a tag. We are taliking about uploads to experimental,
> after all.
>
> AFAIK, [EMAIL PROTECTED] should be used for unstable uploads (it already is,
Thijs Kinkhorst wrote:
> So, the correct way to handle this is to mail to
> [EMAIL PROTECTED] with on the first line of your message
> "Version: ". You should close bugs like this for any you
> fix, regardless of in which distribution the fix will end up.
OK, that's what I wanted to know.
Now I'm
On Wed, Jan 18, 2006 at 10:00:01AM -0200, Henrique de Moraes Holschuh wrote:
> On Wed, 18 Jan 2006, Steve Langasek wrote:
> > On Wed, Jan 18, 2006 at 09:29:35AM -0200, Henrique de Moraes Holschuh wrote:
> > > On Wed, 18 Jan 2006, Thijs Kinkhorst wrote:
> > > > In a more general sense, it's importan
On Wed, 18 Jan 2006, Steve Langasek wrote:
> On Wed, Jan 18, 2006 at 09:29:35AM -0200, Henrique de Moraes Holschuh wrote:
> > On Wed, 18 Jan 2006, Thijs Kinkhorst wrote:
> > > In a more general sense, it's important to note that the
> > > fixed-in-experimental tag is deprecated, and definately not
On Wed, Jan 18, 2006 at 09:29:35AM -0200, Henrique de Moraes Holschuh wrote:
> On Wed, 18 Jan 2006, Thijs Kinkhorst wrote:
> > In a more general sense, it's important to note that the
> > fixed-in-experimental tag is deprecated, and definately not necessary
> It is kinda hard to consider it deprec
On Wed, 18 Jan 2006, Thijs Kinkhorst wrote:
> In a more general sense, it's important to note that the
> fixed-in-experimental tag is deprecated, and definately not necessary
It is kinda hard to consider it deprecated while DAK still sets it instead
of doing a proper job of issuing "notfound" comm
On Wed, 2006-01-18 at 00:38 +0100, Armin Berres wrote:
> There was _never_ any version of Initng in unstable. The current version
> (uploaded today) doesn't contain the bugs anymore.
>
> > - Can you point me to a bug which is counted as "open" for unstable when
> > it's clearly clearly tagged fi
Armin Berres wrote:
> No problem. Maybe you understand now what I mean.
Thanks. I think I do better now.
I think that it might be that version tracking isn't optimal with
experimental yet.
Closing the bug with a [EMAIL PROTECTED] and a Version: pseudo-header seems
to be the best choice. (And indeed
Thomas Viehmann wrote:
> Hi.
>
> Armin Berres wrote:
>
>>Maybe I don't understand you or you don't understand me.
>
> Yes, but please be assured that I'm genuinely trying to understand.
I will try ;)
>>There is no Initng version in unstable! The benefit I see from closing
>>the bug completely
Hi.
Armin Berres wrote:
> Maybe I don't understand you or you don't understand me.
Yes, but please be assured that I'm genuinely trying to understand.
> There is no Initng version in unstable! The benefit I see from closing
> the bug completely is that it will vanish from the statistic. In the
>
Thomas Viehmann wrote:
> Armin Berres wrote:
>
>>>Well, what was the argument agains closing it with appropriate version
>>>information, possibly taging the unstable version as not containing the
>>>bug? (I'd really like to know what is wrong with this course of action.)
>
>
>>The point is: ther
Armin Berres wrote:
>>Well, what was the argument agains closing it with appropriate version
>>information, possibly taging the unstable version as not containing the
>>bug? (I'd really like to know what is wrong with this course of action.)
> The point is: there is no Initng version in unstable a
Thomas Viehmann wrote:
> Hi,
>
> Armin Berres wrote:
>
>>I'm the maintainer of the Initng package. This package has never been in
>>unstable yet and with the last upload I fixed some bugs.
>>Now I have one question: Is it ok if I close the bug or must I tag it as
>>fixed-in-experimental - which mak
Hi,
Armin Berres wrote:
> I'm the maintainer of the Initng package. This package has never been in
> unstable yet and with the last upload I fixed some bugs.
> Now I have one question: Is it ok if I close the bug or must I tag it as
> fixed-in-experimental - which makes no sense IMHO because we ha
Hi all!
I'm the maintainer of the Initng package. This package has never been in
unstable yet and with the last upload I fixed some bugs.
Now I have one question: Is it ok if I close the bug or must I tag it as
fixed-in-experimental - which makes no sense IMHO because we have no
version in unstabl
23 matches
Mail list logo
