Merge lp:~ubuntu-branches/ubuntu/precise/libdatrie/precise-201201030357 into lp:ubuntu/precise/libdatrie
Status: | Needs review |
---|---|
Proposed branch: | lp:~ubuntu-branches/ubuntu/precise/libdatrie/precise-201201030357 |
Merge into: | lp:ubuntu/precise/libdatrie |
Diff against target: |
427 lines (+392/-0) (has conflicts) 3 files modified
debian/changelog (+265/-0) debian/control (+79/-0) debian/copyright (+48/-0) Text conflict in debian/changelog Text conflict in debian/control Text conflict in debian/copyright |
To merge this branch: | bzr merge lp:~ubuntu-branches/ubuntu/precise/libdatrie/precise-201201030357 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ubuntu branches | Pending | ||
Review via email: mp+87315@code.launchpad.net |
Description of the change
The package importer has detected a possible inconsistency between the package history in the archive and the history in bzr. As the archive is authoritative the importer has made lp:ubuntu/precise/libdatrie reflect what is in the archive and the old bzr branch has been pushed to lp:~ubuntu-branches/ubuntu/precise/libdatrie/precise-201201030357. 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)
Unmerged revisions
- 12. By Theppitak Karoonboonyanan <email address hidden>
-
* debian/copyright:
- Use non-forwarding format URL. Bump to revision 202.
- Upstream license is actually LGPL-2.1, not 2.0.
- Add extended text for LGPL-2.1 and GPL-2.
* debian/rules:
- Add back upstream 'make distclean' that was lost in 0.2.4-3, so it
builds twice in a row again. - 11. By Theppitak Karoonboonyanan <email address hidden>
-
* New upstream release.
* Use hardening build flags:
- B-Dep on dpkg-dev (>= 0.16.1~) for dpkg-buildflags
- Obtain build flags from dpkg-buildflags
- Drop old CFLAGS & LDFLAGS, as now overridden by dpkg-buildflags