Merge lp:~ajmitch/launchpad/fakesyncs into lp:launchpad
| Status: | Rejected |
|---|---|
| Rejected by: | Māris Fogels on 2010-06-16 |
| 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) | 2010-06-15 | Needs Information on 2010-06-15 | |
| Julian Edwards | 2010-06-15 | Pending | |
|
Review via email:
|
|||
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
| Andrew Mitchell (ajmitch) wrote : | # |
Having read a thread which I've dug up about this subject ( http://
Unmerged revisions
- 10992. By Andrew Mitchell on 2010-06-10
-
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