Merge lp:~ajmitch/launchpad/fakesyncs into lp:launchpad
Status: | Rejected |
---|---|
Rejected by: | Māris Fogels |
Proposed branch: | lp:~ajmitch/launchpad/fakesyncs |
Merge into: | lp:launchpad |
Diff against target: |
30 lines (+14/-6) 1 file modified
scripts/ftpmaster-tools/sync-source.py (+14/-6) |
To merge this branch: | bzr merge lp:~ajmitch/launchpad/fakesyncs |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Māris Fogels (community) | Needs Information | ||
Julian Edwards | Pending | ||
Review via email: mp+27615@code.launchpad.net |
Description of the change
Summary:
Packages that have been uploaded to Ubuntu & then subsequently uploaded to Debian with a different orig.tar.gz cannot be synced, and a convention is to 'fakesync' these packages with a -XbuildY or XubuntuY revision. Using the former means that sync-source.py will fail at importing them, and the latter means that they will not be automatically synced when a new upstream version is released.
Proposed fix:
This branch adds a special case for packages with a version string containing 'fakesync', such that it will not sync the package if the Ubuntu & Debian upstream versions are the same, and the version contains fakesync
Unmerged revisions
- 10992. By Andrew Mitchell
-
Refuse to try & sync packages with fakesync in the version when they have the same upstream version
Hi Andrew,
The branch structure is really difficult to follow. Before landing this I think you have to make absolutely sure that no execution paths have changed. The fact that these scripts often don't have tests does not help the matter: we have to lean even more on code inspection.
Did you have a pre-implementation call with anyone? And are there any tests that can be run to verify the change?
Maris