LISTSERV mailing list manager LISTSERV 16.5

Help for QSERV-L Archives


QSERV-L Archives

QSERV-L Archives


QSERV-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

QSERV-L Home

QSERV-L Home

QSERV-L  February 2014

QSERV-L February 2014

Subject:

Re: Remarks and proposals about eupspkg

From:

Mario Juric <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Thu, 13 Feb 2014 13:54:23 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (92 lines)

On 2/13/14, 13:20 , Mario Juric wrote:
> 
> Fabrice et al,
> 	Questions re mysqlproxy: it depends on glib2 and libevent. Did you plan
> to make EUPS packages for these, or will you ask the users to install
> the required -dev[el] packages on their distributions?
> 

Ah, OK -- I see that libevent is already there. Let me know what you
intended to do re glib2; it won't take me more than 10 minutes to
package it.

Otherwise, I managed to build everything up to (but excluding) qserv:

======
[mjuric@lsst-dev /ssd/mjuric/buildbot/lsst_build master]$ time
./bin/lsst-build build ./build ./build/manifest.txt            libevent:
master_g410bd5abbb (already installed).
              python: 2.7_1_g4b5dedd60d (already installed).
               expat: master_g4a0254e0b2 (already installed).
       zopeinterface: master_g0277429914+0a4801e32d (already installed).
                 lua: master_ge6f8f65424 (already installed).
              xrootd: master_gc482612125 (already installed).
           luasocket: master_gc334468692+f083576d5c (already installed).
               mysql: 5.1.65_2_g6c6a3b8387 (already installed).
            luaexpat: master_g2e51c46583+8bb3c3661f (already installed).
         mysqlpython: master_gf144fc96d5+63a8112594 (already installed).
           luaxmlrpc: master_g55ddf7ee18+12ef1d036c (already installed).
            protobuf: master_g1ec0f6d55a+0a4801e32d (already installed).
          mysqlproxy: master_g769d47e3fb+5a834d7aac ok (14.4 sec).
             twisted: master_g3cdcb63100+6abb9c9f40 ok (8.0 sec).
               qserv: 0.5.1rc3_28_g2ba3abe916+95fcd65228 ERROR (0 sec).
*** error building product qserv.
======

The qserv error is not surprising, since there's only a table file
present there (I suspect it will need its own eupspkg.sh?).

Btw., I noticed you had a dummy qserv package in /personal/fjammes,
probably for testing purposes. The way I treated similar issues was to
just add a branch to a package (usually u/mjuric/eupspkg) on which all
eupspkg-related changes live. For consistency (and to avoid collisions
on REPOSITORY_PATH between the LSST/DMS/qserv and the other one), I made
a branch /u/mjuric/eupspkg in LSST/DMS/qserv, and copied the table file
there.

PS: I think we should jointly continue working on packages in:

	https://dev.lsstcorp.org/cgit/contrib/eupspkg

I've kept your version of mysqlpython and mysql; in retrospect, I think
it's not really worth the hassle splitting up mysql to -server and
-client packages.

I left out your changes to Python, however -- your changes allow 2.6,
which breaks the rest of the stack (e.g., users aren't warned on RHEL6
that they have the wrong version of Python). I think that if one *knows*
they won't need 2.7, they can use the manifest.remap mechanism to tell
EUPS not to install the 2.7 stub package. And this issue will most
likely go away entirely in a ~year or two, as RHEL7 will have 2.7 by
default (RHEL6 is basically the only major distribution still 2.6).

I'll now continue on to fixing the remaining eupspkg bugs...

- M.

> PS: I found some cycles to make a push of eupspkg, and I'm unifying your
> work on external packages for qserv with the work I did on external
> packages for the rest of the stack. I cloned them all to:
> 
> 	https://dev.lsstcorp.org/cgit/contrib/eupspkg
> 
> so both of us can write there. For now, I implemented the ./ups/eupspkg
> -> ./ups/eupspkg.sh change that I mentioned in the previous e-mail, and
> I'm going down the list fixing issues that have arisen because of that,
> trying to work my way up to building qserv.
> 
> Cheers,
> 


-- 
Mario Juric,
Data Mgmt. Project Scientist, Large Synoptic Survey Telescope
Web : http://research.majuric.org     Phone : +1 617 744 9003

########################################################################
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

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2018
February 2018
January 2018
December 2017
August 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use