From: Alexander Morlang <alx@dd19.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] development-ipkgs broken
Date: Thu, 18 Oct 2007 16:37:34 +0200 [thread overview]
Message-ID: <47176FAE.6050608@dd19.de> (raw)
In-Reply-To: <200710181408.50444.axel@open-mesh.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Axel Neumann schrieb:
> Hey Dennis,
>
> On Dienstag 16 Oktober 2007, Dennis Bartsch wrote:
>> hey,
>>
>> installation of the latest development-ipkgs (at least the i386 ones) of
>> 0.3-beta fails, because control.tar.gz is missing:
>>
>> root@NicoAP5G:~# ipkg install
>> http://downloads.open-mesh.net/batman/development/i386/batmand_0.3-beta-rv7
>> 22_i386-gc-elf-32-lsb-dynamic.tgz Downloading
>
> Hmm, the tgz in that folder is a tgz :-)
> I think there has never been a ipk in the development/i386 folder - maybe
> there should.
> Anyway, there are ipk packages for i386 here:
> http://downloads.open-mesh.net/batman/development/misc/batmand_0.3-beta-current_i386-gc-elf-32-lsb-static.ipk
> or here:
> http://downloads.open-mesh.net/batman/development/misc/batmand_0.3-beta-current_i386-gc-elf-32-lsb-dynamic.ipk
>
> If you can confirm that its working for i386-kamikaze I'll open a
> deveopment/i386-kamikaze folder.
how about just maintaing the batman package in kamikaze?
>
> Yesterday you also mentioned some problems with the binary packages for ARM
> CPUs. Ipkg and tgz can be found here:
> http://downloads.open-mesh.net/batman/development/armv5te/
> Unfortunately, I do not remember the exact problem description ;-)
>
> ciao
> /axel
alex
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHF2+uhx2RbV7T5aERAsnzAKCQRILx+ZH+mOBib33/DkeqgoHrXACeNBum
vRmaZRP/Pwo8AzpiXkNNYuA=
=iPnZ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-10-18 14:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 12:38 [B.A.T.M.A.N.] strange default routes Dennis Bartsch
2007-10-15 13:41 ` a.anselmi
2007-10-15 14:08 ` Marek Lindner
2007-10-15 15:01 ` Dennis Bartsch
2007-10-15 14:14 ` elektra
2007-10-15 14:54 ` a.anselmi
2007-10-15 17:03 ` Dennis Bartsch
2007-10-16 13:15 ` Marek Lindner
2007-10-16 10:04 ` elektra
2007-10-16 11:43 ` [B.A.T.M.A.N.] development-ipkgs broken Dennis Bartsch
2007-10-18 12:08 ` Axel Neumann
2007-10-18 14:37 ` Alexander Morlang [this message]
2007-10-17 18:09 ` [B.A.T.M.A.N.] strange default routes Axel Neumann
2007-10-17 18:40 ` [B.A.T.M.A.N.] 0.3-beta testing Jan Hetges
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=47176FAE.6050608@dd19.de \
--to=alx@dd19.de \
--cc=b.a.t.m.a.n@open-mesh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.