We (most likely Jean-François, from the commit logs) cleverly post-process the
malformed .info files once the have been compiled. Even more cleverly,
SnowLeopard's makeinfo apparently gzips the generated files, so there's nothing
to find and patch anymore.
Should be easy enough to fix, thanks for the report.
Matthias
On Dec 31, 2009, at 0:38 , monipol wrote:
> On 30/12/2009, at 12:31, Wolfram Schroers wrote:
>> I have a problem installing the package ucblogo. The build works fine, but
>> when trying to "fink (re)install" it, I get an error message:
> (...)
>> Preparing to replace ucblogo 5.5-2 (using .../ucblogo_5.5-2_darwin-i386.deb)
>> ...
>> install-info(loops.info): no entry for file `loops'.
>> install-info(ucblogo.info): no entry for file `ucblogo'.
>> Unpacking replacement ucblogo ...
>> Setting up ucblogo (5.5-2) ...
>>
>> No `START-INFO-DIR-ENTRY' and no `This file documents'.
>> install-info(/sw/share/info/loops.info): unable to determine description for
>> `dir' entry - giving up
>> /sw/bin/dpkg: error processing ucblogo (--install):
>> subprocess post-installation script returned error exit status 1
>> Errors were encountered while processing:
>> ucblogo
>> ### execution of /sw/bin/dpkg-lockwait failed, exit code 1
>> Failed: can't install package ucblogo-5.5-2
>>
>> I do not know if this is related to the other issues I have been observing
>> or not.
>>
>> I am running Snow-Leopard 10.6.2, latest updates installed, latest version
>> of Fink and have the development branch activated.
>
> Hello, William. It looks like the documentation file provided by the
> developers of ucblogo (ucblogo.info) doesn't have the necessary
> INFO-DIR-SECTION and {START, END}-INFO-DIR-ENTRY fields. Since this
> particular package is maintained by Matthias Neeracher, so I'm CC'ing this
> reply to him. As package maintainers are ultimately responsible for their
> packages, we recommend users to send bug reports to both the maintainer and
> one of the {fink-users, fink-beginners} mailing lists.
>
> In order to find out who is the maintainer of a given package, run the fink
> info command, as in
>
> fink info ucblogo
>
> None <fink-devel...> is a particular case. It means that the package doesn't
> have a maintainer, so it usually suffices to send an e-mail to the fink-devel
> address alone.
>
>
> Cheers,
>
> --
> monipol
> http://finkers.wordpress.com
>
> Submitting a Fink bug report? Read this:
> http://www.finkproject.org/doc/netiquette/index.php
> http://finkers.wordpress.com/2009/06/03/bug-reports/
>
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
