On Wed, 25 Aug 2021, Vincent Lefevre wrote:
> Yes, but only the notification (and one needs to see the full message).
> But what if the close message is sent when an empty From or with
> a From containing the -cl...@bugs.debian.org address
> of the bug[*] (such messages could come from
On 2021-08-23 07:43:07 +0100, Tim Woodall wrote:
> On Mon, 23 Aug 2021, Holger Wansing wrote:
> > Am 23. August 2021 07:19:26 MESZ schrieb Tomas Pospisek
> > :
> > >
> > > The thing is, if you close a bug report via `Bcc:
> > > -cl...@bugs.debian.org` then the mail that arrives at the
On Mon, Aug 23, 2021 at 02:21:04AM +0200, Vincent Lefevre wrote:
> On 2021-08-22 23:32:15 +0500, Andrey Rahmatullin wrote:
> > On Sun, Aug 22, 2021 at 08:25:41PM +0200, Tomas Pospisek wrote:
> > > Wouldn't the Bcc'ed email that arrived to the BTS be visible in the bug's
> > > log/archive (on the bu
On Mon, 23 Aug 2021, Holger Wansing wrote:
Am 23. August 2021 07:19:26 MESZ schrieb Tomas Pospisek :
The thing is, if you close a bug report via `Bcc:
-cl...@bugs.debian.org` then the mail that arrives at the
BTS does *not* have the -cl...@bugs.debian.org address in
t
Am 23. August 2021 07:19:26 MESZ schrieb Tomas Pospisek :
>
>The thing is, if you close a bug report via `Bcc:
>-cl...@bugs.debian.org` then the mail that arrives at the
>BTS does *not* have the -cl...@bugs.debian.org address in
>the email header but only in the mail e
On 23.08.21 07:24, Tomas Pospisek wrote:
On 23.08.21 02:35, Vincent Lefevre wrote:
On 2021-08-21 10:36:04 +0200, Tomas Pospisek wrote:
In particular it *seems* to work for him and he doesn't have access
to your
system where things apparently went wrong so it could be really hard
for him
to kno
On 23.08.21 02:35, Vincent Lefevre wrote:
On 2021-08-21 10:36:04 +0200, Tomas Pospisek wrote:
In particular it *seems* to work for him and he doesn't have access to your
system where things apparently went wrong so it could be really hard for him
to know. So what you can do is to try to debug *y
On 23.08.21 02:21, Vincent Lefevre wrote:
On 2021-08-22 23:32:15 +0500, Andrey Rahmatullin wrote:
On Sun, Aug 22, 2021 at 08:25:41PM +0200, Tomas Pospisek wrote:
Wouldn't the Bcc'ed email that arrived to the BTS be visible in the bug's
log/archive (on the bug's page (https://bugs.debian.org/989
On 2021-08-21 10:36:04 +0200, Tomas Pospisek wrote:
> In particular it *seems* to work for him and he doesn't have access to your
> system where things apparently went wrong so it could be really hard for him
> to know. So what you can do is to try to debug *yourself* why the upgrade
> went wrong a
On 2021-08-22 23:32:15 +0500, Andrey Rahmatullin wrote:
> On Sun, Aug 22, 2021 at 08:25:41PM +0200, Tomas Pospisek wrote:
> > Wouldn't the Bcc'ed email that arrived to the BTS be visible in the bug's
> > log/archive (on the bug's page (https://bugs.debian.org/989734))?
> It's visible: https://bugs.
On Sun, Aug 22, 2021 at 08:25:41PM +0200, Tomas Pospisek wrote:
> Wouldn't the Bcc'ed email that arrived to the BTS be visible in the bug's
> log/archive (on the bug's page (https://bugs.debian.org/989734))?
It's visible: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989734;msg=27
--
WBR, wRA
Hi Mattia,
On 21.08.21 12:06, Mattia Rizzolo wrote:
On Sat, Aug 21, 2021 at 10:36:04AM +0200, Tomas Pospisek wrote:
Hi Vincent,
On 20.08.21 16:50, Vincent Lefevre wrote:
My bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989734
has been closed again, with no explanations.
https
On Sat, Aug 21, 2021 at 10:36:04AM +0200, Tomas Pospisek wrote:
> Hi Vincent,
>
> On 20.08.21 16:50, Vincent Lefevre wrote:
> > My bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989734
> > has been closed again, with no explanations.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi
Hi Vincent,
On 20.08.21 16:50, Vincent Lefevre wrote:
My bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989734
has been closed again, with no explanations.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989734;msg=12 claims
that the bug was closed via
https://bugs.debian.org
14 matches
Mail list logo
