On Thu, Jul 30, 2015 at 04:06:51PM +0200, Simon Richter wrote:
> Hi,
>
> On 30.07.2015 05:12, Nikolaus Rath wrote:
>
> > I'm looking at the bug overview page for src:python3-llfuse
> > (https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-llfuse). The
> > first thing it lists is the apparentl
On Jul 29 2015, Russ Allbery wrote:
> Nikolaus Rath writes:
>
>> I'm looking at the bug overview page for src:python3-llfuse
>> (https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-llfuse). The
>> first thing it lists is the apparently nasty grave bug #775056.
>
>> However, this bug only exi
* Steve Langasek , 2015-07-29, 20:48:
Normally, such a bug is closed with 'close' rather than 'fixed'; the
difference between these two commands being *whether* to continue
showing the bug as a going concern.
Normally, you should close a bug by sending a message to
nn-d...@bugs.debian.org
Hi Nikolaus,
On Wed, Jul 29, 2015 at 08:12:57PM -0700, Nikolaus Rath wrote:
> I'm at a loss how to best use debbugs, I hope someone can offer some
> advice / best practices.
> I'm looking at the bug overview page for src:python3-llfuse
> (https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-l
Nikolaus Rath writes:
> I'm looking at the bug overview page for src:python3-llfuse
> (https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-llfuse). The
> first thing it lists is the apparently nasty grave bug #775056.
> However, this bug only exists in wheezy, it's fixed in both jessie and
Hello,
I'm at a loss how to best use debbugs, I hope someone can offer some
advice / best practices.
I'm looking at the bug overview page for src:python3-llfuse
(https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python-llfuse). The
first thing it lists is the apparently nasty grave bug #775056.
6 matches
Mail list logo