Mail Archives: cygwin/2009/02/07/14:29:16
On Sat, Feb 07, 2009 at 02:20:55PM -0500, Larry Hall (Cygwin) wrote:
> wynfield AT gmail DOT com wrote:
>> Re:
>>> Larry Hall (Cygwin) <reply-to-list-only-lh AT cygwin DOT com> wrote:
>>> On 02/05/2009, Wynfield Henman wrote:
>>>> Though I am building a different package, I have the same problem as
>>>> mentioned below. The libtool package downloaded is 46 bytes
>>>> (effectively null) and get stashed into the _obsolete folder without
>>>> ever getting installed.
>>> <http://cygwin.com/cgi-bin2/package-grep.cgi?grep=usr%2Fbin%2Flibtoolize>
>>>
>>> Don't install obselete packages unless you really know what you're doing.
>>>
>>> Given the above, why doesn't just installing the 'libtool' package get
>>> you what you need?
>>>
>> That is just the problem it doesn't get what is needed, but only shows the
>> obsolete (from what you say) versions as the newest. I even tried
>> experimental to try to find newer libtool version, but none show up.
>> Version1.5b or whatever was presented as the newest version by setup.
>> There was no intentional _obsolete gets on my part.
>> I solved the problem by hand getting the new vesion and untarring it in
>> the appropriate location, but that shouldn't have to be done. I believe it
>> is a setup related problem, either hints or ini file data.
>
> It may have been related to a problem with 'upset' late last week. I
> just tried it now using ftp://mirrors.xmission.com/cygwin and
> http://sources-redhat.mirror.redwire.net/cygwin and had no trouble
> getting version 2.2.6.a-1. After the install, I have
> '/usr/bin/libtoolize'.
> If you continue to see problems with 'setup.exe', report back with the
> process you went through and the problems you're seeing.
There are continued problems with setup.ini after last weeks problems.
I made some changes to tighten up the way that setup.ini was generated
which caused package directories to be sorted differently. That
uncovered a problem with libtool, apr1, and aprutil1. There were
duplicate packages in the cygwin "repo" and, after my changes, the
obsolete duplicate packages were given precedence over their newer
counterparts.
I've removed the offending packages and added error checking to upset
to catch this kind of thing in the future.
So, now, as last week, the thing to do is wait for the mirrors to catch
up and cross your fingers that this is the last package problem we'll see
for a while.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -