Re: Trying to upgrade bash on squeeze, running into errors
I just did this thanks to this tip:
https://wiki.debian.org/LTS/Using
https://wiki.debian.org/LTS
https://wiki.debian.org/LTS/FAQ
Joe
Russell Jones ---09/29/2014 07:40:50 PM---Hi Don, Thanks for the help! It looks like the diversion does exist, so doesn't
From: Russell Jones <russell-list@jonesmail.me>
To: debian-user@lists.debian.org
Date: 09/29/2014 07:40 PM
Subject: Re: Trying to upgrade bash on squeeze, running into errors
Hi Don,
Thanks for the help! It looks like the diversion does exist, so doesn't
look like that's the issue:
local diversion of /bin/sh to /bin/sh.distrib
I am not wanting to change the default shell, just trying to upgrade
bash to close the Shellshock vulnerability. Any further ideas on how to
get past this issue?
Thanks!
On 9/26/2014 6:43 PM, Don Armstrong wrote:
> On Fri, 26 Sep 2014, Russell Jones wrote:
>> I've seen several posts about this Bash upgrade issue, but no real
>> answers on how to get past it. Any assistance would be appreciated,
>> thank you!
> This looks like the diversions for /bin/sh got removed or otherwise
> improperly modified at some point in time.
>
> dpkg-divert --list '/bin/sh*';
>
> will show you what the diversions are.
>
> You should have a diversion of /bin/sh to /bin/sh.distrib by dash or by
> bash (depending on which of them you want to be the default shell).
>
> If the diversion doesn't exist, then you probably want to run the
> following (for dash to be the default shell)
>
> dpkg-divert --package dash --divert /bin/sh.distrib --add /bin/sh;
> dpkg-divert --package dash --divert /usr/share/man/man1/sh.distrib.1.gz \
> --add /usr/share/man/man1/sh.1.gz;
>
> or similar.
>
> In theory, running /var/lib/dpkg/info/dash.preinst; should also do this
> for you.
>
>
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] 5429EDD5.5030800@jonesmail.me">https://lists.debian.org/[🔎] 5429EDD5.5030800@jonesmail.me
Reply to: