All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: <poky@yoctoproject.org>
Subject: Re: bernard-5.0.1, poky-image-lsb, beagle, build error
Date: Tue, 14 Jun 2011 12:38:26 -0700	[thread overview]
Message-ID: <4DF7B8B2.7050709@mentor.com> (raw)
In-Reply-To: <4DF7B675.6050304@linux.intel.com>

On 06/14/2011 12:28 PM, Saul Wold wrote:
> On 06/14/2011 11:20 AM, Robert Berger wrote:
>> Hi,
>>
>> I hit a build error with the tag: bernard-5.0.1
>> while trying to build poky-image-lsb, which failed, because psmisc could
>> not be downloaded.
>>
>> I fixed it like this:
>>
>> diff --git a/meta/recipes-extended/psmisc/psmisc.inc
>> b/meta/recipes-extended/psmisc/psmisc.inc
>> index 8b391f4..460affc 100644
>> --- a/meta/recipes-extended/psmisc/psmisc.inc
>> +++ b/meta/recipes-extended/psmisc/psmisc.inc
>> @@ -10,8 +10,9 @@ SECTION = "base"
>>   PRIORITY = "required"
>>   DEPENDS = "ncurses virtual/libintl"
>>
>> -SRC_URI = "${SOURCEFORGE_MIRROR}/psmisc/psmisc-${PV}.tar.gz \
>> +SRC_URI =
>> "${SOURCEFORGE_MIRROR}/project/psmisc/psmisc/${PV}/psmisc-${PV}.tar.gz \
>>             file://libintl-link.patch;patch=1"
>> +
>>   S = "${WORKDIR}/psmisc-${PV}"
>>
>> This means that the tag bernard-5.0.1 does not build anymore for the
>> beagle and most likely other platforms won't build as well out of the
>> box.
>>
>> That's just a small issue, but my problem is more generic.
>>
>> Assuming someone makes a distro based on a tag e.g. bernard-5.0.1 and
>> wants to rebuild this distro in a year from now.
>>
>> Packages might have disappeared, or in best case just the URLs changed.
>> In any case the distro will not build anymore out of the box.
>>
>> I would ideally like to be able to reproduce exactly what I have in a
>> couple of years from now, which seems impossible due to dependencies
>> external to poky which are not controlled by this community.
>>
>> I could come up with a solution, where local copies of packages are kept
>> e.g. in a local download directory, but this would mean, that I'll need
>> to build and test all possible platforms just after the releases (where
>> everything still works) and not when I'll actually need them.
>>
>> What's the best way to deal with this?
>>
> Robert,
> 
> This is a know problem with Upstream sources moving, dropping older
> versions or just doing strange behavior.
> 
> Currently, if you have MIRRORS, it should pick up the original upstream
> source tarball from http://autobuilder.yoctoprojecto.org/sources, if you
> want to avoid checking any upstream source, you can set
> PREMIRRORS_prepend for ftp, http, and https URLs to the
> autobuilder/sources location. This location should maintain all tarballs
> for releases.
> 
> We had a similar problem with distcc right about the time we released
> 5.0.1!
> 
> You can use a local solution also with PREMIRRORS_prepend, as well as
> setting the BB_NO_NETWORK, which will force bitbake to not look on the
> network for any upstreams, this assumes you have everything preloaded
> locally.
> 
> Let us know if this is what you are looking for.

I'd suggest making poky look at a poky-mirror as a "last resort" mirror
by default (similar to angstrom and angstrom-mirror.bbclass), at least
for release branches.

-- 
Tom Rini
Mentor Graphics Corporation


  reply	other threads:[~2011-06-14 19:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 18:20 bernard-5.0.1, poky-image-lsb, beagle, build error Robert Berger
2011-06-14 19:28 ` Saul Wold
2011-06-14 19:38   ` Tom Rini [this message]
2011-06-14 19:52     ` Richard Purdie
2011-06-14 20:00       ` Tom Rini
2011-06-14 20:55   ` Robert Berger
2011-06-14 21:47     ` Saul Wold
2011-06-15  6:04       ` Robert Berger

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=4DF7B8B2.7050709@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=poky@yoctoproject.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.