Dear gregor (and others off-list),
On Fri, Apr 29, 2016 at 12:17:36PM +0200, gregor herrmann wrote:
> The BTS is version-aware and knows/displays that the bug still
> affects the version in stable.
I am aware that the BTS is version-aware, but where I have got confused is I
was assuming that mail
On Fri, 29 Apr 2016 10:15:13 +0100, Jonathan Dowland wrote:
> I think perhaps closing all open bugs when a sid package is removed is the
> wrong thing to do. I'm not sure what could be done instead, though.
> Thoughts?
The BTS is version-aware and knows/displays that the bug still
affects the ver
Junichi Uekawa <[EMAIL PROTECTED]> wrote:
> Hi,
>
>> > > AFAIK apt-listbugs only displays open bugs, if the bug is closed
>> > > then it won't get displayed.
>> >
>> > It will be displayed even when it's closed. It does have some
>> > heuristics to avoid showing irrelevant bugs.
>> >
>> >
>>
Hi,
> > > AFAIK apt-listbugs only displays open bugs, if the bug is closed
> > > then it won't get displayed.
> >
> > It will be displayed even when it's closed. It does have some
> > heuristics to avoid showing irrelevant bugs.
> >
> >
> > > Ideally apt-listbugs needs to be updated to suppor
On Sat, Nov 12, 2005 at 09:43:26AM +0900, Junichi Uekawa
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> > >> Today I did a update of the system (yes, sid and yes I know
> > >> it can be unstable but...) and the update includes grep where
> > >> no open critical bug was seen. After Boot the syste
Hi,
> >> Today I did a update of the system (yes, sid and yes I know it
> >> can be unstable but...) and the update includes grep where no
> >> open critical bug was seen. After Boot the system was
> >> completely broken as of the libpcre dependency.
> >>
> >> So please do
> "Junichi" == Junichi Uekawa <[EMAIL PROTECTED]> writes:
Junichi> Hi,
>> Today I did a update of the system (yes, sid and yes I know it
>> can be unstable but...) and the update includes grep where no
>> open critical bug was seen. After Boot the system was
>> completely b
Klaus Ethgen <[EMAIL PROTECTED]> wrote:
> Today I did a update of the system (yes, sid and yes I know it can be
> unstable but...) and the update includes grep where no open critical bug
> was seen. After Boot the system was completely broken as of the libpcre
> dependency.
> So please do not clos
Hi,
> Today I did a update of the system (yes, sid and yes I know it can be
> unstable but...) and the update includes grep where no open critical bug
> was seen. After Boot the system was completely broken as of the libpcre
> dependency.
>
> So please do not close bugs bevore it is available on
Klaus Ethgen <[EMAIL PROTECTED]> writes:
> Today I did a update of the system (yes, sid and yes I know it can be
> unstable but...) and the update includes grep where no open critical bug
> was seen. After Boot the system was completely broken as of the libpcre
> dependency.
>
> So please do not c
On Mon, Oct 17, 2005 at 03:16:01AM +0200, Henning Makholm wrote:
> If I understand correctly, after version tracking was implemented, the
> fixed-in-experimental tag has been superseded by simply closing the
> bug for the current experimental version (i.e. mailing [EMAIL PROTECTED]
> with a pseudo-
Scripsit "Jan C. Nordholz" <[EMAIL PROTECTED]>
> Now I'd like to save the maintainer some work and tag the bug
> fixed-in-experimental myself (together with a short explanatory
> message to the bug log),
If I understand correctly, after version tracking was implemented, the
fixed-in-experimental
On Mon, Oct 17, 2005 at 02:17:01AM +0200, Jeroen van Wolffelaar wrote:
> Yes, you may do so -- if in doubt, simply write an explanatory mail to
> [EMAIL PROTECTED], and let the maintainer deal with it. If you're sure
> that what you're doing is correct, there is in general no reason to not do it.
>
"Jan C. Nordholz" <[EMAIL PROTECTED]> writes:
> I'd like to ask you if it is desired (and possible at all)
> that submitters close their own bugs if they have been fixed
> without the package maintainer's noticing. The informational
> pages on b.d.o don't state whether [EMAIL PROTECTED] is obeying
This one time, at band camp, Jan C. Nordholz said:
> Dear list,
>
> I'd like to ask you if it is desired (and possible at all)
> that submitters close their own bugs if they have been fixed
> without the package maintainer's noticing. The informational
> pages on b.d.o don't state whether [EMAIL P
On Mon, Oct 17, 2005 at 02:09:06AM +0200, Jan C. Nordholz wrote:
> Dear list,
>
> I'd like to ask you if it is desired (and possible at all)
> that submitters close their own bugs if they have been fixed
> without the package maintainer's noticing. The informational
> pages on b.d.o don't state wh
On Thu, Aug 25, 2005 at 12:25:08AM +0200, martin f krafft wrote:
> > Moreover I wonder if when closing via mail should I write in
> > Changelog sth like: this upload fixes bug number 1234567 in
> > testing and unstable which has been closed via mail, and add tag
> > sarge to bug that remain opened
* Steinar H. Gunderson [Thu, 25 Aug 2005 01:03:03 +0200]:
> BTW, does the BTS understand that the package might "fork"? Specifically, if
> I have a bug in a sarge package (say, 1.0) that is fixed in an upstream
> version 1.2, but is backported to sarge (because it's an RC bug), can I say
> that it
On Thu, Aug 25, 2005 at 12:49:19AM +0200, martin f krafft wrote:
>> AFAICT there is no support for a "done" command to [EMAIL PROTECTED]
>
> I meant "close":
>
> close 99 1.2
BTW, does the BTS understand that the package might "fork"? Specifically, if
I have a bug in a sarge package (say,
In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
>In recent announce about changes in BTS (Subject: BTS version tracking
>Date: Mon, 18 Jul 2005 12:06:29 +0100) is described how to use new
>versioning system. I'm not sure if sending mail to [EMAIL PROTECTED] is
>now prefered way to closing
also sprach Frans Pop <[EMAIL PROTECTED]> [2005.08.25.0038 +0200]:
> > done 99 1.2
>
> AFAICT there is no support for a "done" command to [EMAIL PROTECTED]
I meant "close":
close 99 1.2
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft
Thu, 25 Aug 2005 00:25:08 +0200
martin f krafft <[EMAIL PROTECTED]> wrote:
> > In recent announce about changes in BTS (Subject: BTS version
> > tracking Date: Mon, 18 Jul 2005 12:06:29 +0100) is described how to
> > use new versioning system. I'm not sure if sending mail to
> > [EMAIL PROTECTED]
On Thursday 25 August 2005 00:25, martin f krafft wrote:
> done 99 1.2
AFAICT there is no support for a "done" command to [EMAIL PROTECTED]
pgps430gVp78z.pgp
Description: PGP signature
Em Qua, 2005-08-24 às 23:59 +0200, Grzegorz Bizon escreveu:
> In recent announce about changes in BTS (Subject: BTS version tracking
> Date: Mon, 18 Jul 2005 12:06:29 +0100) is described how to use new
> versioning system. I'm not sure if sending mail to [EMAIL PROTECTED] is
> now prefered way to c
also sprach Grzegorz Bizon <[EMAIL PROTECTED]> [2005.08.24.2359 +0200]:
> Maintainer uploads fixed package into unstable and closes bug in
> Changelog, after few days corrected package enters testing, depending on
> urgency. Granted that reported bug wasn't so important to justify
> upload do stab
> Now that sarge is out (BTW, congrats to everybody!), can I close bug
> reports tagged "woody" ?
I think that you should close those reports if and only if corresponding
bugs are fixed in sarge.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [
Le Tue, 07 Jun 2005 19:51:03 +0200, Frank Lichtenheld a écrit :
> On Tue, Jun 07, 2005 at 05:14:12PM +0200, Rafael Laboissiere wrote:
>> Now that sarge is out (BTW, congrats to everybody!), can I close bug
>> reports tagged "woody" ?
>
> Depends. Certainly not security related bugs. For others it
On Tue, Jun 07, 2005 at 05:14:12PM +0200, Rafael Laboissiere wrote:
> Now that sarge is out (BTW, congrats to everybody!), can I close bug
> reports tagged "woody" ?
Depends. Certainly not security related bugs. For others it might
be usefull to keep them around to perhaps prevent others from repo
On 14 Oct 1998, Ole J. Tetlie wrote:
> Quick question: When two bugs are merged, do I need to close both
> or will one closing close both, and send a message to both the
> submittors?
The documentation for the bug system says:
[...] When reports are merged
opening, closing, marking or unmark
Ole J. Tetlie wrote:
> Quick question: When two bugs are merged, do I need to close both
> or will one closing close both, and send a message to both the
> submittors?
You need to close both, imho.
Regards,
Joey
--
Unix is user friendly ... It's just picky about it's friends.
30 matches
Mail list logo
