Re: Processed: closing 921272

To: Dominik George <nik@naturalnet.de>, debian-tex-maint@lists.debian.org
Subject: Re: Processed: closing 921272
From: Norbert Preining <norbert@preining.info>
Date: Wed, 27 Feb 2019 19:50:34 +0900
Message-id: <[🔎] 20190227105034.GB30019@bulldog.preining.info>
In-reply-to: <[🔎] handler.s.C.15512600899296.transcript@bugs.debian.org>
References: <20190227093445.31D9618C2FD2@shore.naturalnet.de> <[🔎] handler.s.C.15512600899296.transcript@bugs.debian.org>

Hi Dominik,

On Wed, 27 Feb 2019, Debian Bug Tracking System wrote:
> > close 921272 2018.20190131-2

That might be, but it is NOT FIXED in 2018.20190207-1 that has been
included suddenly yesterday.

What is the reason that you closed this bug?
Could you please trust my judgement when I re-opened this bug?

You should have used "not-found" or similar, because the bug *IS*
present in the above version.

Can you please revert this mess.

Thanks

Norbert

--
PREINING Norbert                               http://www.preining.info
Accelia Inc.     +    JAIST     +    TeX Live     +    Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Reply to:

Follow-Ups:
- Re: Processed: closing 921272
  - From: Dominik George <natureshadow@debian.org>

References:
- Processed: closing 921272
  - From: "Debian Bug Tracking System" <owner@bugs.debian.org>

Prev by Date: Re: Processed: closing 921272
Next by Date: Processed: reopening 920459, found 920459 in 2018.20190131-1, fixed 920459 in 2018.20190131-2 ...
Previous by thread: Processed: closing 921272
Next by thread: Re: Processed: closing 921272
Index(es):
- Date
- Thread