Re: ltmain.sh and configure

Peter O'Gorman wrote: I assume you mean the libtool-1.5 is not available on gnu.org since it was hacked in March. I believe it's reappearance is waiting on a libtool admin letting the relevant folks know the md5 checksum for that release. The checksum I have is 0e1844f25e2ad74c3715b5776d017545 i

Re: ltmain.sh and configure

On Thursday, September 11, 2003, at 12:38 AM, Gary V. Vaughan wrote: The checksum I have is 0e1844f25e2ad74c3715b5776d017545 in case anyone is interested :) I am interested :-) Rob rolled that release, and I don't have a tarball of 1.5 from which to generate the sum myself :-( What date did yo

Re: ltmain.sh and configure

On Wed, 10 Sep 2003, Gary V. Vaughan wrote: > Peter O'Gorman wrote: > > I assume you mean the libtool-1.5 is not available on gnu.org since it > > was hacked in March. I believe it's reappearance is waiting on a libtool > > admin letting the relevant folks know the md5 checksum for that release. >

RE: ltmain.sh and configure

Gary, While we're on the subject (sort of) Peter expressed some interest in becoming a co-maintainer. I think that is a good idea, what about you? Cheers, Robert -Original Message- From: Gary V. Vaughan [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 10, 2003 10:39 AM To: Peter O

RE: ltmain.sh and configure

On Wed, 10 Sep 2003, Boehne, Robert wrote: > While we're on the subject (sort of) Peter expressed some interest in becoming > a co-maintainer. I think that is a good idea, what about you? That is something I would like to see as well. Bob == Bob Friesenhahn [

Re: ltmain.sh and configure

Hi Rob, Peter, Boehne, Robert wrote: While we're on the subject (sort of) Peter expressed some interest in becoming a co-maintainer. I think that is a good idea, what about you? Absolutely! My attention to the libtool lists has been intermittent to say the least while I am working on m4... and

What is the status of the official libtool-1.5 tarball?

FSF rightly withdrew many of their tarballs to check for malicious code because a cracker owned them for many months. However, it has now been a month since that withdrawal and there is still no official libtool-1.5 tarball at http://ftp.gnu.org/gnu/libtool/. This affects many projects (like the

Re: ltmain.sh and configure

Bob Friesenhahn <[EMAIL PROTECTED]> writes: > I have a copy of libtool-1.5.tar.gz which was retrieved on April 15. > The MD5 checksum is also "0e1844f25e2ad74c3715b5776d017545". I have a copy dated April 14 with the same MD5 checksum. -- Russ Allbery ([EMAIL PROTECTED])

RE: What is the status of the official libtool-1.5 tarball?

Alan, Until last week, none of us had a libtool-1.5 tarball, but now that one has been located we can verify it for the FSF. I'm not sure when though. HTH, Robert -Original Message- From: Alan W. Irwin [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 02, 2003 11:54 AM To: [EMAIL PROT

Re: ltmain.sh and configure

Hello. Bob Friesenhahn wrote: > > On Wed, 10 Sep 2003, Gary V. Vaughan wrote: [snip] > > I am interested :-) Rob rolled that release, and I don't have a tarball > > of 1.5 from which to generate the sum myself :-( What date did you > > download it? Hopefully, very soon after the upload judging

Re: ltmain.sh and configure

On Thursday, September 11, 2003, at 2:11 AM, Gary V. Vaughan wrote: Boehne, Robert wrote: While we're on the subject (sort of) Peter expressed some interest in becoming a co-maintainer. I think that is a good idea, what about you? Absolutely! My attention to the libtool lists has been intermitte

Re: What is the status of the official libtool-1.5 tarball?

Boehne, Robert wrote: Until last week, none of us had a libtool-1.5 tarball, but now that one has been located we can verify it for the FSF. I'm not sure when though. Yeesh, I had no idea. The cygwin libtool-devel-1.5 source dist is widely mirrored, and: Contents of libtool-devel-1.5-1.tar.bz2

Re: ltmain.sh and configure

Gary V. Vaughan wrote: Peter O'Gorman wrote: I assume you mean the libtool-1.5 is not available on gnu.org since it was hacked in March. I believe it's reappearance is waiting on a libtool admin letting the relevant folks know the md5 checksum for that release. The checksum I have is 0e1844f2