Re: Patch for bash

1999-09-13 Thread Anthony Towns
On Sat, Aug 28, 1999 at 05:13:55AM +1000, Anthony Towns wrote: > So Guy, would you be willing to apply this patch? Unfortunately, I don't > seem to be able to compile bash properly (the libc5 stuff dies horrible > deaths if I don't comment it out), so I can't offer to make an NMU, but > hopefully s

Re: Patch for bash

1999-08-30 Thread Anthony Towns
severity 34717 wishlist thanks Severity rationale: the current behaviour is bug free, and works. Having /bin/sh point to ash is not a release critical feature. A workaround exists: use: # dpkg-divert --rename --add /bin/sh # ln -sf ash /bin/sh to get the desired behaviour without c

Re: Patch for bash

1999-08-28 Thread Michael Stone
On Sat, Aug 28, 1999 at 02:10:01PM +1000, Anthony Towns wrote: > Note that the first maintainer script after "remove /bin/sh" is the > postinst -- adding the link in the preinst doesn't do us any good on > upgrades. Ok. I stand corrected. How's this for a nasty hack: what if the preinst diverts /b

Re: Patch for bash

1999-08-28 Thread Richard Braakman
Anthony Towns wrote: > On Sat, Aug 28, 1999 at 12:22:37PM +0200, Richard Braakman wrote: > > Frankly, I think this whole process is too risky for the benefit gained, > > certainly too much risk for a non-maintainer upload, and that we shouldn't > > do it with current tools. > > Do note that changi

Re: Patch for bash

1999-08-28 Thread Anthony Towns
On Sat, Aug 28, 1999 at 12:22:37PM +0200, Richard Braakman wrote: > Anthony Towns wrote: > > Furthermore, Essential packages are always immediately configured by Apt, > > so we don't have an issue there either. > That means we're dropping support for all non-APT dselect methods in > potato. I don'

Re: Patch for bash

1999-08-28 Thread Richard Braakman
Anthony Towns wrote: > Furthermore, Essential packages are always immediately configured by Apt, > so we don't have an issue there either. That means we're dropping support for all non-APT dselect methods in potato. I don't think that's a good idea, since people will be upgrading from slink, whic

Re: Patch for bash

1999-08-28 Thread Anthony Towns
On Fri, Aug 27, 1999 at 06:10:20PM -0400, Michael Stone wrote: > On Fri, Aug 27, 1999 at 11:28:30PM +0200, Raphael Hertzog wrote: > > Which is also not so logical since in the preinst bash is not yet unpacked > > and there may be no /bin/bash ... it may be installed in the > > preinst when the pack

Re: Patch for bash

1999-08-27 Thread Michael Stone
On Fri, Aug 27, 1999 at 11:28:30PM +0200, Raphael Hertzog wrote: > Which is also not so logical since in the preinst bash is not yet unpacked > and there may be no /bin/bash ... it may be installed in the > preinst when the package is upgraded ($1 = upgrade) only (in which > case the link should al

Re: Patch for bash

1999-08-27 Thread Raphael Hertzog
Le Fri, Aug 27, 1999 at 04:40:41PM -0400, Michael Stone écrivait: > I'm a little concerned about creating the link in the postinst, as that > part of the install (IIRC) can be delayed for various reasons. (And it > would be a Bad Thing to risk losing /bin/sh for an indefinite period of > time.) Can

Re: Patch for bash

1999-08-27 Thread Michael Stone
On Sat, Aug 28, 1999 at 05:13:55AM +1000, Anthony Towns wrote: > * postinst is a /bin/bash script instead of a /bin/sh script -- this >means it won't fail if for some reason there isn't a /bin/sh symlink >already. If there isn't a symlink (or or an actual file) it makes >