Comment 11 for bug 155423

Steve Langasek (vorlon) wrote :

Yes, sorry, the bzr repo made use of some fairly cutting-edge functionality to merge the upstream and Debian branches, so it's not surprising that it doesn't work with the gutsy version of bzr.

As for pushing the patch, I'd looked at this bug before and was unconvinced that this is a bug that warrants fixing in update-grub. "noclobber" is really just not supposed to get set for system scripts, and I think that's the real bug here; we could fix update-grub now to be safe under noclobber, but how many more times would we have to play whack-a-mole with scripts on the system that don't work under noclobber?

For comparison, this same 'noclobber' issue was discussed in Debian several years ago in connection to another package, and the conclusion was that having "noclobber" set in such a way that it's inherited by package scripts is unsupported: http://bugs.debian.org/275140

And the recommendation from <http://bugs.debian.org/cgi-bin/275140#37> is that "set -o noclobber" should be guarded by if [ -n "$PS1" ].

Alex, does changing your .bashrc in this manner give you the desired behavior?