Summary: | unpacking of kbd-1.12 fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Federico Fenara <federicofenara> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jonathanu |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Repackaged kbd-1.12.tar.gz so that it correctly extracts on JFS filesystems.
Changed digest file |
Description
Federico Fenara
2004-02-25 02:50:22 UTC
please delete the file and reemerge again I've already done it with the same result. servizievole root # rm /usr/portage/distfiles/kbd-1.12.tar.gz servizievole root # emerge kbd Calculating dependencies ...done! >>> emerge (1 of 1) sys-apps/kbd-1.12-r2 to / >>> Downloading http://gentoo.oregonstate.edu/distfiles/kbd-1.12.tar.gz --08:51:23-- http://gentoo.oregonstate.edu/distfiles/kbd-1.12.tar.gz => `/usr/portage/distfiles/kbd-1.12.tar.gz' Resolving gentoo.oregonstate.edu... 128.193.0.3 Connecting to gentoo.oregonstate.edu[128.193.0.3]:80... connected. HTTP request sent, awaiting response... 200 OK Length: 884,827 [application/x-gzip] 100%[====================================>] 884,827 117.37K/s ETA 00:00 08:51:30 (132.32 KB/s) - `/usr/portage/distfiles/kbd-1.12.tar.gz' saved [884827/884827] >>> md5 src_uri ;-) kbd-1.12.tar.gz >>> Unpacking source... >>> Unpacking kbd-1.12.tar.gz to /var/tmp/portage/kbd-1.12-r2/work tar: ./kbd-1.12/doc/utf/\342\231\252\342\231\254: Cannot open: Invalid argument tar: Error exit delayed from previous errors !!! ERROR: sys-apps/kbd-1.12-r2 failed. !!! Function unpack, Line 332, Exitcode 2 !!! failure unpacking kbd-1.12.tar.gz servizievole root # This bug comes from the UTF-8 in the tar.gz file being unusable in conjunction with the JFS drivers from Knoppix or the 1.4 release LiveCD. Workaround: 1. Unpack kbd-1.12.tar.gz, ignoring the error. 2. Repack kbd-1.12.tar.gz, moving this file to /usr/portage/distfiles 3. Recompute MD5-sums for ebuild Real patch: Make kbd-1.12-r2 unpack itself with ignoring errors caused by wrong UTF-8 characters in filenames. I've seen this error occur only when the filesystem where the files are being unpacked on is JFS, and with kernels = 2.4.x Created attachment 26463 [details]
Repackaged kbd-1.12.tar.gz so that it correctly extracts on JFS filesystems.
Created attachment 26466 [details]
Changed digest file
Changed digest file, replace the one in /usr/portage/sys-apps/kbd/files with
this one before trying to emerge it, and you should be fine without recomputing
the MD5-sum of the ebuild. In case you don't replace it, and don't recalculate
the MD5-sum, you're in for trouble, as it will try to download the original
file, padding this one with the extra data. (seems the original was very badly
compressed)
I've just found the way to make it work upgrading to kernel 2.6.3-rc2. Thanks for the support. :) *** Bug 45942 has been marked as a duplicate of this bug. *** How is this a duplicate for kdb-1.08? 1.12 doesn't help those of us installing a new system. Some of us don't know the ebuild system well enough to use this as a work-around, can more detailed steps be given, if there's a way to do an emerge system using this version instead of 1.08-r5? OR can a re-packaged 1.08 tar.gz be posted as well? I created my own work around/kludge: First, untar the distfile (kbd-1.08.tar.gz) somewhere sane (/tmp is a good place to start), and it will ignore the UTF-8 filename. Then re-package: tar -cvzf kbd-1.08.tar.gz ./kbd-1.08 back up the digest file and the original distfile copy the new package to the distfiles directory in /usr/portage md5sum kdb-1.08.tar.gz Edit the digest file with the appropriate md5 checksum and file size difference. emerge kdb-1.08-r5.ebuild And then retry your emerge system / whatever you were doing. This really doesn't *fix* anything, all it does is remove a doc file from the package. I solved this problem by remounting the filesystem with "iocharset=utf8" . After that I was able to continue and finish the installation. ok, I think I've fixed this by manually unpacking in the ebuild instead of using the portage unpack function. Please re-open if it's still broken for you. |