 |
 |
Mario, Robyn We need guidance on how to publish different releases of Qserv. Please see below. I don't want us to maintain Qserv on multiple distribution servers. Thanks, Jacek On 08/27/2014 03:17 AM, Fabrice Jammes wrote: > The problem I'd like to solve is : > I think that lsstsw build tool uses by default the tip of each master > branch of a given product dependencies. This may be wrong is the tip a > of dependency is broken, or if you want to re-package a previous Qserv > version (which may be only compliant with previous versions of the > dependencies and not the current ones). > => That's why i'm interesting in learning how to describe in lsstsw/eups > the dependencies versions set for a given Qserv version. > > I'm very interested about having informations about buildbot, but for > now it seems that even if Mario succeeded in integrating Qserv with > official LSST distribution server, only one Qserv version is currently > distributed > (see http://sw.lsstcorp.org/eupspkg/products/ which only contains > qserv-master-g6c2884f158.eupspkg) and furthermore the last xrootd > version isn't distributed. That's why I think buildbot integration has > not yet been performed, and for now distribution of new > Qserv/dependencies version still have to be done by hand (on my side I'm > only able to publish this under my user account, in > http://lsst-web.ncsa.illinois.edu/~fjammes/qserv-dev/). It would be fine > to be able to publish multiples Qserv releases/version in official LSST > distribution server, in preference with buildbot, or even by hand with > lsstsw. ######################################################################## 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