Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 567978 - www-client/chromium beta tarball is larger than 1 GB
Summary: www-client/chromium beta tarball is larger than 1 GB
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Chromium Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-11 08:59 UTC by Oleh
Modified: 2016-01-23 21:14 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oleh 2015-12-11 08:59:03 UTC 
chromium-48.0.2564.23 release tarball is about 3-4 times bigger than usual. While it's not really a big problem for me, this case might be quite confusing for many others.

Reproducible: Always
Comment 1 Mike Gilbert gentoo-dev 2015-12-11 14:53:27 UTC 
It looks like the native_client directory exploded in size.

34 MB in 48.0.2564.10.
2.1 GB in 48.0.2564.23.

Most of that is toolchain binaries for nacl on different archs.
Comment 3 Jouni Kosonen 2015-12-13 17:17:23 UTC 
The ebuild has CHECKREQS_DISK_BUILD="5G" but it's already taking more than that to even unpack the tarball.

2.6G    chromium-48.0.2564.10
4.6G    chromium-48.0.2564.23
5.1G    chromium-48.0.2564.41
Comment 4 Mike Gilbert gentoo-dev 2015-12-13 21:18:21 UTC 
(In reply to Jouni Kosonen from comment #3)

I bumped it up to 30G/10G for debug/no-debug, respectively.
Comment 5 Jouni Kosonen 2016-01-13 21:39:40 UTC 
(In reply to Mike Gilbert from comment #4)
> I bumped it up to 30G/10G for debug/no-debug, respectively.

Thanks. Starting from 48.0.2564.79 and 49.0.2612.0 the limits could probably be relaxed back to 25G/5G again, as it looks like the the tarball blowup got resolved in the upstream issue.
Comment 6 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2016-01-23 21:14:37 UTC 
Yup, this is fixed now.