Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 554188 - portage should not rebuild binary deps when merging binary packages
Summary: portage should not rebuild binary deps when merging binary packages
Status: RESOLVED INVALID
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Binary packages support (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-07 23:42 UTC by William L. Thomson Jr.
Modified: 2016-05-26 17:43 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description William L. Thomson Jr. 2015-07-07 23:42:59 UTC
Hopefully not a duplicate, I did not see anything like it when I searched. I want to prevent this;

The following packages are causing rebuilds:

  (dev-lang/perl-5.20.2::gentoo, ebuild scheduled for merge) causes rebuilds for:
    (dev-perl/Locale-gettext-1.50.0-r1::gentoo, binary scheduled for merge)
    (perl-core/Data-Dumper-2.154.0::gentoo, binary scheduled for merge)
    (dev-perl/XML-Parser-2.410.0-r2::gentoo, binary scheduled for merge)

There is no need for perl to be rebuilt. I am trying to update a system with pre-built binaries. All perl modules were already built against that version of perl that I am merging. Thus the perl binaries were already merged using that version of perl. Portage/emerge thinks it needs to rebuild perl, when it does not. So instead of installing the pre-made perl binary. It is re-compiling perl needlessly. Which is what I am reporting, and would like to see the behavior modified. 

Thankfully it just seems to be perl, but I assume this same thing would happen for any package really. If dependencies caused rebuilds, but the deps were already built against the version they would rebuild against.
Comment 1 Jason Zaman gentoo-dev 2015-07-12 13:08:17 UTC
They are not needless tho, anything that requires perl has to be rebuilt after a perl upgrade. If you are using binary packages then the binhost will have to rebuild them and the other machines can just re-install the packages.
Comment 2 William L. Thomson Jr. 2015-07-12 14:33:11 UTC
The binhost had rebuilt them already that is my point. Its trying to be rebuilt again, when it was already been re-built against the version perl its being re-built again against for the 2nd time on the binclient. The binaries were prepped on the binhost, thus just need to be installed on the binclient, no deps need to be rebuild as that was already done on the binhost.
Comment 3 Zac Medico gentoo-dev 2015-07-12 18:10:51 UTC
(In reply to William L. Thomson Jr. from comment #0)
> The following packages are causing rebuilds:
> 
>   (dev-lang/perl-5.20.2::gentoo, ebuild scheduled for merge) causes rebuilds
> for:
>     (dev-perl/Locale-gettext-1.50.0-r1::gentoo, binary scheduled for merge)
>     (perl-core/Data-Dumper-2.154.0::gentoo, binary scheduled for merge)
>     (dev-perl/XML-Parser-2.410.0-r2::gentoo, binary scheduled for merge)
> 
> There is no need for perl to be rebuilt.

You can try using --binpkg-respect-use=n and --binpkg-changed-deps=n. That will make it re-use binary packages whenever possible. Alternatively, the --usepkgonly/--getbinpkgonly options will give similar results.
Comment 4 William L. Thomson Jr. 2015-07-12 18:19:50 UTC
Ok thanks, will try those next I run into this. All systems were updated so I do not have any to replicate this with atm.
Comment 5 William L. Thomson Jr. 2016-05-26 17:43:37 UTC
I think this might be a false report, rebuilds are triggered but uses binary packages it does not rebuild.