Merge lp:~afrantzis/mir/fix-mircommon-debian-replaces into lp:mir

[Alexandros Frantzis]

debian: Update version numbers for libmircommon-dev and libmirplatform-dev Breaks,Replaces clauses

Our previous scheme used a specific 0.5.x version, but we have since moved to a newer 0.5.x version. Use (<< 0.6) to avoid such problems.

debian: Update version numbers for libmircommon-dev and libmirplatform-dev Breaks,Replaces clauses

Our previous scheme used a specific 0.5.x version, but we have since moved to a newer 0.5.x version. Use (<< 0.6) to avoid such problems.

[Daniel van Vugt (vanvugt)]

Looks right but needs some manual testing...

review: Approve

[Chris Halse Rogers (raof)]

LGTM.

review: Approve

[Daniel van Vugt (vanvugt)]

Hmm, isn't working. Perhaps we shouldn't have "Breaks", only "Replaces"...

$ sudo dpkg -i libmircommon-dev_0.6.0+14.10.20140811-0ubuntu1vv1_amd64.deb
dpkg: regarding libmircommon-dev_0.6.0+14.10.20140811-0ubuntu1vv1_amd64.deb containing libmircommon-dev:amd64:
 libmircommon-dev:amd64 breaks mircommon-dev (<< 0.6)
  mircommon-dev:amd64 (version 0.5.1+14.10.20140728-0ubuntu1) is present and installed.

dpkg: error processing archive libmircommon-dev_0.6.0+14.10.20140811-0ubuntu1vv1_amd64.deb (--install):
 installing libmircommon-dev:amd64 would break mircommon-dev:amd64, and
 deconfiguration is not permitted (--auto-deconfigure might help)
Errors were encountered while processing:
 libmircommon-dev_0.6.0+14.10.20140811-0ubuntu1vv1_amd64.deb

review: Needs Fixing

[Chris Halse Rogers (raof)]

No, you need to pass --auto-deconfigure.

In order to test such upgrades you really have to use apt; apt is where the smarts that handle Breaks/Replaces are.

[Daniel van Vugt (vanvugt)]

OK, it does work with:
sudo dpkg --auto-deconfigure -i libmircommon-dev_0.6.0+14.10.20140811-0ubuntu1vv1_amd64.deb libmircommon1_0.6.0+14.10.20140811-0ubuntu1vv1_amd64.deb

Although I'm not sure if apt does auto-deconfigure. The policy manual does say to "Breaks" and "Replaces"...
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

review: Approve

[Chris Halse Rogers (raof)]

apt will translate Breaks/Replaces into “remove mircommon-dev and install libmircommon-dev instead”. There's no way to really duplicate the apt upgrade procedure except for actually running apt that I know of.

[PS Jenkins bot (ps-jenkins)]

FAILED: Autolanding.
No commit message was specified in the merge proposal. Hit 'Add commit message' on the merge proposal web page or follow the link below. You can approve the merge proposal yourself to rerun.
https://code.launchpad.net/~afrantzis/mir/fix-mircommon-debian-replaces/+merge/230583/+edit-commit-message

review: Needs Fixing (continuous-integration)

[Iain Lane (laney)]

I uploaded this manually since the error was breaking dist-upgrades. You can tell the train to ignore that upload when merging this branch.

[PS Jenkins bot (ps-jenkins)]

PASSED: Continuous integration, rev:1838
http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-ci/2379/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-android-utopic-i386-build/1302
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-clang-utopic-amd64-build/1308
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-mediumtests-utopic-touch/1290
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-utopic-amd64-ci/901
        deb: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-utopic-amd64-ci/901/artifact/work/output/*zip*/output.zip
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-utopic-armhf-ci/902
        deb: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-utopic-armhf-ci/902/artifact/work/output/*zip*/output.zip
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-utopic-armhf/226
        deb: http://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-utopic-armhf/226/artifact/work/output/*zip*/output.zip
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/2380
    SUCCESS: http://s-jenkins.ubuntu-ci:8080/job/touch-flash-device/11371

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/mir-team-mir-development-branch-ci/2379/rebuild

review: Approve (continuous-integration)

[PS Jenkins bot (ps-jenkins)]

FAILED: Autolanding.
More details in the following jenkins job:
http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-autolanding/974/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-android-utopic-i386-build/1304
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-clang-utopic-amd64-build/1310
    None: http://jenkins.qa.ubuntu.com/job/mir-mediumtests-utopic-touch/1292/console
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-utopic-amd64-autolanding/358
        deb: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-utopic-amd64-autolanding/358/artifact/work/output/*zip*/output.zip
    None: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-utopic-armhf-autolanding/358/console
    FAILURE: http://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-utopic-armhf/228/console

review: Needs Fixing (continuous-integration)

[Alexandros Frantzis (afrantzis)]

Manually cancelled since it would fail anyway because of CI issues, retriggering.

[PS Jenkins bot (ps-jenkins)]

FAILED: Autolanding.
More details in the following jenkins job:
http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-autolanding/975/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-android-utopic-i386-build/1306
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-clang-utopic-amd64-build/1312
    FAILURE: http://jenkins.qa.ubuntu.com/job/mir-mediumtests-utopic-touch/1294/console
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-utopic-amd64-autolanding/359
        deb: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-utopic-amd64-autolanding/359/artifact/work/output/*zip*/output.zip
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-utopic-armhf-autolanding/359
        deb: http://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-utopic-armhf-autolanding/359/artifact/work/output/*zip*/output.zip
    SUCCESS: http://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-utopic-armhf/231
        deb: http://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-utopic-armhf/231/artifact/work/output/*zip*/output.zip
    FAILURE: http://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/2383/console
    SUCCESS: http://s-jenkins.ubuntu-ci:8080/job/touch-flash-device/11385

review: Needs Fixing (continuous-integration)

[Alexandros Frantzis (afrantzis)]

Sigh...

dpkg: error processing archive /var/cache/apt/archives/lxc-android-config_0.192_all.deb (--unpack):
 unable to make backup link of `./lib/udev/rules.d/70-android.rules' before installing new version: Invalid cross-device link

=== modified file 'debian/control'
--- debian/control	2014-08-07 08:43:25 +0000
+++ debian/control	2014-08-13 07:05:25 +0000
@@ -111,8 +111,8 @@
 Depends: libmircommon1 (= ${binary:Version}), 
          libprotobuf-dev (>= 2.4.1),
          ${misc:Depends},
-Breaks: mircommon-dev (<= 0.5.0+14.10.20140722-0ubuntu1)
-Replaces: mircommon-dev (<= 0.5.0+14.10.20140722-0ubuntu1)
+Breaks: mircommon-dev (<< 0.6)
+Replaces: mircommon-dev (<< 0.6)
 Description: Display server for Ubuntu - development headers
  Mir is a display server running on linux systems, with a focus on efficiency,
  robust operation and a well-defined driver model.
@@ -128,8 +128,8 @@
          libmircommon-dev,
          libboost-program-options-dev,
          ${misc:Depends},
-Breaks: libmirplatform (<=0.5.1+14.10.20140728-0ubuntu1)
-Replaces: libmirplatform (<=0.5.1+14.10.20140728-0ubuntu1)
+Breaks: libmirplatform (<< 0.6)
+Replaces: libmirplatform (<< 0.6)
 Description: Display server for Ubuntu - development headers
  Mir is a display server running on linux systems, with a focus on efficiency,
  robust operation and a well-defined driver model.