Devuan logs - #19, boring messages

Message sent to [email protected], Jaromil <[email protected]>:

Subject: bug#19: devuan-project:  Backports priority is not set correctly 
Reply-To: [email protected], [email protected]
Resent-From: [email protected]
Resent-To: [email protected]
Resent-CC: Jaromil <[email protected]>
Resent-Date: Fri, 24 Mar 2017 16:33:02 UTC
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
From: [email protected]
To: [email protected]

Package: devuan-project
Severity:  critical

Backports priority is not set correctly

Message sent:

X-Loop: [email protected]
From: [email protected] (Devuan bug Tracking System)
To: [email protected]
Subject: bug#19: Acknowledgement (devuan-project:  Backports priority is not set correctly )
Message-ID: <[email protected]>
In-Reply-To: 
References: 
Precedence: bulk
X-Devuan-PR-Message: ack 19
X-Devuan-PR-Package: devuan-project
X-Devuan-PR-Keywords: 
Reply-To: [email protected]

Thank you for the problem report you have sent regarding Devuan.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the developers mailing list for
their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Jaromil <[email protected]>

If you wish to submit further information on your problem, please send
it to [email protected] (and *not* to
[email protected]).

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Devuan Bugs Owner
(administrator, Devuan bugs database)

Message sent:

X-Loop: [email protected]
From: [email protected] (Devuan bug Tracking System)
To: KatolaZ <[email protected]>
Cc: Jaromil <[email protected]>
Subject: bug#19: marked as done (devuan-project:  Backports priority is not set correctly )
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]> 
Precedence: bulk
X-Devuan-PR-Message: closed 19
X-Devuan-PR-Package: devuan-project
X-Devuan-PR-Keywords: 

Your message dated Fri, 12 May 2017 19:31:44 +0100
with message-id <[email protected]>
and subject line Fixed
has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Devuan Bugs Owner
(administrator, Devuan bugs database)

--------------------------------------
Received: (at submit) by bugs.devuan.org; 24 Mar 2017 16:32:55 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from mail.dyne.org [178.62.188.7]
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Fri, 24 Mar 2017 17:32:55 +0100 (CET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	(Authenticated sender: [email protected])
	with ESMTPSA id 6143118BDAA
From: [email protected]
To: [email protected]
Subject: devuan-project:  Backports priority is not set correctly 
X-Spam-Status: No, score=0.5 required=5.0 tests=ALL_TRUSTED,
	HEADER_FROM_DIFFERENT_DOMAINS,MISSING_DATE,MISSING_MID autolearn=disabled
	version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tupac2

Package: devuan-project
Severity:  critical

Backports priority is not set correctly


---------------------------------------
Received: (at 19-close) by bugs.devuan.org; 12 May 2017 18:40:05 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from mail.dyne.org [178.62.188.7]
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Fri, 12 May 2017 20:40:05 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	(Authenticated sender: [email protected])
	with ESMTPSA id A343E18D85D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=freaknet.org; s=mail;
	t=1494613905; bh=uqFcRimSgRBBb2WFs2HJqb5tTUHcwmwUB1BzIgl0Of8=;
	h=Date:From:To:Subject:From;
	b=CnFUx9lmrRANy5VuoRwczn4XnZ2FgPkfgqsUAyrp0EBfKND0lGT4NhKbAmm2acb/L
	 h7VhnCEZOJy7srL+RENdD9fZQLKjhiOGGTUmII7o7MNPQg9Myoliu3bHgdKmbEuJ10
	 ojzKmtxeifhCDbK8LQwMEzpTKhrAGwIhfrBo7JZo=
Date: Fri, 12 May 2017 19:31:44 +0100
From: KatolaZ <[email protected]>
To: [email protected]
Subject: Fixed
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED
	autolearn=disabled version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tupac2

This has been fixed by a patch to amprolla. Kudos to Centurion Dan

Message sent:

X-Loop: [email protected]
From: [email protected] (Devuan bug Tracking System)
To: [email protected]
Subject: bug#19 acknowledged by developer
         (Fixed)
Message-ID: <[email protected]>
In-Reply-To: 
References: <[email protected]> 
X-Devuan-PR-Message: they-closed 19
X-Devuan-PR-Package: devuan-project
X-Devuan-PR-Keywords: 
Reply-To: [email protected]

This is an automatic notification regarding your bug report
#19: devuan-project:  Backports priority is not set correctly ,
which was filed against the devuan-project package.

It has been closed by one of the developers, namely
KatolaZ <[email protected]>.

Their explanation is attached below.  If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact the developer, by replying to this email.

Devuan Bugs Owner
(administrator, Devuan bugs database)

Received: (at 19-close) by bugs.devuan.org; 12 May 2017 18:40:05 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from mail.dyne.org [178.62.188.7]
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Fri, 12 May 2017 20:40:05 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	(Authenticated sender: [email protected])
	with ESMTPSA id A343E18D85D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=freaknet.org; s=mail;
	t=1494613905; bh=uqFcRimSgRBBb2WFs2HJqb5tTUHcwmwUB1BzIgl0Of8=;
	h=Date:From:To:Subject:From;
	b=CnFUx9lmrRANy5VuoRwczn4XnZ2FgPkfgqsUAyrp0EBfKND0lGT4NhKbAmm2acb/L
	 h7VhnCEZOJy7srL+RENdD9fZQLKjhiOGGTUmII7o7MNPQg9Myoliu3bHgdKmbEuJ10
	 ojzKmtxeifhCDbK8LQwMEzpTKhrAGwIhfrBo7JZo=
Date: Fri, 12 May 2017 19:31:44 +0100
From: KatolaZ <[email protected]>
To: [email protected]
Subject: Fixed
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED
	autolearn=disabled version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tupac2

This has been fixed by a patch to amprolla. Kudos to Centurion Dan