no @ward. i have been working with the dev team recently. while my change does work, it has the potential to mute legitimate problems at that spot in the code. we have been discussing possible proper resolution.
the dev team learned that the component that is behind the failure is the...
i think i got it.
in /usr/share/perl5/PMG/DBTools.pm, in sub postgres_admin_cmd, i changed this...
original
local $> = $uid;
$! && die "setuid postgres ($uid) failed - $!\n";
to
local $> = $uid || die "setuid postgres ($uid) failed - $!\n";
was this ever corrected?
i too am seeing this problem. our eval system is stuck trying to upgrade to pmg-api 5.1-3. so far i have traced the issue to a call from 'pmgdb init' during postinstall.
in a perl debug trace i have drilled down to this call:
PMG:: DBTools:: postgres_admin_cmd('psql'...