On 2008-04-17 12:28 +0200, Mathieu Malaterre wrote: > Hi Sven, > > Thanks a bunch for tracking the issue down ! I am making some > progress. See the new debian package (still not quite there yet): > > http://gdcm.sourceforge.net/thingies/debpackage-0.0.2-Linux-x86_64.deb
Thanks. If possible, try to create “Architecture: all” packages so that I can (try to) install them without using the “--force-architecture” switch. > After installation I am getting: > > $ dpkg -L debpackage > /tmp > /tmp/very > /tmp/very/long > /tmp/very/long/pathname > /tmp/very/long/pathname/foobar > /tmp/very/long/pathname/foobar/hello_world > /tmp/very/long/pathname/foobar/hello_world/toreproduceabugindpkg > /tmp/very/long/pathname/foobar/hello_world/toreproduceabugindpkg/pleaseconsider > /tmp/very/long/pathname/foobar/hello_world/toreproduceabugindpkg/pleaseconsider/123 > /tmp/very/long/pathname/foobar/hello_world/toreproduceabugindpkg/pleaseconsider/123/install_me1.txt > /tmp/very/long/pathname/foobar/hello_world/toreproduceabugindpkg/pleaseconsider/123/do_not_install_me.txt,.+ > /tmp/very/long/pathname/foobar/hello_world/toreproduceabugindpkg/pleaseconsider/123/install_me112.txtnsq > /tmp/very/long/pathname/foobar/hello_world/toreproduceabugindpkg/pleaseconsider/123/install_me11.txt > /tmp/very/long/pathname/foobar/hello_world/toreproduceabugindpkg/pleaseconsider/123/install_m.txt > /tmp/very/long/pathname/foobar/hello_world/toreproduceabugindpkg/pleaseconsider/123/install_me1123.txt > /tmp/very/long/pathname/foobar/hello_world/toreproduceabugindpkg/pleaseconsider/123/install_me.txt I was not able to install the package at all, here is what I got with dpkg 1.14.18 on i386: ,---- |# dpkg --force-architecture -i debpackage-0.0.2-Linux-x86_64.deb | dpkg - warning, overriding problem because --force enabled: | package architecture (amd64) does not match system (i386) | (Reading database ... 134335 files and directories currently installed.) | Unpacking debpackage (from debpackage-0.0.2-Linux-x86_64.deb) ... | dpkg: error processing debpackage-0.0.2-Linux-x86_64.deb (--install): | unable to create `./tmp/very/long/pathname/foobar/hello_world/toreproduceabugindpkg/pleaseconsider/123/install_me112.txt/man/mq': No such file or directory | Errors were encountered while processing: | debpackage-0.0.2-Linux-x86_64.deb `---- Apparently dpkg puts random junk at the end of the filenames, and in my case that junk included a slash. So dpkg cannot handle this type of archive either. While file reports your data.tar as “POSIX tar archive (GNU)” it is probably rather a USTAR archive, since I found the string “ustar” between the filenames, but no “LONGLINK” entry that is characteristic of GNU archives with long filenames. (No, I'm not an expert on tar archive formats -- it was only yesterday evening that I became aware of their differences!) > You can clearly see that there are some garbage at the end of the > filepath, while this is not reported by dpkg -c: dpkg -c (aka dpkg-deb -c) uses tar to list the contents, while dpkg uses its own implementation when installing packages, that explains the discrepancy. Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
