Merge lp:~didrocks/platform-api/changelog-cleanup into lp:platform-api

[Didier Roche-Tolomelli]

minor cosmetic cleanups as we detect the archs we can't build for in daily release now

minor cosmetic cleanups as we detect the archs we can't build for in daily release now

[PS Jenkins bot (ps-jenkins)]

PASSED: Continuous integration, rev:75
http://jenkins.qa.ubuntu.com/job/platform-api-ci/53/
Executed test runs:
    SUCCESS: http://jenkins.qa.ubuntu.com/job/platform-api-saucy-amd64-ci/23
    SUCCESS: http://jenkins.qa.ubuntu.com/job/platform-api-saucy-armhf-ci/23
        deb: http://jenkins.qa.ubuntu.com/job/platform-api-saucy-armhf-ci/23/artifact/work/output/*zip*/output.zip
    SUCCESS: http://jenkins.qa.ubuntu.com/job/platform-api-saucy-i386-ci/23

Click here to trigger a rebuild:
http://s-jenkins:8080/job/platform-api-ci/53/rebuild

review: Approve (continuous-integration)

[Michael Terry (mterry)]

From IRC:
<mterry> didrocks, what do you mean you detect the arches we can't build for?
<mterry> didrocks, but we don't change the control file, so we are still uploading to archive and causing dep-wait packages, right?
<didrocks> mterry: detect the arch -> yeah, we don't live in stone age! :)
<didrocks> mterry: basically I'm checking if we build-dep for an unimportant arch in distro
<didrocks> (from last uploda)
<didrocks> upload*
<didrocks> if so, I'm ignoring the arch state in daily release
<didrocks> (right now, "important archs" are i386, amd64, armhf)

But we're still going to end up eventually pushing a package to distro that will attempt to build for powerpc and end up dep-waiting, right? That seems bogus. Like, it will show up on the ftbfs report with other dep-waiting packages, right?

[Didier Roche-Tolomelli (didrocks)]

@mterry: this is how the release team prefer we deal with, dep-waiting for ever and if one day, v8 or any build-deps becomes available, we can have it building.

I won't ship in ftbfs report as the last published version was already dep-waiting.

[Didier Roche-Tolomelli (didrocks)]

Note that I had to develop some code just for that on purpose for daily release on the release team request (so that we finish hardcoding the archs in Architectures:)

[Michael Terry (mterry)]

OK!

review: Approve

=== modified file 'debian/control'
--- debian/control	2013-06-14 21:06:57 +0000
+++ debian/control	2013-06-26 07:43:26 +0000
@@ -1,5 +1,6 @@
 Source: platform-api
 Priority: optional
+Section: devel
 Maintainer: Ubuntu Developers <[e-mail]>
 Build-Depends: cmake,
                debhelper (>= 9),
@@ -7,18 +8,17 @@
                libgles2-mesa-dev[armhf],
                libhybris-dev,
 Standards-Version: 3.9.4
-Section: devel
 Homepage: https://launchpad.net/platform-api
 Vcs-Bzr: lp:platform-api
-# If you aren't a member of http://pad.lv/~phablet-team but need to upload packaging changes,
-# just go ahead.  http://pad.lv/~phablet-team will notice and sync up the code again.
+# If you aren't a member of ~phablet-team but need to upload packaging changes,
+# just go ahead.  ~phablet-team will notice and sync up the code again.
 Vcs-Browser: https://code.launchpad.net/platform-api
 
 Package: libplatform-api-headers
 Section: libdevel
+Architecture: any
 Pre-Depends: ${misc:Pre-Depends},
 Multi-Arch: same
-Architecture: i386 amd64 armhf
 Depends: ${misc:Depends},
 Description: Platform API for system level capabilities (API headers)
  This package provides the library headers for the Platform API.
@@ -29,9 +29,9 @@
 
 Package: libplatform-api1-dev
 Section: libdevel
+Architecture: any
 Pre-Depends: ${misc:Pre-Depends},
 Multi-Arch: same
-Architecture: i386 amd64 armhf
 Depends: libgles2-mesa-dev,
          libplatform-api-headers (= ${binary:Version}),
          libplatform-api1-hybris | libplatform-api1,
@@ -41,13 +41,13 @@
  dependency) for the Platform API.
 
 Package: libplatform-api1-hybris
+Section: libs
+Architecture: any
 Provides: libplatform-api1,
 Conflicts: libplatform-api1,
 Replaces: libplatform-api1,
-Section: libs
 Pre-Depends: ${misc:Pre-Depends},
 Multi-Arch: same
-Architecture: i386 amd64 armhf
 Depends: libhybris,
          ${misc:Depends},
          ${shlibs:Depends},
@@ -58,7 +58,7 @@
  Android userspace, which is where the Ubuntu Application Manager lives.
 
 Package: libplatform-api1-hybris-tests
-Architecture: i386 amd64 armhf
+Architecture: any
 Depends: libplatform-api1-hybris (= ${binary:Version}),
          ${misc:Depends},
          ${shlibs:Depends},