Re: Processed: Follow-up

To: <owner@bugs.debian.org>
Cc: <wrar@debian.org>, <debian-efi@lists.debian.org>
Subject: Re: Processed: Follow-up
From: <Mario.Limonciello@dell.com>
Date: Mon, 3 Feb 2020 13:30:22 +0000
Message-id: <[🔎] 18b14161-f417-4e44-997f-c359de479097@email.android.com>
In-reply-to: <[🔎] handler.s.B950408.158073541516984.transcript@bugs.debian.org>
References: <[🔎] 20200203122503.GD3484@belkar.wrar.name> <[🔎] 158054697629.7787.17272058597667960344.reportbug@belkar.wrar.name>,<[🔎] handler.s.B950408.158073541516984.transcript@bugs.debian.org>

1.3.7-2 should fix this, but I think I mixed up fixes/closed syntax between GitHub and Debian for the changelog so you weren't notified and it wasn't autoclosed.

On Feb 3, 2020 07:12, Debian Bug Tracking System <owner@bugs.debian.org> wrote:

[EXTERNAL EMAIL]

Processing control commands:

> severity -1 critical
Bug #950408 [fwupd] Bad ExecStart in fwupd-refresh.service
Severity set to 'critical' from 'important'

--
950408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950408
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Reply to:

References:
- Bug#950408: Follow-up
  - From: Andrey Rahmatullin <wrar@debian.org>
- Bug#950408: Bad ExecStart in fwupd-refresh.service
  - From: Andrey Rahmatullin <wrar@debian.org>
- Processed: Follow-up
  - From: "Debian Bug Tracking System" <owner@bugs.debian.org>

Prev by Date: Processed: Follow-up
Next by Date: Processed: your mail
Previous by thread: Processed: Follow-up
Next by thread: Processing of fwupd_1.3.7-2_source.changes
Index(es):
- Date
- Thread