Skip to contentSkip to conversation

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

PATCH Robert Berger 4 participants 8 messages Jun 14, 2011 – Jun 15, 2011

lore
Share & tools
lore
#0 lore raw

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:

(quoted diff) +0 -0

b/meta/recipes-extended/psmisc/psmisc.inc
index 8b391f4..460affc 100644

meta/recipes-extended/psmisc/psmisc.inc +1 -1
@@ -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?

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

#1 lore raw
Quoted 39 lines · Robert Berger

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:

meta/recipes-extended/psmisc/psmisc.inc +2 -1
index 8b391f4..460affc 100644
@@ -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.

Quoted 7 lines

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!

Quoted 17 lines

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
[email protected]
https://lists.yoctoproject.org/listinfo/poky

#2 lore raw
Quoted 63 lines · Saul Wold
Quoted 40 lines · Robert Berger

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:

meta/recipes-extended/psmisc/psmisc.inc +2 -1
index 8b391f4..460affc 100644
@@ -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.

Quoted 7 lines

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!

Quoted 6 lines

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.

Signature · 2 lines
Tom Rini
Mentor Graphics Corporation
#3 lore raw
Quoted 69 lines · Tom Rini
Quoted 68 lines · Saul Wold
Quoted 40 lines · Robert Berger

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:

meta/recipes-extended/psmisc/psmisc.inc +2 -1
index 8b391f4..460affc 100644
@@ -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.

Quoted 7 lines

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.

Quoted 5 lines
Quoted 1 line

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.

What worries me is that it should be doing this by default. The question is therefore why isn't that working? Is that source on the sources mirror?

Cheers,

Richard

#4 lore raw
Quoted 72 lines · Richard Purdie
Quoted 71 lines · Tom Rini
Quoted 69 lines · Saul Wold
Quoted 40 lines · Robert Berger

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:

meta/recipes-extended/psmisc/psmisc.inc +2 -1
index 8b391f4..460affc 100644
@@ -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.

Quoted 7 lines

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.

Quoted 7 lines
Quoted 3 lines

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.

What worries me is that it should be doing this by default. The question is therefore why isn't that working? Is that source on the sources mirror?

Fall-out from the IP change right now? Or webserver needs a restart? Chrome isn't connecting atm and I have the same IP as the LF servers say...

Signature · 2 lines
Tom Rini
Mentor Graphics Corporation
#5 lore raw
In reply to Saul Wold

Hi,

Quoted 11 lines · Saul Wold

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!

Quoted 6 lines

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.

There is a file called meta/conf/distro/poky.conf which contains

PREMIRRORS ?= "\

bzr://.*/.*   http://autobuilder.yoctoproject.org/sources/ \n \
cvs://.*/.*   http://autobuilder.yoctoproject.org/sources/ \n \
git://.*/.*   http://autobuilder.yoctoproject.org/sources/ \n \
hg://.*/.*    http://autobuilder.yoctoproject.org/sources/ \n \
osc://.*/.*   http://autobuilder.yoctoproject.org/sources/ \n \
p4://.*/.*    http://autobuilder.yoctoproject.org/sources/ \n \
svk://.*/.*   http://autobuilder.yoctoproject.org/sources/ \n \
svn://.*/.*   http://autobuilder.yoctoproject.org/sources/ \n"

MIRRORS =+ "\

ftp://.*/.*      http://autobuilder.yoctoproject.org/sources/ \n \
http://.*/.*     http://autobuilder.yoctoproject.org/sources/ \n \
https://.*/.*    http://autobuilder.yoctoproject.org/sources/ \n"

Isn't this supposed to be included by default?
Do I need to do something else to activate MIRRORS/PREMIRRORS?

Regards,

Robert

Quoted 3 lines

Sau!

...The significant problems we face cannot be solved at the same level of thinking we were at when we created them. - Albert Einstein

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1

#6 lore raw
Quoted 33 lines · Robert Berger

Hi,

Quoted 11 lines · Saul Wold

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!

Quoted 6 lines

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.

There is a file called meta/conf/distro/poky.conf which contains

PREMIRRORS ?= "\

bzr://.*/.*   http://autobuilder.yoctoproject.org/sources/ \n \
cvs://.*/.*   http://autobuilder.yoctoproject.org/sources/ \n \
git://.*/.*   http://autobuilder.yoctoproject.org/sources/ \n \
hg://.*/.*    http://autobuilder.yoctoproject.org/sources/ \n \
osc://.*/.*   http://autobuilder.yoctoproject.org/sources/ \n \
p4://.*/.*    http://autobuilder.yoctoproject.org/sources/ \n \
svk://.*/.*   http://autobuilder.yoctoproject.org/sources/ \n \
svn://.*/.*   http://autobuilder.yoctoproject.org/sources/ \n"
Quoted 8 lines

MIRRORS =+ "\

ftp://.*/.*      http://autobuilder.yoctoproject.org/sources/ \n \
http://.*/.*     http://autobuilder.yoctoproject.org/sources/ \n \
https://.*/.*    http://autobuilder.yoctoproject.org/sources/ \n"

Isn't this supposed to be included by default?
Do I need to do something else to activate MIRRORS/PREMIRRORS?

That's the right list and your not overriding them at all?

Then it should pick it up. Coulg you run a bitbake -DD -v psmisc -c fetch and send me the out put, on the failing build that you have?

This might help identify if there's a problem.

Thanks
Sau!

Quoted 19 lines

Regards,

Robert

Quoted 3 lines

Sau!

...The significant problems we face cannot be solved at the same level of thinking we were at when we created them. - Albert Einstein

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

#7 lore raw

Hi,

Quoted 3 lines · Saul Wold

Then it should pick it up. Coulg you run a bitbake -DD -v psmisc -c fetch and send me the out put, on the failing build that you have?

It magically healed over night;)

NOTE: fetch http://downloads.sourceforge.net/psmisc/psmisc-22.2.tar.gz
DEBUG: executing /usr/bin/env wget -t 5 -q --passive-ftp -P /work/rber/downloads 'http://downloads.sourceforge.net/psmisc/psmisc-22.2.tar.gz'
DEBUG: Fetcher accessed the network with the command /usr/bin/env wget -t 5 -q --passive-ftp -P /work/rber/downloads 'http://downloads.sourceforge.net/psmisc/psmisc-22.2.tar.gz'

Yesterday night it could not fetch it from this location, but in the meantime I guess someone cooked something on sourceforge and points to the new location of the file.

wget http://downloads.sourceforge.net/psmisc/psmisc-22.2.tar.gz
--2011-06-15 09:00:30--
http://downloads.sourceforge.net/psmisc/psmisc-22.2.tar.gz
Resolving downloads.sourceforge.net... 216.34.181.59 Connecting to downloads.sourceforge.net|216.34.181.59|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location:
http://downloads.sourceforge.net/project/psmisc/psmisc/22.2/psmisc-22.2.tar.gz
[following]
--2011-06-15 09:00:31--
http://downloads.sourceforge.net/project/psmisc/psmisc/22.2/psmisc-22.2.tar.gz
Reusing existing connection to downloads.sourceforge.net:80. HTTP request sent, awaiting response... 302 Moved Temporarily Location:
http://mesh.dl.sourceforge.net/project/psmisc/psmisc/22.2/psmisc-22.2.tar.gz
[following]
--2011-06-15 09:00:31--
http://mesh.dl.sourceforge.net/project/psmisc/psmisc/22.2/psmisc-22.2.tar.gz
Resolving mesh.dl.sourceforge.net... 213.203.218.122 Connecting to mesh.dl.sourceforge.net|213.203.218.122|:80... connected. HTTP request sent, awaiting response... 200 OK
Length: 244247 (239K) [application/x-gzip]
Saving to: `psmisc-22.2.tar.gz'

100%[===================================================================================>]
244,247 345K/s in 0.7s

2011-06-15 09:00:32 (345 KB/s) - `psmisc-22.2.tar.gz' saved [244247/244247]
Quoted 5 lines

This might help identify if there's a problem.

Thanks
Sau!

Regards,

Robert
..."You are in a twisty little passage of standards, all conflicting." - Michael Meissner, [email protected]

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1