[Bug 422189] Re: Can't exec id errors from pg_maintenance after upgrading to 87ubuntu1

2009-09-09 Thread Launchpad Bug Tracker
This bug was fixed in the package postgresql-common - 87ubuntu2 --- postgresql-common (87ubuntu2) hardy-proposed; urgency=low * pg_maintenance: Fix $PATH to include /usr/bin, so that the cron job can run the id command. (LP: #422189) -- Martin Pitt martin.p...@ubuntu.com

[Bug 422189] Re: Can't exec id errors from pg_maintenance after upgrading to 87ubuntu1

2009-09-02 Thread Nafallo Bjälevik
Haven't got a cronspam since I updated the packages this morning. +1 -- Can't exec id errors from pg_maintenance after upgrading to 87ubuntu1 https://bugs.launchpad.net/bugs/422189 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 422189] Re: Can't exec id errors from pg_maintenance after upgrading to 87ubuntu1

2009-09-02 Thread Martin Pitt
** Tags added: verification-done ** Tags removed: verification-needed -- Can't exec id errors from pg_maintenance after upgrading to 87ubuntu1 https://bugs.launchpad.net/bugs/422189 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

Re: [Bug 422189] Re: Can't exec id errors from pg_maintenance after upgrading to 87ubuntu1

2009-09-01 Thread James Troup
Martin Pitt martin.p...@ubuntu.com writes: Hm, this exact change has been in intrepid onwards without such reports, and $PATH in cron.d defaults to /usr/bin:/bin in Lenny and Karmic, so I don't think this changed just recently. Is that default $PATH change a local customization on your

[Bug 422189] Re: Can't exec id errors from pg_maintenance after upgrading to 87ubuntu1

2009-09-01 Thread Martin Pitt
Argh, this was a regression from: revno: 758 committer: Martin Pitt martin.p...@ubuntu.com branch nick: postgresql-common timestamp: Sun 2007-05-20 13:36:59 +0200 message: * pg_createcluster, pg_ctlcluster, pg_dropcluster, pg_maintenance, pg_upgradecluster: Strip down PATH untainting to the

[Bug 422189] Re: Can't exec id errors from pg_maintenance after upgrading to 87ubuntu1

2009-09-01 Thread Martin Pitt
Straightforward debdiff to fix this, I tested this now. Uploaded to the queue, needs Steve or Colin to process. ** Attachment added: 87ubuntu2 debdiff http://launchpadlibrarian.net/31114782/postgresql-common.422189.debdiff ** Changed in: postgresql-common (Ubuntu Hardy) Status: In

[Bug 422189] Re: Can't exec id errors from pg_maintenance after upgrading to 87ubuntu1

2009-09-01 Thread Colin Watson
Accepted into hardy-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Tags added: verification-needed -- Can't

[Bug 422189] Re: Can't exec id errors from pg_maintenance after upgrading to 87ubuntu1

2009-09-01 Thread Martin Pitt
Hm, this exact change has been in intrepid onwards without such reports, and $PATH in cron.d defaults to /usr/bin:/bin in Lenny and Karmic, so I don't think this changed just recently. Is that default $PATH change a local customization on your servers? Anyway, easy enough to fix, I was just

[Bug 422189] Re: Can't exec id errors from pg_maintenance after upgrading to 87ubuntu1

2009-08-31 Thread Steve Langasek
12:20 slangasek elmo: blink is /usr/bin not in the path? 12:20 elmo slangasek: not in a cron job, no 12:21 slangasek hrm 12:21 elmo not unless the cron file goes to the trouble of setting $PATH 12:21 elmo /etc/crontab sets PATH, but postgresql-common is in /etc/cron.d ** Also affects: