mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH] ptrtd: move to staging
Date: Tue, 26 Feb 2019 16:58:34 +0100	[thread overview]
Message-ID: <20190226155834.17094-1-rhi@pengutronix.de> (raw)

Unmaintained version of a probably no longer needed software, both URLs
dead or claim deadness.

Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
 rules/ptrtd.in | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/rules/ptrtd.in b/rules/ptrtd.in
index a0fb0027c..6f3c7f113 100644
--- a/rules/ptrtd.in
+++ b/rules/ptrtd.in
@@ -1,4 +1,6 @@
-## SECTION=networking_ipv6_transition
+## SECTION=staging
+## old section:
+### SECTION=networking_ipv6_transition
 
 config PTRTD
 	tristate
@@ -7,13 +9,17 @@ config PTRTD
 	  This is a Portable Transport Relay Translator Daemon (pTRTd)
 	  as specified by RFC 3142 (tcp, udp)
 
+	  STAGING: remove in ptxdist-2020.02.0
+
 	  Beware: This is rather old voodoo, last upstream update was
-	  in 2002. This ptxdist package ist provided primarily for
+	  in 2002, and upstream was declared dead in 2010.
+	  This ptxdist package ist provided primarily for
 	  test environments, ipv6 transition planing, etc.
 
 	  DO NOT USE PTRTD EXCEPT IN AN ISOLATED NETWORK.
 
 	  References:
 	  http://www.litech.org/ptrtd/		(now unsupported)
-	  http://jk.fr.eu.org/debian/unstable/  (updated version)
+	  http://web.archive.org/web/20130110070644/http://jk.fr.eu.org/debian/unstable/
+	                                        (updated version, but original URL dead)
 	  http://www.faqs.org/rfcs/rfc3142.html
-- 
2.20.1


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

                 reply	other threads:[~2019-02-26 15:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190226155834.17094-1-rhi@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox