From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: libmatthew-java-0.7.1.tar.gz not fetchable
Date: Thu, 15 Mar 2012 11:32:43 +0100 [thread overview]
Message-ID: <4F61C54B.1000609@dresearch-fe.de> (raw)
libmatthew-java-0.7.1.tar.gz (used in 2011.03-maintenance branch) is no longer fetchable from it's original location (the maintainer provides the latests version only). And i did not found another reliable source.
Can someone put the tarball into the OE and/or Angstrom mirrors?
Thx,
Steffen
PS: I can send the tarball on request.
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next reply other threads:[~2012-03-15 10:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 10:32 Steffen Sledz [this message]
2012-03-19 7:49 ` libmatthew-java-0.7.1.tar.gz not fetchable Steffen Sledz
2012-03-19 15:18 ` Tom Rini
2012-03-19 15:44 ` Frans Meulenbroeks
2012-03-19 16:21 ` Tom Rini
2012-03-20 7:13 ` Steffen Sledz
2012-03-20 7:42 ` Frans Meulenbroeks
2012-03-20 14:22 ` Tom Rini
2012-03-21 6:47 ` Steffen Sledz
2012-03-21 10:36 ` Steffen Sledz
2012-03-21 10:37 ` [PATCH] libmatthew-0.7.1: SRC_URI updated Steffen Sledz
2012-03-21 12:58 ` Frans Meulenbroeks
2012-03-21 14:44 ` Tom Rini
2012-03-21 14:46 ` Tom Rini
2012-03-22 7:01 ` Steffen Sledz
2012-03-22 22:13 ` Tom Rini
2012-03-23 7:01 ` Steffen Sledz
2012-03-23 15:20 ` Tom Rini
2012-03-21 14:47 ` Steffen Sledz
2012-03-20 14:16 ` libmatthew-java-0.7.1.tar.gz not fetchable Khem Raj
2012-03-20 14:26 ` Steffen Sledz
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=4F61C54B.1000609@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=openembedded-devel@lists.openembedded.org \
/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