On Sb, 19 mai 12, 15:48:46, Manuel A. Fernandez Montecelo wrote:
>
> I don't know much about querybts, but you can ask for all [unarchived,
> I think] bugs in package emacs21, for example:
For that you would have to know the "package" the bug was reported
against.
> Hopefully somebody more kno
2012/5/19 Andrei POPESCU :
> On Vi, 18 mai 12, 14:34:40, Manuel A. Fernandez Montecelo wrote:
>>
>> So I wouldn't blindly close those bug reports, and that's why I'm
>> triaging and handling them in my spare time.
>
> Do you know how to retrieve those bugs with querybts(1) other than by
> individua
On Sat, 19 May 2012, Goswin von Brederlow wrote:
> The BTS could then not just track the binary/source package of a bug
> but also the meta-source package. That way when gcc-4.4 is removed
> from the archive the bugs can still be associated with the gcc-x.y
> meta package and won't be completly los
On Vi, 18 mai 12, 14:34:40, Manuel A. Fernandez Montecelo wrote:
>
> So I wouldn't blindly close those bug reports, and that's why I'm
> triaging and handling them in my spare time.
Do you know how to retrieve those bugs with querybts(1) other than by
individual bug number?
Kind regards,
Andrei
Neil Williams writes:
> On Fri, 18 May 2012 14:34:40 +0100
> "Manuel A. Fernandez Montecelo" wrote:
>
>> Hi,
>>
>> 2012/5/18 Daniel Leidert :
>> > Hi,
>> >
>> > Our bug tracker contains items for packages, which do (not longer) exist.
>> > What should happen to them? I see, that it might be a
Hi!
On 18.05.2012 10:50, Paul Wise wrote:
Our bug tracker contains items for packages, which do (not longer) exist. What
should happen to them? I see, that it might be a good idea to keep them for the
case, a package is re-introduced. But this might happen only for a few
packages. Most of th
On Fri, 18 May 2012 16:41:55 +0100
"Manuel A. Fernandez Montecelo" wrote:
> Another question, perhaps unrelated is, what happens with the bugs
> closed from egroupware or salome (removed from unstable/testing but
> still present in stable releases) when their users look for them in
> the BTS? Th
2012/5/18 Thomas Preud'homme :
> According to [1] salome is not part of any debian release now. Did I miss
> something? IIRW, for package still in stable, if the -done mail contains the
> right version then the bug will still be visible as long as it affects stable.
Oh yes, egroupware only in olds
Le vendredi 18 mai 2012 17:41:55, Manuel A. Fernandez Montecelo a écrit :
> 2012/5/18 Neil Williams :
> > There's a big difference between these bugs and the rest - here there
> > are clear migration paths to later packages which can be used to triage
> > the bug reports in order not to lose report
2012/5/18 Neil Williams :
> There's a big difference between these bugs and the rest - here there
> are clear migration paths to later packages which can be used to triage
> the bug reports in order not to lose reports. A lot of the rest *can*
> be closed without more triage work because the packag
On Fri, 18 May 2012 14:34:40 +0100
"Manuel A. Fernandez Montecelo" wrote:
> Hi,
>
> 2012/5/18 Daniel Leidert :
> > Hi,
> >
> > Our bug tracker contains items for packages, which do (not longer) exist.
> > What should happen to them? I see, that it might be a good idea to keep
> > them for the
Hi,
2012/5/18 Daniel Leidert :
> Hi,
>
> Our bug tracker contains items for packages, which do (not longer) exist.
> What should happen to them? I see, that it might be a good idea to keep them
> for the case, a package is re-introduced. But this might happen only for a
> few packages. Most of
"Daniel Leidert" writes:
> Hi,
>
> Our bug tracker contains items for packages, which do (not longer) exist.
> What should happen to them? I see, that it might be a good idea to keep them
> for the case, a package is re-introduced. But this might happen only for a
> few packages. Most of them
"Daniel Leidert" writes:
> Hi,
>
> Our bug tracker contains items for packages, which do (not longer)
> exist. What should happen to them? I see, that it might be a good idea
> to keep them for the case, a package is re-introduced. But this might
> happen only for a few packages. Most of them got
Daniel Leidert (18/05/2012):
> Our bug tracker contains items for packages, which do (not longer)
> exist. What should happen to them? I see, that it might be a good idea
> to keep them for the case, a package is re-introduced. But this might
> happen only for a few packages. Most of them got remo
On Fri, 18 May 2012 16:50:12 +0800
Paul Wise wrote:
> On Fri, May 18, 2012 at 4:45 PM, Daniel Leidert wrote:
>
> > Our bug tracker contains items for packages, which do (not longer) exist.
> > What should happen to them? I see, that it might be a good idea to keep
> > them for the case, a pack
On Fri, May 18, 2012 at 4:45 PM, Daniel Leidert wrote:
> Our bug tracker contains items for packages, which do (not longer) exist.
> What should happen to them? I see, that it might be a good idea to keep them
> for the case, a package is re-introduced. But this might happen only for a
> few pa
17 matches
Mail list logo
