| View previous topic :: View next topic |
| Author |
Message |
mi_unixbird
Tux's lil' helper
Joined: 24 Jul 2015
Posts: 118
|
 Posted: Wed Aug 16, 2017 3:41 am Post subject: Some files in PKGDIR unrealistically large? |
 |
|
So I have FEATURES=buildpkg and most things it builds are the size one expects around 50 KiB but some are unrealistically large into severa mibibytes and when I rebuild them with quickpkg they become normal again—for example:
| Code: | —— — du -sBK /var/lib/portage/packages/app-text/poppler-data-0.4.8.tbz2
3424K /var/lib/portage/packages/app-text/poppler-data-0.4.8.tbz2
—— — sudo quickpkg app-text/poppler-data
* Building package for app-text/poppler-data-0.4.8 ... [ ok ]
* Packages now in '/var/lib/portage/packages':
* app-text/poppler-data-0.4.8: 13.4K
—— — du -sBK /var/lib/portage/packages/app-text/poppler-data-0.4.8.tbz2
16K /var/lib/portage/packages/app-text/poppler-data-0.4.8.tbz2 |
This 3424 KiB package was automatically generated by FEATURES=buildpkg, manually making a binary package of the exact same package that is currently installed shrinks it to 16 KiB.
Any suggestion to what might cause this?
It in fact seems like every package built with FEATURES=buildpkg is so large while quickpkg doesn't suffer from this problem. Does buildpkg include some extra stuff?
Nota bene: I use distcc to share load between my machines; not sure if that has anything to do with it.
_________________
execctl --path exec filectl --current-directory list |
|
| Back to top |
|
 |
Ant P.
Watchman
Joined: 18 Apr 2009
Posts: 6920
|
| Posted: Wed Aug 16, 2017 5:45 am Post subject: |
|
|
buildpkg snapshots the package contents before merging while quickpkg just takes what's on the live filesystem at the time. You might have run stuff like localepurge in the meantime. But that obviously doesn't account for the whole 3MB.
What's actually happening here is the .tbz2 files portage creates aren't plain tarballs - they glue the entire contents of /var/db/pkg/*whatever*/ metadata on the end of the file. All verbatim and uncompressed, so you might have a file contents list several hundred KB in size that just duplicates the tarball header. They're basically a crappy, de-facto proprietary knockoff of .deb files (which are just plain /usr/bin/ar files). |
|
| Back to top |
|
|
Josef.95
Advocate
Joined: 03 Sep 2007
Posts: 4553
Location: Germany
|
| Posted: Wed Aug 16, 2017 12:28 pm Post subject: |
|
|
Hm, I think quickpkg is currently probably broken :-/
Example: | Code: | du -sh /var/repos/packages/www-client/firefox-55.0.tbz2
52M /var/repos/packages/www-client/firefox-55.0.tbz2 |
I think these 52 MB is correct, and normal.
But now, I make via quickpkg a new binary package from the new firefox-55.0.1 version: | Code: | # quickpkg www-client/firefox
* www-client/firefox-55.0.1: package was emerged with USE=-bindist!
* www-client/firefox-55.0.1: it might not be legal to redistribute this.
* Building package for www-client/firefox-55.0.1 ... [ ok ]
* Packages now in '/var/repos/packages':
* www-client/firefox-55.0.1: 76.3K |
| Code: | du -sh /var/repos/packages/www-client/firefox-55.0.1.tbz2
80K /var/repos/packages/www-client/firefox-55.0.1.tbz2 |
I think ~80 K for a big firefox package is not correct.. :-/
Edit/: Yes, looks like quickpkg from =sys-apps/portage-2.3.7 is broken :-/
After downgrade to (current stable) =sys-apps/portage-2.3.6 it works fine --> | Code: | # quickpkg www-client/firefox
* www-client/firefox-55.0.1: package was emerged with USE=-bindist!
* www-client/firefox-55.0.1: it might not be legal to redistribute this.
* Building package for www-client/firefox-55.0.1 ... [ ok ]
* Packages now in '/var/repos/packages':
* www-client/firefox-55.0.1: 51.9M |
|
|
| Back to top |
|
|
mi_unixbird
Tux's lil' helper
Joined: 24 Jul 2015
Posts: 118
|
| Posted: Wed Aug 16, 2017 12:54 pm Post subject: |
|
|
So what's the broken part and what is it omitting exactly?
I only very recently started using buildpkg after finding out how extremely small they were but that's apparently just a bug and they don't work properly?
Edit, ideed, atter downgrading:
| Quote: | —— — sudo quickpkg x11-wm/fluxbox
* Building package for x11-wm/fluxbox-1.3.7-r4 ... [ ok ]
* Excluded config: '/etc/X11/Sessions/fluxbox'
* Packages now in '/var/lib/portage/packages':
* x11-wm/fluxbox-1.3.7-r4: 724K
* Excluded config files: 1
* See --help if you would like to include config files.
—— — du -sBK /var/lib/portage/packages/x11-wm/fluxbox-1.3.7-r4.tbz2
728K /var/lib/portage/packages/x11-wm/fluxbox-1.3.7-r4.tbz2
—— — sudo quickpkg poppler-data
* Building package for app-text/poppler-data-0.4.8 ... [ ok ]
* Packages now in '/var/lib/portage/packages':
* app-text/poppler-data-0.4.8: 3.4M
—— — du -sBK /var/lib/portage/packages/app-text/poppler-data-0.4.8.tbz2
3436K /var/lib/portage/packages/app-text/poppler-data-0.4.8.tbz2 |
Which are indeed the same sizes of buidpkg. So what was it omitting?
_________________
execctl --path exec filectl --current-directory list |
|
| Back to top |
|
|
Josef.95
Advocate
Joined: 03 Sep 2007
Posts: 4553
Location: Germany
|
| Posted: Wed Aug 16, 2017 2:35 pm Post subject: |
|
|
| It is now as Bug 628010 reported. |
|
| Back to top |
|
|
mi_unixbird
Tux's lil' helper
Joined: 24 Jul 2015
Posts: 118
|
| Posted: Thu Aug 17, 2017 2:45 am Post subject: |
|
|
Seems lie portage rolled out an update just yet that fixed this.
_________________
execctl --path exec filectl --current-directory list |
|
| Back to top |
|
|
|
Portage & Programming
