From: Thomas Osterried <thomas@osterried.de>
To: Patrick Ouellette <pouelle@debian.org>
Cc: Thomas Osterried <thomas@x-berg.in-berlin.de>,
David Ranch <linux-hams@trinnet.net>,
"Bernard, f6bvp" <f6bvp@free.fr>,
ralf@linux-mips.org, linux-hams <linux-hams@vger.kernel.org>
Subject: Re: Compiling FBB
Date: Tue, 8 Nov 2011 21:12:24 +0100 [thread overview]
Message-ID: <201111082112.25176.thomas@osterried.de> (raw)
In-Reply-To: <20111108200524.GE30829@flying-gecko.net>
Am Dienstag, den 08. November 2011 um 21:05:24 Uhr, schrieb Patrick Ouellette <pouelle@debian.org> in <20111108200524.GE30829@flying-gecko.net>:
> On Fri, Oct 21, 2011 at 02:04:00PM +0200, Thomas Osterried wrote:
> >
> > On 2011-10-20 21:02:44 -0700, David Ranch <linux-hams@trinnet.net>
> > wrote in <4EA0EEE4.7050502@trinnet.net>:
> > >
> > > Hello Bernard, Ralf, Thomas,
> > >
> > > I've been meaning to ask this question for a while now: Do you know
> > > why the official version of the ax25 apps/libs/tools hasn't been
> > > updated in ages?
> >
> > Unfortunately, there's no debian-developer who regulary builds new
> > packages from the CVS head of ax25-apps, -tools and libax25.
>
> I used maintain ax25 for Debian to a long time ago. Apparently I will be
> picking up support in Debian again since no one else seems to want to and the
> "team maintainer" concept has fallen apart.
>
> The first order of business I have to attend to is the apparent need to rename
> the node package and binary to ax25-node.
>
> www.linux-ax25.org is apparently down right now?
yes, it's currently under maintainance:
** PROBLEM Service Alert: linux-ax25/FTP is CRITICAL **
Von:
root@mail-smt.osterried.it
An:
thomas@x-berg.in-berlin.de
Datum:
Tue Nov 8 21:00:04 2011
***** Nagios *****
Notification Type: PROBLEM
Service: FTP
Host: linux-ax25
Address: 81.2.74.12
State: CRITICAL
Date/Time: Tue Nov 8 21:00:04 CET 2011
Additional Info:
Connection refused
>
> (the Google repo mentioned is: http://code.google.com/p/linuxax25/ )
>
> 73,
>
> Pat
>
next prev parent reply other threads:[~2011-11-08 20:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 8:18 Compiling FBB f6bvp
2011-10-14 22:10 ` Miroslav Skoric
2011-10-14 22:20 ` Dave Platt
2011-10-15 7:55 ` Bernard, f6bvp
2011-10-15 10:00 ` Marc Coevoet
2011-10-17 11:25 ` Bernard, f6bvp
2011-10-18 20:07 ` RS232-USB conversion (was: Compiling FBB) Miroslav Skoric
2011-10-18 20:21 ` Gordon JC Pearce
2011-10-18 21:16 ` RS232-USB conversion Dave Platt
2011-10-18 21:00 ` Bruno Tréguier
2011-10-21 4:02 ` Compiling FBB David Ranch
2011-10-21 10:15 ` Bernard, f6bvp
2011-10-21 17:11 ` Lee Woldanski
2011-10-21 12:04 ` Thomas Osterried
2011-11-08 20:05 ` Patrick Ouellette
2011-11-08 20:12 ` Thomas Osterried [this message]
2011-11-08 21:22 ` Ralf Baechle DL5RB
2011-11-08 21:39 ` Bill Vodall
2011-11-08 22:09 ` Patrick Ouellette
2011-11-09 1:22 ` David Ranch
2011-11-09 7:09 ` Marc Coevoet
2011-11-09 9:31 ` Thomas Osterried
2011-11-09 9:36 ` Marco Di Martino (IW2OHX)
-- strict thread matches above, loose matches on Subject: below --
2011-11-09 9:14 Tomi Manninen
2011-10-02 15:41 Miroslav Skoric
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=201111082112.25176.thomas@osterried.de \
--to=thomas@osterried.de \
--cc=f6bvp@free.fr \
--cc=linux-hams@trinnet.net \
--cc=linux-hams@vger.kernel.org \
--cc=pouelle@debian.org \
--cc=ralf@linux-mips.org \
--cc=thomas@x-berg.in-berlin.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