From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: release 2010-12: slugos does not build due to handhelds.org breakage
Date: Fri, 3 Dec 2010 13:45:34 +0100 [thread overview]
Message-ID: <20101203124534.GA3403@jama> (raw)
In-Reply-To: <AANLkTi=g1i2wB-9MKVh8AMctnFJVUccYFw0RYf600Tm-@mail.gmail.com>
On Fri, Dec 03, 2010 at 01:37:51PM +0100, Frans Meulenbroeks wrote:
> Still get this on a clean build (machine nslu2le, distro slugos image
> slugos-image, rm-ed downloads, sources.openembedded.org as premirror).
that's because slugos uses different SRCDATE for this package
./distro/include/slugos.inc:SRCDATE_ipkg-utils-native ?= "20060106"
I don't have that file in my downloads dir...
Regards,
> OTE: package ipkg-utils-native-1.6+cvs20050404-r25: task do_fetch: Started
> NOTE: fetch http://anoncvs@sources.openembedded.org//ipkg-utils_anoncvs.handhelds.org__20060106.tar.gz
> --2010-12-03 10:23:42--
> http://anoncvs@sources.openembedded.org//ipkg-utils_anoncvs.handhelds.org__20060106.tar.gz
> Resolving sources.openembedded.org... 140.211.169.165
> Connecting to sources.openembedded.org|140.211.169.165|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-12-03 10:23:43 ERROR 404: Not Found.
>
> cvs [checkout aborted]: connect to
> anoncvs.handhelds.org(128.31.0.23):2401 failed: Connection refused
>
> Frans
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
prev parent reply other threads:[~2010-12-03 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 12:37 release 2010-12: slugos does not build due to handhelds.org breakage Frans Meulenbroeks
2010-12-03 12:45 ` Martin Jansa [this message]
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=20101203124534.GA3403@jama \
--to=martin.jansa@gmail.com \
--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 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.