RE: LSB Sample Implementation - 11 packages retrieval failed

The instructions are accurate.  Not all of the
locations are accurate.

> The location you had provided
> http://ftp.freestandards.org/pub/lsb/impl/packages has all 
> the packages but
> I can't tell if this site is used for download by the
> "extras/entitycheck.py" command . I guess I can download each package
> separately but don't know if that will be most efficient 
> route...  Is there
> a way to download all of these packages as a part of the
> "extras/entitycheck.py" command.

That's what the -f flag is for (-f = "fetch").

entitycheck.py automates a number of functions that
are not done by the version of the builder tool
(nALFS) that we use.  As an aside note, all of the
interesting ones - capturing package download locations,
actual package download and checksum verification - 
are done by current version of the tool so if we
ever manage a version uplift, entitycheck won't
be needed any longer.

If entitycheck won't download them, why don't
you just wget the missing files from the
above freestandards.org location.


The gory details of what's going on:

entitycheck.py tries to parse the entity file
(entities/package) to determine a list of
package names and versions.  This is a little
painful since it's not valid xml, so we can't
just use an xml parser, but never mind.

If those packages aren't already in place in
the designated package location, an attempt is
made to download them.  This is done by
cross-referencing the packages with a list of 
places to download those packages from. That 
list is extras/package_locations. There are 
potentially three places to try downloading a 
package from: a primary, an optional secondary 
(both of these appear in package_locations) and 
then a backup site on freestandards.org in case 
the first two fail.  Usually, if we know that a 
package may be moved on the primary we include a
stable secondary (often what happens is that as
a new version of a package is released the previous
one is moved to a subdirectory such as "old").

Unfortunately, we can't always predict future
behavior by maintainers based on past evidence,
so some things have "vanished" from the supposedly
stable locations since the information for LSB 1.3
was frozen - sorry for this incovenience, but 
it's kind of out of our control.