linux-traipu team mailing list archive

[coldtobi <970944@xxxxxxxxxxxxxxxxxx>]

Hallo Henrik,

yes, for proper building I need to call config/autorun.sh before
configure (e.g to keep the tree debbuild-able twice in a row), but that
is not the point.

The point is that the buildsystem thinks it is building from the drizzle VCS, but the VCS I have in place is to keep track the packaging stuff, not the drizzle source code, as I'm using git-buildpackage to maintain the packaging. 
And that confuses the buildsystem, leading to a different behaviour during build (compared to when building with pdebuilder or later on the buildd)

Of course, I can perfectly live with this, as I have added a patch to
hack around that detection. But #968824 shows me that this also hits
other people...

(I was also hit by thhe warnings -> error problem during building...)

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/970944

Title:
  The pandora buildsystem does not detect if the VCS repository is the
  offical drizzle repository

Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
  New

Bug description:
  For Debian, the files required to keep the packaging are kept in its
  own VCS (https://gitorious.org/drizzle-debian/drizzle-
  debian/trees/master)

  However, the pandora-buildsystem does not detect this and subsequently
  the build fails in the Debian maintainer's sandbox.

  I work around this issue by disabling the detection for git in
  m4/pandora_vc_build.m4   (see Debian patch   http://patch-
  tracker.debian.org/patch/series/view/drizzle/2012.01.30-3/pandora-
  ignore-git-repo.patch) but this is not a complete fix.

  coldtobi

To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/970944/+subscriptions