 |
 |
Hi Lukasz, I am slightly puzzled by the packages not being pushed to EPEL, or did I misunderstand? Do you know what a sysadmin who depends on EPEL should do to upgrade? Of course this involves us too. How would you rate the upgrade? I mean things like mandatory/good to have/cosmetic/avoid ? Thank you! Fabrizio On 04/26/2013 09:18 PM, Lukasz Janyst wrote: > Dear All, > > the XRootD 3.3.2 bugfix release has been tagged. You can download the source here: > > http://xrootd.org/download/v3.3.2/xrootd-3.3.2.tar.gz > > and the RPMs here: > > http://xrootd.cern.ch/sw/releases/3.3.2/rpms/ > > Please note that the RPMs exceptionally have not been pushed to the yum repositories, due to some deployments issues related > to the package names conflicting with EPEL. > > The release notes are available here: > > https://github.com/xrootd/xrootd/blob/v3.3.2/docs/ReleaseNotes.txt > > Please note that we now also provide experimental python bindings: > > RPMs: http://xrootd.cern.ch/sw/releases/python/0.1.0/ > Documentation: http://xrootd.org/doc/python/xrootd-python-0.1.0/ > > Best regards, > Lukasz > > ######################################################################## > 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-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1