Daniel,
> I don't know what b76 is either, so my first inclination
> would be to assume it doesn't apply to me and to avoid it.
"eups list -h" gives:
> Normally for each product, printed will be the product name, version,
> its currently assigned tags, and whether it is currently setup. If -v
> is given, the EUPS database and and the product installation directory
> will also be printed.
All of those things after the version labels are tags. b76 is
supposed to be a tag created by buildbot (hence the "b"). You can look
in versiondb.git (nominally at
https://dev.lsstcorp.org/cgit/LSST/DMS/devenv/versiondb.git/) to see
what the contents of b76 are. In particular, you can look at the
contents of manifests/b76.txt to see what the SHA1s of all the packages
in the build were, as well as the "git describe" version.
Unfortunately, in this case I think b76 is actually from a
different versiondb that Jacek has locally, rather than the buildbot
one. Nevertheless, all the b76-tagged packages should have been built
together, so they should be able to be used together. The way to do
that is to specify that tag (with "-t b76") whenever you setup a
package.
--
Kian-Tat Lim, LSST Data Management, [log in to unmask]
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1
|