dpkg-buildpackage fails on 9.2.6 on ubuntu 12.04.3 LTS
Preface on the venue: It is specified in the description of mailing
lists that pgsql-general is for all topics except those relating to
failed compiles. However doing a search for the word compile fails to
yield any other mailing list for said compilation failures. Presumably
this is the said mailing list for compilation failures.
The compilation appears to fail on initdb, specifying that the initdb
as expected must be run by the user that runs the daemon, postgres,
when executing:
dpkg-buildpackage
Executing:
sudo -u postgres dpkg-buildpackage
Does not work. How does one build a debian package from source?
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
tail of the failure.
Running:
sudo -u postgres dpkg-buildpackage -rsudo
Ends in the same failure.
On Mon, Dec 16, 2013 at 9:50 PM, imagenesis@gmail.com
<imagenesis@gmail.com> wrote:
Preface on the venue: It is specified in the description of mailing
lists that pgsql-general is for all topics except those relating to
failed compiles. However doing a search for the word compile fails to
yield any other mailing list for said compilation failures. Presumably
this is the said mailing list for compilation failures.The compilation appears to fail on initdb, specifying that the initdb
as expected must be run by the user that runs the daemon, postgres,
when executing:dpkg-buildpackage
Executing:
sudo -u postgres dpkg-buildpackage
Does not work. How does one build a debian package from source?
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
This is resolved by running dpkg-buildpackage with postgres and
dpkg-buildpackage -rsudo with the postgresql source folder in a
directory owned by postgres as dpkg creates a temporary folder in said
parent directory.
However, I am now running into the following issue:
The reason I am compiling is because I must change #define NAMEDATALEN
64 to a larger value. Setting it to 256 has presumably yielded the
following errors in the make check:
It fails on the name and enum tests.
I am rerunning the compilation to confirm this is a result of this
change. Please specify how to remove the regression check from the
dpkg build or how to resolve this (is there a max value that will not
fail?) if this is caused by this change or by something else on the
specified platform.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Resolved.
Regression test outputs for name and enum can be replaced with generated out.
On Tue, Dec 17, 2013 at 12:17 AM, imagenesis@gmail.com
<imagenesis@gmail.com> wrote:
This is resolved by running dpkg-buildpackage with postgres and
dpkg-buildpackage -rsudo with the postgresql source folder in a
directory owned by postgres as dpkg creates a temporary folder in said
parent directory.However, I am now running into the following issue:
The reason I am compiling is because I must change #define NAMEDATALEN
64 to a larger value. Setting it to 256 has presumably yielded the
following errors in the make check:It fails on the name and enum tests.
I am rerunning the compilation to confirm this is a result of this
change. Please specify how to remove the regression check from the
dpkg build or how to resolve this (is there a max value that will not
fail?) if this is caused by this change or by something else on the
specified platform.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers