Merge lp:~mterry/launchpad-buildd/prefer-install into lp:launchpad-buildd
Status: | Rejected |
---|---|
Rejected by: | Colin Watson |
Proposed branch: | lp:~mterry/launchpad-buildd/prefer-install |
Merge into: | lp:launchpad-buildd |
Diff against target: |
23 lines (+5/-5) 1 file modified
sbuild (+5/-5) |
To merge this branch: | bzr merge lp:~mterry/launchpad-buildd/prefer-install |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson (community) | Disapprove | ||
Richard Harding (community) | Approve | ||
Adam Conrad | Pending | ||
William Grant | Pending | ||
Review via email: mp+117318@code.launchpad.net |
Description of the change
This is an attempt to fix bug 1030893, which is causing some bogus dep-waits.
From looking at the sbuild fork code, what happens is that libsocket-perl gets marked as installable and perl gets marked as upgradeable. But the code prefers to upgrade over install, so it tries to upgrade the existing perl instead.
I'm curious in what situations would an upgrade be useful? Any package in the chroot should already be the latest version, since the first part of the build upgrades the packages in the chroot.
So with that logic in mind, this branch prefers installing new packages over upgrading existing ones.
Unmerged revisions
- 55. By Michael Terry
-
prefer installing new packages to upgrading existing chroot packages
This makes sense to me, but it seems like there would have been a reason for setting it up this way originally. So I'm going to ok, but ask William (lucky since he's got the most commits recently against launchpad-buildd) to give an ok as well.