Merge lp://staging/~ubuntu-branches/ubuntu/oneiric/gcompris/oneiric-201108242027 into lp://staging/ubuntu/oneiric/gcompris
| Status: | Needs review |
|---|---|
| Proposed branch: | lp://staging/~ubuntu-branches/ubuntu/oneiric/gcompris/oneiric-201108242027 |
| Merge into: | lp://staging/ubuntu/oneiric/gcompris |
| Diff against target: |
136 lines (+80/-2) (has conflicts) 7 files modified
debian/gcompris-sound-af.files (+1/-0) debian/gcompris-sound-sl.files (+1/-0) debian/patches/90-submarine-set-but-unused-variables.patch (+37/-0) debian/patches/91-dont-translate-nonexisting-files.patch (+24/-0) debian/patches/series (+2/-0) debian/source/format (+1/-0) src/submarine-activity/submarine.c (+14/-2) Conflict adding file debian/gcompris-sound-af.files. Moved existing file to debian/gcompris-sound-af.files.moved. Conflict adding file debian/gcompris-sound-sl.files. Moved existing file to debian/gcompris-sound-sl.files.moved. Conflict adding file debian/patches. Moved existing file to debian/patches.moved. Conflict adding file debian/source. Moved existing file to debian/source.moved. Text conflict in src/submarine-activity/submarine.c |
| To merge this branch: | bzr merge lp://staging/~ubuntu-branches/ubuntu/oneiric/gcompris/oneiric-201108242027 |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Ubuntu branches | Pending | ||
|
Review via email:
|
|||
Description of the change
The package importer has detected a possible inconsistency between the package history in the archve and the history in bzr. As the archive is authoritative the importer has made lp:ubuntu/oneiric/gcompris reflect what is in the archive and the old bzr branch has been pushed to lp:~ubuntu-branches/ubuntu/oneiric/gcompris/oneiric-201108242027. This merge proposal was created so that an Ubuntu developer can review the situations and perform a merge/upload if necessary. There are three typical cases where this can happen.
1. Where someone pushes a change to bzr and someone else uploads the package without that change. This is the reason that this check is done by the importer. If this appears to be the case then a merge/upload should be done if the changes that were in bzr are still desirable.
2. The importer incorrectly detected the above situation when someone made a change in bzr and then uploaded it.
3. The importer incorrectly detected the above situation when someone just uploaded a package and didn't touch bzr.
If this case doesn't appear to be the first situation then set the status of the merge proposal to "Rejected" and help avoid the problem in future by filing a bug at https:/
(this is an automatically generated message)
