Ok, so just so I understand: You have the debian/ code in a git repository, but no drizzle code? And then you import a drizzle source tarball for packaging, and it then thinks it is part of your git repository even when it is not? I think in this case disabling the .git detection is relatively good solution.
Still, I think the root cause is the running of autorun.sh. I know the Debian packaging manual tells you to do it, otoh the point of the autotools workflow is that the upstream developers run aclocal (autorun.sh) and release the tarball with that, then the consumers of the tarball should be content with ./configure. I've never understood (even from your above reply) what benefit re-running autorun.sh is supposed to give you? -- 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 -- Mailing list: https://launchpad.net/~linux-traipu Post to : [email protected] Unsubscribe : https://launchpad.net/~linux-traipu More help : https://help.launchpad.net/ListHelp
