Am Donnerstag 14 Oktober 2010 schrieb Ehsan Esbati:
> OK. I tried that and it doesn't work.
> 
> My diagnosis is that the installation paths are not set correctly
> during the build process. Here's what happens on a fresh install of
> Maverick with all traces of hugin and its dependencies purged, even
> the folders:
> 
> When installing enblend:
> 
>      unable to create `/usr/local/share/man/man1/enblend.1.dpkg-
>      new' (while processing `./usr/local/share/man/man1/enblend.1'):
> No
>      such file or directory
> 
> In Maverick, there is no "man" folder under /usr/local/share, which I
> think causes the installation to fail.

But installing my supplied enblend was working. With 
/usr/local/share/man/man1/enfuse.1 and /usr/local/share/man/man1/enblend.1
So this conclusion does not apply.

> When installing libpano:
> 
>      unable to create `/usr/local/lib/pkgconfig/libpano13.pc.dpkg-
>      new' (while processing `./usr/local/lib/pkgconfig/libpano13.pc'):
> No
>      such file or directory
> 
> Again, in Maverick, there is no "pkgconfig" folder under /usr/local/
> lib, which I believe causes installation to fail.

The same argument is valid for libpano13. My supplied version _has_ 
/usr/local/lib/pkgconfig/libpano13.pc too.

> When installing hugin:
> 
>      unable to create `/usr/local/share/man/man1/nona.1.dpkg-
>      new' (while processing `./usr/local/share/man/man1/nona.1'): No
>      such file or directory
> 
> As with enblend, no "man" folder under /usr/local/share, resulting in
> failure. Even if you create this folder with "man1" under it, the
> installation fails at a later stage. For example:
> 
>     unable to create `/usr/local/share/applications/
> hugin.desktop.dpkg-
>     new' (while processing `./usr/local/share/applications/
> hugin.desktop'): No
>     such file or directory
> 
> Again, no "applications" folder under /usr/local/share in Maverick,
> installation fails.
> 
> I don't know what is responsible for setting the correct paths when
> the package is being built but my limited knowledge tells me that that
> is the culprit. I hope it helps.
> 
You could try to install with debug enabled to see more info.
        #sudo dpkg -D111 -i {your package}
as suggested on the same page 
(https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/574524)

        Kornel
-- 
Kornel Benko
[email protected]

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to