Bug#288616: acknowledged by developer (Re: Bug#288616: use of ">" in tetex postinst errors for sites using bash noclobber)
- To: 288616@bugs.debian.org
- Subject: Bug#288616: acknowledged by developer (Re: Bug#288616: use of ">" in tetex postinst errors for sites using bash noclobber)
- From: "George Georgalis" <george@galis.org>
- Date: Sun, 28 Aug 2005 21:00:53 -0400
- Message-id: <[🔎] 20050829010053.GB10940@sta.duo>
- Reply-to: "George Georgalis" <george@galis.org>, 288616@bugs.debian.org
- In-reply-to: <handler.288616.D288616.11251750802074.notifdone@bugs.debian.org>
- References: <87psrz86ai.fsf@alhambra.kuesterei.ch> <20050104173659.GB24751@sta.local> <handler.288616.D288616.11251750802074.notifdone@bugs.debian.org>
On Sat, Aug 27, 2005 at 01:48:13PM -0700, Debian Bug Tracking System wrote:
>This is an automatic notification regarding your Bug report
>#288616: use of ">" in tetex postinst errors for sites using bash noclobber,
>which was filed against the tetex-base package.
>
>[...]
>> Frank K=FCster asked you some questions half a year ago, but you never
>> reacted. Do still intend to help us to track down the problem?=20=20
>
>Again no reaction for a couple of weeks. There is no bug in tetex-bin,
>and I guess nowhere at all.
Sorry I didn't notice any inquiry since my last followup.
I suppose not, no bugs. The method of generating temp files is
not as I would choose. I tend to prefer to set no clobber in my
environment as people often alias -i with rm, but the problem
I experienced probably wouldn't have happened on a white box
test. My system had BASH_ENV set which is bound to cause problems
in any 'distribution' and was not intentional by my part -- the
shell loaded a user environment, which caused the script to fail
due to its dependency on being able to clobber files. Unless that
becomes a default option in debian bash, I see no bug.
// George
--
George Georgalis, systems architect, administrator <IXOYE><
http://galis.org/ cell:646-331-2027 mailto:george@galis.org
Reply to: