[poky] bernard-5.0.1, poky-image-lsb, beagle, build error

[Saul Wold]

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.

Sau!

> Regards,
>
> Robert
>
>
> ..."C++ has its place in the history of programming languages. Just as
> Caligula has his place in the history of the Roman Empire." - Robert Firth
>
> My public pgp key is available at:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
>
>
> _______________________________________________
> poky mailing list
> poky at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>