Devuan logs - #57, boring messages

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

Subject: bug#57: devuan-doc: Add general guide on mixing and unmixing Devuan release branches
Reply-To: Michael Siegel <[email protected]>, [email protected]
Resent-From: Michael Siegel <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected]
Resent-Date: Sun, 16 Apr 2017 23:33:01 UTC
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
To: [email protected]
From: Michael Siegel <[email protected]>
Message-ID: <[email protected]>
Date: Mon, 17 Apr 2017 01:17:34 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101
 Icedove/45.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Package: devuan-doc

I've recently put together a howto on reverting to stable from a mixed
stable/testing setup in Devuan (See:
https://dev1galaxy.org/viewtopic.php?id=512).

While going over that again and making notes for a few improvements, I
thought that it would probably be a good idea to include a general guide
on mixing and unmixing Devuan release branches into the official Devuan
documentation.

Maybe my howto can be used as a starting point for that.

Message sent:

X-Loop: [email protected]
From: [email protected] (Devuan bug Tracking System)
To: Michael Siegel <[email protected]>
Subject: bug#57: Acknowledgement (devuan-doc: Add general guide on mixing and unmixing Devuan release branches)
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]>
Precedence: bulk
X-Devuan-PR-Message: ack 57
X-Devuan-PR-Package: devuan-doc
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.

Devuan Bugs Owner
(administrator, Devuan bugs database)

Message received at [email protected]:

Date: Wed, 26 Apr 2017 23:47:26 +0100
From: KatolaZ <[email protected]>
To: [email protected]
Subject: ...
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)

severity 57 wishlist

severity 56 wishlist

reassign 67 devuan-installer

Message sent:

X-Loop: [email protected]
From: [email protected] (Devuan bug Tracking System)
To: KatolaZ <[email protected]>
Cc: [email protected]
Subject: bug#57: marked as done (devuan-doc: Add general guide on mixing and unmixing Devuan release branches)
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]> <[email protected]>
Precedence: bulk
X-Devuan-PR-Message: closed 57
X-Devuan-PR-Package: devuan-doc
X-Devuan-PR-Keywords: 

Your message dated Sat, 9 Dec 2017 12:48:58 +0000
with message-id <[email protected]>
and subject line closed
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; 16 Apr 2017 23:18:31 +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); Mon, 17 Apr 2017 01:18:31 +0200 (CEST)
Received: from poseidon.malbolge.net (poseidon.malbolge.net [5.45.108.48])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by tupac2.dyne.org (Postfix) with ESMTPS id 337061896A5
	for <[email protected]>; Sun, 16 Apr 2017 23:17:46 +0000 (UTC)
Received: from poseidon.malbolge.net (localhost [127.0.0.1])
	by poseidon.malbolge.net (OpenSMTPD) with ESMTP id 8bddc141
	for <[email protected]>;
	Mon, 17 Apr 2017 01:17:45 +0200 (CEST)
Received: from hermes.malbolge.net (hermes.malbolge.net [192.168.123.201])
	by poseidon.malbolge.net (OpenSMTPD) with ESMTPSA id 279fb163 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO)
	for <[email protected]>;
	Mon, 17 Apr 2017 01:17:45 +0200 (CEST)
Received: from poseidon.malbolge.net ([10.0.10.1]:5851 helo=127.0.0.1)
	by hermes.malbolge.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1cztQO-0005QO-E3
	for [email protected]; Mon, 17 Apr 2017 01:17:44 +0200
To: [email protected]
From: Michael Siegel <[email protected]>
Subject: devuan-doc: Add general guide on mixing and unmixing Devuan release
 branches
Message-ID: <[email protected]>
Date: Mon, 17 Apr 2017 01:17:34 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101
 Icedove/45.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, score=-0.0 required=5.0 tests=RP_MATCHES_RCVD,SPF_PASS
	autolearn=disabled version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tupac2

Package: devuan-doc


I've recently put together a howto on reverting to stable from a mixed
stable/testing setup in Devuan (See:
https://dev1galaxy.org/viewtopic.php?id=512).

While going over that again and making notes for a few improvements, I
thought that it would probably be a good idea to include a general guide
on mixing and unmixing Devuan release branches into the official Devuan
documentation.

Maybe my howto can be used as a starting point for that.
---------------------------------------
Received: (at 57-close) by bugs.devuan.org; 9 Dec 2017 12:50:06 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Sat, 09 Dec 2017 13:50:06 +0100 (CET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	(Authenticated sender: [email protected])
	with ESMTPSA id 905E6F60947
Date: Sat, 9 Dec 2017 12:48:58 +0000
From: KatolaZ <[email protected]>
To: [email protected]
Subject: closed
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="FQCVrJSEImXpcASh"
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.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tupac3.dyne.org


--FQCVrJSEImXpcASh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

It looks like this have been solved by appropriate documentation added
to the wiki. I am closing it now

--FQCVrJSEImXpcASh
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlor27oACgkQXyCzrgtfBi+jzACdFqvs6FmErArHWHmiMLq7oMVb
CgcAn3OjUXexN1EYrgI+rGl5GbKCDwRq
=4Bsu
-----END PGP SIGNATURE-----

--FQCVrJSEImXpcASh--

Message sent:

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

This is an automatic notification regarding your bug report
#57: devuan-doc: Add general guide on mixing and unmixing Devuan release branches,
which was filed against the devuan-doc 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 57-close) by bugs.devuan.org; 9 Dec 2017 12:50:06 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from tupac3.dyne.org [195.169.149.119]
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Sat, 09 Dec 2017 13:50:06 +0100 (CET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	(Authenticated sender: [email protected])
	with ESMTPSA id 905E6F60947
Date: Sat, 9 Dec 2017 12:48:58 +0000
From: KatolaZ <[email protected]>
To: [email protected]
Subject: closed
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="FQCVrJSEImXpcASh"
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.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tupac3.dyne.org


--FQCVrJSEImXpcASh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

It looks like this have been solved by appropriate documentation added
to the wiki. I am closing it now

--FQCVrJSEImXpcASh
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlor27oACgkQXyCzrgtfBi+jzACdFqvs6FmErArHWHmiMLq7oMVb
CgcAn3OjUXexN1EYrgI+rGl5GbKCDwRq
=4Bsu
-----END PGP SIGNATURE-----

--FQCVrJSEImXpcASh--