From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: linux_2.6.24.bb: patch file unavailable
Date: Thu, 16 Apr 2009 11:11:32 +0200 [thread overview]
Message-ID: <gs6so4$8mb$2@ger.gmane.org> (raw)
In-Reply-To: <69E6C70090A0A14498CC98FAE5E06B6E3CF75B@hiob.intern.dresearch.de>
On 16-04-09 10:51, Sledz, Steffen wrote:
> linux_2.6.24.bb since 2008-02-16 14:33:38 +0000 contains
>
> SRC_URI = "${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/linux-2.6.24.tar.bz2 \
> http://kamikaze.waninkoko.info/patches/2.6.24/kamikaze1/broken-out/squashfs-lzma-2.6.24.patch;patch=1 \
>
> But this patch is no longer available there:
>
> $ wget http://kamikaze.waninkoko.info/patches/2.6.24/kamikaze1/broken-out/squashfs-lzma-2.6.24.patch
> --07:58:38-- http://kamikaze.waninkoko.info/patches/2.6.24/kamikaze1/broken-out/squashfs-lzma-2.6.24.patch
> => `squashfs-lzma-2.6.24.patch'
> Resolving kamikaze.waninkoko.info... failed: Name or service not known.
>
> Does somebody know a new URL for that?
http://www.angstrom-distribution.org/unstable/sources/squashfs-lzma-2.6.24.patch
> Or should i upload a copy to the OE repo from my local sources cache?
Personally I strongly dislike using patches from remote hosts, since the
get changed/deleted/etc beyond our control.
FWIW: squashfs is now in mainline :)
regards,
Koen
next prev parent reply other threads:[~2009-04-16 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 8:51 linux_2.6.24.bb: patch file unavailable Sledz, Steffen
2009-04-16 9:11 ` Koen Kooi [this message]
2009-04-16 13:21 ` Denys Dmytriyenko
2009-04-18 15:37 ` Leon Woestenberg
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='gs6so4$8mb$2@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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