Hi David,
We urgently need non-DPM sites to upgrade to xrootd 4.1 as it includes an important fix of memory leak in the xrootd client (for xrootd proxy). I wonder under this situation, do you mind that the WLCG repo makes the new N2N rpm and VOMSXRD rpm available? They depend on xrootd 4.1 so if xrootd 4.1 is not available from EPEL, DPM sites won't automatically get the new N2N and VOMSXRD rpms. At most, they get complains in yum update that the dependency of new n2n and vomsxrd rpms can not be satisfied, which they can just ignore.
We have thought of your other suggestions about packing .so and -4.so in one rpm and make them depend on only xrootd 3.x. We actually made it work a long time ago before we adapted the current two rpms (.rpm and -compat.rpm) mechanism. We would prefer to avoid going back and forth in between these two packaging methods which will likely confuse the sites.
Any thoughts?
regards,
--
Wei Yang | [log in to unmask] | 650-926-3338(O)
> On Jan 26, 2015, at 3:39 PM, Lukasz Janyst <[log in to unmask]> wrote:
>
> FYI. Lukasz
> ________________________________________
> From: David Smith
> Sent: 26 January 2015 17:57
> To: Mattias Ellert
> Cc: Lukasz Janyst
> Subject: Re: xrootd 4 & xrootd 3 compat packages and dpm
>
> On 06 Jan 2015, at 09:55, David Smith <[log in to unmask]> wrote:
> […]
>> The DPM team is still trying to prepare so that sites will be able to upgrade or install after the move - but it would be better for us to have some more time to do this. Is it possible for you to further delay moving the xrootd 4 and xrootd 3 compat packages to stable until the end of January (we can let you know if we are ready before that time)?
>
> Hello Mattias,
>
> Unfortunately we’re still in the process of going over the instructions for upgrade to xrootd 4 with our preproduction sites. Furthermore our dpm-xrootd component will not finish its two week period of testing in epel-testing until 5 February.
>
> Would it be possible for you to, once again, further delay the move of xrootd 4 & xrootd 3 compat packages from epel-testing to stable until we’ve finished? We expect this to be by the middle of February but I think it would be best if we could wait until we can confirm all the test sites are successful.
>
> Yours,
> David
>
> --
> -------------------------------------------------------------------------
> David Smith e-mail: [log in to unmask] tel: +41 22 76 70394
> Address: D. Smith, CERN G06900, Bat 28 R-026, 1211 Geneva 23, Switzerland
> -------------------------------------------------------------------------
>
> ########################################################################
> Use REPLY-ALL to reply to list
>
> To unsubscribe from the XROOTD-DEV list, click the following link:
> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
|