Devuan logs - #256, boring messages

Message sent to [email protected], [email protected]:

Subject: bug#256: [reportbug-ng] ..devuan's reportbug-ng obviously should report bugs to [email protected]
Reply-To: Arnt Karlsen <[email protected]>, [email protected]
Resent-From: Arnt Karlsen <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected]
Resent-Date: Tue, 13 Nov 2018 01:48:01 UTC
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
Date: Tue, 13 Nov 2018 02:34:15 +0100
From: Arnt Karlsen <[email protected]>
Disposition-Notification-To: Arnt Karlsen <[email protected]>
To: [email protected]
Message-ID: <20181113023415.54c42f43@d44>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Package: reportbug-ng
Version: 2.1
Severity: important

--- Please enter the report below this line. ---

..my first attempt wound up in the partially wrong place, upstream:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913364

..my second attempt wound up in the partially wrong place, upstream:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913365

..devuan's reportbug-ng obviously should report bugs to
[email protected], not [email protected].


--- System information. ---
Architecture: 
Kernel:       Linux 4.18.0-0.bpo.1-rt-amd64

Debian Release: 9
  500 stable-updates  deb.devuan.org 
  500 stable-security deb.devuan.org 
  500 stable          deb.devuan.org 
  100 stable-proposed-updates deb.devuan.org 
  100 stable-backports deb.devuan.org 
  100 experimental    deb.devuan.org 

--- Package information. ---
Depends                       (Version) | Installed
=======================================-+-==============
python:any                (>= 2.7.5-5~) | 
python-debianbts               (>= 1.0) | 2.6.1
python-pyqt5                            | 5.7+dfsg-5
python-pyqt5.qtwebkit                   | 5.7+dfsg-5
xdg-utils                               | 1.1.1-1+deb9u1
xterm                                   | 327-2
python-apt                  (>= 0.7.93) | 1.4.0~beta3


Package's Recommends field is empty.

Package's Suggests field is empty.




Hi,


-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

Message sent:

X-Loop: [email protected]
From: [email protected] (Devuan bug Tracking System)
To: Arnt Karlsen <[email protected]>
Subject: bug#256: Acknowledgement ([reportbug-ng] ..devuan's reportbug-ng obviously should report bugs to [email protected])
Message-ID: <[email protected]>
In-Reply-To: <20181113023415.54c42f43@d44>
References: <20181113023415.54c42f43@d44>
Precedence: bulk
X-Devuan-PR-Message: ack 256
X-Devuan-PR-Package: reportbug-ng
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):
 [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.

Your message specified a Severity: in the pseudo-header, but
the severity value important was not recognised.
The default severity normal is being used instead.
The recognised values are: critical, grave, normal, minor, wishlist.

Devuan Bugs Owner
(administrator, Devuan bugs database)

Message sent to [email protected], [email protected]:

Subject: bug#256: Acknowledgement ([reportbug-ng] ..devuan's reportbug-ng obviously should report bugs to [email protected])
Reply-To: Arnt Karlsen <[email protected]>, [email protected]
Resent-From: Arnt Karlsen <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected]
Resent-Date: Tue, 13 Nov 2018 07:03:02 UTC
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
Date: Tue, 13 Nov 2018 07:58:11 +0100
From: Arnt Karlsen <[email protected]>
To: [email protected]
Message-ID: <20181113075811.7bee32b7@d44>
In-Reply-To: <[email protected]>
References: <20181113023415.54c42f43@d44>
	<[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,


..no date error in bug#256: Acknowledgement mail:
On , Devuan wrote in message 
<[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):
>  [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.
> 
> Your message specified a Severity: in the pseudo-header, but
> the severity value important was not recognised.
> The default severity normal is being used instead.
> The recognised values are: critical, grave, normal, minor, wishlist.
> 
> Devuan Bugs Owner
> (administrator, Devuan bugs database)
> 

..reportbug-ng installed without errors but is never configured 
to actually use bugs.devuan.org, it uses bugs.debian.org.  

..reportbug-ng does not have the reportbug --bts option, 
and appears to be hard coded to use bugs.debian.org. 


-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

Message sent:

X-Loop: [email protected]
From: [email protected] (Devuan bug Tracking System)
To: Arnt Karlsen <[email protected]>
Subject: bug#256: Info received (was bug#256: Acknowledgement ([reportbug-ng] ..devuan's reportbug-ng obviously should report bugs to [email protected]))
Message-ID: <[email protected]>
In-Reply-To: <20181113075811.7bee32b7@d44>
References: <20181113075811.7bee32b7@d44>
Precedence: bulk
X-Devuan-PR-Message: ack-info 256
X-Devuan-PR-Package: reportbug-ng
X-Devuan-PR-Keywords: 
Disabled-Doogie-Reply-To: [email protected]

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the developer(s) and
to the developers mailing list to accompany the original report.

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

If you wish to continue to submit further information on your problem,
please send it to [email protected], as before.

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 to [email protected], [email protected]:

X-Loop: [email protected]
Subject: bug#256: Acknowledgement ([reportbug-ng] ..devuan's reportbug-ng obviously should report bugs to [email protected])
Reply-To: Mark Hindley <[email protected]>, [email protected]
Resent-From: Mark Hindley <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected]
X-Loop: [email protected]
Resent-Date: Thu, 16 Jan 2020 20:48:02 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Devuan-PR-Message: followup 256
X-Devuan-PR-Package: reportbug-ng
X-Devuan-PR-Keywords: 
References: <20181113023415.54c42f43@d44>
Received: via spool by [email protected] id=B256.157920720719495
          (code B ref 256); Thu, 16 Jan 2020 20:48:02 +0000
Received: (at 256) by bugs.devuan.org; 16 Jan 2020 20:40:07 +0000
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Thu, 16 Jan 2020 20:40:07 +0000 (UTC)
Received: from mx.hindley.org.uk (mohindley.plus.com [81.174.245.179])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id ADED4F60B7B
	for <[email protected]>; Thu, 16 Jan 2020 21:30:25 +0100 (CET)
Received: from apollo.hindleynet ([192.168.1.3] helo=apollo)
	by mx.hindley.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1isBmZ-0008Ci-Ef
	for [email protected]; Thu, 16 Jan 2020 20:30:23 +0000
Received: from mark by apollo with local (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1isBmY-0006uD-6q
	for [email protected]; Thu, 16 Jan 2020 20:30:22 +0000
Date: Thu, 16 Jan 2020 20:30:22 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
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=0.0 required=5.0 tests=FAKE_REPLY_C,SPF_PASS
	autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

Control: merge -1 242

Message received at [email protected]:

Received: (at 256) by bugs.devuan.org; 16 Jan 2020 20:40:07 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Thu, 16 Jan 2020 20:40:07 +0000 (UTC)
Received: from mx.hindley.org.uk (mohindley.plus.com [81.174.245.179])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id ADED4F60B7B
	for <[email protected]>; Thu, 16 Jan 2020 21:30:25 +0100 (CET)
Received: from apollo.hindleynet ([192.168.1.3] helo=apollo)
	by mx.hindley.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1isBmZ-0008Ci-Ef
	for [email protected]; Thu, 16 Jan 2020 20:30:23 +0000
Received: from mark by apollo with local (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1isBmY-0006uD-6q
	for [email protected]; Thu, 16 Jan 2020 20:30:22 +0000
Date: Thu, 16 Jan 2020 20:30:22 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Subject: Re: bug#256: Acknowledgement ([reportbug-ng] ..devuan's reportbug-ng
 obviously should report bugs to [email protected])
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debbugs-No-Ack: No Thanks
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Status: No, score=0.0 required=5.0 tests=FAKE_REPLY_C,SPF_PASS
	autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

Control: merge -1 242