backports for trusty

[Enrico Weigelt, metux IT consult]

On 14.04.2017 08:31, Ralf Mardorf wrote:

> I'm neither an Ubuntu developer, nor do I maintains some backports.
> However, a lot of backports easily could be counter-productive regarding
> the Long Term Support's policy.

Why so ?

> Consider to provide your packages by a PPA.

I'm already trying this, but somethings not right yet.
What I've done so far:

* created a ppa:
  https://launchpad.net/~metux/+archive/ubuntu/cairo-drm

* created a project w/ git repo and my uploaded (debianized) tree
  https://launchpad.net/cairo-drm
  https://code.launchpad.net/~metux/cairo-drm/+git/cairo-drm

  --> git upload seems to be fine (git ls-remote showed it up),
      but the branch doesn't appear on the lp web frontend

* created a build receipe:
  https://code.launchpad.net/~metux/+recipe/trusty

* build ran but failed:
  https://launchpadlibrarian.net/315946016/buildlog.txt.gz

>> subprocess.CalledProcessError: Command '['git', '-C',
'/home/buildd/build-RECIPEBRANCHBUILD-1353331/chroot-autobuild/home/buildd/work/tree/recipe',
'fetch', 'lp:cairo-drm', 'HEAD:refs/remotes/source/HEAD',
'refs/heads/*:refs/remotes/source/*']' returned non-zero exit status 128

That looks a bit strange to me - it should just clone and checkout
refs/branches/trusty/master, and not care about the symbolic ref 'HEAD'.


--mtx