[Pkg-postgresql-public] buildd path too long (postgresql-9.3 FTBFS)

Philipp Kern pkern at debian.org
Sun May 12 19:52:19 UTC 2013

On Sat, May 11, 2013 at 06:24:38PM -0700, Christoph Berg wrote:
> On the packaging side, we could easily replace "/build/" by "/b/", but
> that saves only 4 bytes, while we'd need to save at least 11. Changing
> the location to be somewhere else seems like an invasive change to the
> upstream test system I'd rather like to avoid (pg_upgrade is a pretty
> sophisticated program that should rather operated as designed).

It does seem to me that running it with a socket in $TMPDIR instead of the
current directory would solve the problem, though. Is there no env var
for this? Also during regular operation it looks like this would be not
insane to do if it invokes temporary daemons.

The current directory design is due to the following:

* /build is a separate persistent partition.
* /build/$pkg-$ver-$arch-$random is the base dir to host the source files and
  the unpacked source
* /build/$pkg-$ver-$arch-$random/$pkg-$ver is the result of the dpkg unpack.

Hence you can just remove /build/$pkg-$ver-$arch-$random and be guaranteed
to have no remainder on disk.

Kind regards
Philipp Kern 

More information about the Pkg-postgresql-public mailing list