From: Thomas Osterried <thomas@osterried.de>
To: "Mike McCarthy, W1NR" <lists@w1nr.net>
Cc: linux-hams@vger.kernel.org
Subject: Re: Replacement for linux-ax25.org git?
Date: Tue, 8 Nov 2022 16:14:55 +0100 [thread overview]
Message-ID: <Y2pybykD07N1nBG+@x-berg.in-berlin.de> (raw)
In-Reply-To: <ed2bfaa6-4c68-5743-90aa-0149322e5f94@w1nr.net>
On Tue, Nov 08, 2022 at 08:41:22AM -0500, Mike McCarthy, W1NR wrote:
> Does anyone know if the repos at linux-ax25.org
> were archived anywhere before it went offline?
linux-ax25.org domain is dead due to dns fail.
The host running the repos is still in service and
is available under linux-ax25.in-berlin.de.
That dns name is not my favourite choice (see my post on this list about this topic),
but it is future proven, does not depend on a single person, and is under full control.
I hoped linux-ax25.org will come back. Now we have to live with that solution.
vy 73,
- Thomas dl9sau
>
> Mike, W1NR
>
> On 11/8/2022 7:41 AM, Dave Hibberd wrote:
> > Hi all,
> >
> > I'm one of the folks in the Debian Hamradio team with an active interest in keeping our packet tooling going.
> >
> > With the demise of linux-ax25.org and discussions here about change of maintenance, is there a new canonical repo for ax25-tools and similar where these components are held?
> >
> > Our last upstram mirror was about 3 years ago, we've got it tagged as 0.0.10-rc5+git20190411+3595f87 [1] - this is what will have flowed down into Ubuntu, Raspberry Pi OS etc.
> >
> > If there's currently active work going on with these userland components, where is it happening so we can rebase our packages?
> > If not, I guess this is something we need to make a decision on how to proceed as a community!
> >
> >
> > [1]: https://salsa.debian.org/debian-hamradio-team/ax25-tools/-/tree/upstream
> >
next prev parent reply other threads:[~2022-11-08 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 12:41 Replacement for linux-ax25.org git? Dave Hibberd
2022-11-08 13:41 ` Mike McCarthy, W1NR
2022-11-08 15:14 ` Thomas Osterried [this message]
2022-11-08 17:52 ` Steven R. Loomis
[not found] ` <29F7FF8E-64E6-4927-9DE6-23E98C763832@gmail.com>
2022-11-08 18:10 ` Thomas Osterried
2022-11-08 23:28 ` Dave Hibberd
2022-11-10 2:03 ` John Weaver
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=Y2pybykD07N1nBG+@x-berg.in-berlin.de \
--to=thomas@osterried.de \
--cc=linux-hams@vger.kernel.org \
--cc=lists@w1nr.net \
/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