"grep: Docs/INFO_SRC: No such file or directory" in build-ps/build-binary.sh

[Roel Van de Paar]

[roel@qaserver percona-server]$ ./build-ps/build-binary.sh .
grep: Docs/INFO_SRC: No such file or directory <-------------
[...]

[Roel Van de Paar (roel11)]

File is not to be found

[roel@qaserver percona-server]$ find . | grep INFO_SRC
[roel@qaserver percona-server]$

iirc, this file is used to give information on revisions of source code. Seems somewhat important. However, seems the issue is historical from input by Raghu.

[Roel Van de Paar (roel11)]

Alexey, please check and set proposed triage accordingly. Thanks

[Roel Van de Paar (roel11)]

Bug 1005787 ?

[Roel Van de Paar (roel11)]

Some further input

<raghu> Roel: I don't think that is used in current builds though
<Roel> https://bugs.launchpad.net/percona-server/+bug/1005787 is of interest
<raghu> for PS builds it is a bit different, INFO_SRC may be generated during source build
<raghu> so http://jenkins.percona.com/job/percona-server-5.5-source-tarball/lastSuccessfulBuild/artifact/percona-server-5.5.36-34.0.tar.gz has it
<Roel> hmm interesting
<raghu> ie. the source tarball build generates INFO_SRC
<Roel> but the build-binary.sh does not
<raghu> no
<raghu> you will need to do what source build does here http://jenkins.percona.com/job/percona-server-5.5-source-tarball/configure
<raghu> cmake . && make dist
<raghu> one of them generates that file
<raghu> Roel: easier would be to run build-binary on artifact of source-tarball build
<raghu> that is what also pushed to downloads/repos as source tar.gz
<raghu> regarding using build-binary on bzr tree
<raghu> yeah, there it may fail
<raghu> may if/then required there to check for that file etc.
<Roel> ok so the bug is valid but there could be better ways to build. would be good to get build-binary.sh to do the same as Jenkins builds

[Stewart Smith (stewart)]

Roel Van de Paar <email address hidden> writes:
> <raghu> cmake . && make dist
> <raghu> one of them generates that file
> <raghu> Roel: easier would be to run build-binary on artifact of source-tarball build
> <raghu> that is what also pushed to downloads/repos as source tar.gz
> <raghu> regarding using build-binary on bzr tree
> <raghu> yeah, there it may fail
> <raghu> may if/then required there to check for that file etc.
> <Roel> ok so the bug is valid but there could be better ways to
> build. would be good to get build-binary.sh to do the same as Jenkins
> builds

Yep, should be run from source tarball, as the INFO_SRC thing is
generated by MySQL CMake and used in build for all the version info

--
Stewart Smith

[Laurynas Biveinis (laurynas-biveinis)]

Fixed in https://code.launchpad.net/~tplavcic/percona-server/bug1319670-5.6/+merge/221017

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1481