SCIENTIFIC-LINUX-DEVEL Archives

February 2012

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steven Haigh <[log in to unmask]>
Reply To:
Steven Haigh <[log in to unmask]>
Date:
Thu, 16 Feb 2012 08:51:26 +1100
Content-Type:
multipart/signed
Parts/Attachments:
text/plain (2074 bytes) , smime.p7s (4 kB)
On 16/02/2012 4:23 AM, Pat Riehecky wrote:
> We are going to stick with upstream on this one. The reasoning is
> somewhat complex. We have a few concerns before we ever consider forking
> off.

I thought this would be the case - and it is really hard as this can be 
considered a major bug - however I fully agree with the decision - as it 
is more likely to cause long term pain if a 'rush-to-fix' is done.

> Is upstream going to fix?
> How likely are the uninformed end users to blame us for things not working?
> How entrenched is this package?
> Does this effect our compatibility with TUV?
>
> With upstream having the patch on Q/A and promising a fix with 6.3, we
> know they are going to fix it. Both Connie and I expect they will
> release the fix sooner than that.

I agree, from talking to the TUV guys involved off-BZ, I believe it will 
be fixed sooner. I have been provided a copy of the patch being used by 
TUV to address the issue and am currently building i686 & x86_64 
packages for testing the fix and shall report those back to TUV on the 
degree of success for this. I shall also post the results here for 
completeness and the archives for future reference.

> And because it is so invasive people may blame it for unrelated problems.

I figure it will more cause bugs to be lodged against other projects. I 
was *very* close to blaming mod_perl for this one until I did a much 
deeper analysis of the issue!

> This package is listed by TUV as _THE_ core library, changes have a very
> large impact.

Without a doubt! This is also why a bug such as this is a major one! It 
is also a great reason to tread very lightly. I don't mind testing on my 
insignificant systems and if it dies, well thats another data point - 
but $diety help us if something goes wrong affecting glibc in a public 
repo!!!

> Changing glibc clearly changes our compatibility with TUV.
>
> Since a fix is coming, we are going to wait for it.

A wise and understandable move! :)

--
Steven Haigh

Email: [log in to unmask]
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299




ATOM RSS1 RSS2