Summary: | www-client/google-chrome fails to unpack | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Mike Gilbert <floppym> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chromium |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 384147 | ||
Bug Blocks: | |||
Attachments: | Build log |
Description
Diego Elio Pettenò (RETIRED)
2011-09-15 06:43:45 UTC
Yeah, deb2targz is crap. It doesn't work with lzma compressed data.tar files. deb2targz: converting 'google-chrome-beta_14.0.835.162-r100637_i386.deb' ... deb2targz: skipping section 'debian-binary' deb2targz: skipping section 'control.tar.gz' deb2targz: skipping section 'data.tar.lzma' mv: cannot stat `google-chrome-beta_14.0.835.162-r100637_i386.tar.gz': No such file or directory I changed the blocker to DEPEND="!!app-arch/deb2targz". Thanks for the report. Actually, I see that a patch was recently added to deb2targz to support this. *deb2targz-1-r1 (30 Aug 2011) 30 Aug 2011; Tony Vroon <chainsaw@gentoo.org> +files/deb2targz-lzma-support.patch, +deb2targz-1-r1.ebuild: Support for LZMA as written by Oschtan in bug #357703. Ported to EAPI 4. Do you happen to have have the old version (-r0) installed? It's the tinderbox, I can't say for certain now tbh. But the automagic use is bad, just disable it in src_unpack if it's not what you want to use... Good idea. It now calls ar directly, and I removed the blocker. |