 |
 |
Hi Doug, We have no solution for the automatic yum updates, which is why I dislike them. It is likely we will have future releases that have issues. If at all possible, sites should make the yum update semi-automatic with it not happening until someone gives the manual go-ahead. Andy On Sun, 13 May 2012, Doug Benjamin wrote: > Hi Andy, > > I am sure that we are going to fall into the trap that some sites will automatically update the xrootd library due to the automatic > yum update and then get jammed up. The cron job that updates many rpm's does not automatically exclude xrootd nor does the > rpm that installs xrootd make xrootd not to be auto installed. In scientific linux the yum update cron is automatically installed. > > Actually I do not believe the real problem is the "we didn't make it clear enough that 3.2.1 didn't include the FRM fix.". The fact > that frm is broken is the problem. > > Doug > > On May 13, 2012, at 3:01 PM, Andrew Hanushevsky wrote: > >> Hi Doug, >> >> The reason is that the release manager is out on vacation. While the FRM bug is severe it does not affect everyone as the double-free problem did. >> It made 3.2.0 unuseable and we needed to fix that ASAP. Also, the solution for real-time FRM sites is to stay at 3.1.1 or earlier to avoid both issues. That's a reasonable compromise given our time constraints. Our real problem was that we didn't make it clear enough that 3.2.1 didn't include the FRM fix. >> >> Andy >> >> On Sun, 13 May 2012, Doug Benjamin wrote: >> >>> Wei, >>> >>> I understand that bug fixed in 3.2.1 was extremely severe. So I am not commenting on the need to >>> push out 3.2.1 as soon as possible. I am commenting on Andy's statement that the frm fix will wait >>> until next month. The frm bug in 3.2x is a significant bug also. >>> >>> Doug >>> On May 13, 2012, at 1:49 PM, Yang, Wei wrote: >>> >>>> Hi Doug, the things that needed to go into 3.2.1 couldn't wait ... >>>> >>>> regards, >>>> Wei Yang | [log in to unmask] | 650-926-3338(O) >>>> >>>> >>>> >>>> >>>> On May 13, 2012, at 6:17 AM, Doug Benjamin wrote: >>>> >>>>> Hi, >>>>> >>>>> The frm bug is very significant. There are other places besides NYU to use the >>>>> frm between xrootd pools. Why is the fix waiting until next month? Why isn't >>>>> the fix considered important enough for 3.2.2? >>>>> >>>>> Also what is the situation with xrdcp in extreme copy was the problem with linux threads >>>>> fixed? I never got a new routine to test. >>>>> >>>>> Cheers, >>>>> >>>>> Doug >>>>> >>>> >>>> >>>> ######################################################################## >>>> 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 >>>> <winmail.dat> >>> >>> >> >> ######################################################################## >> 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