On 13-Apr-2011, Debian Bug Tracking System wrote:
> Date: Wed, 13 Apr 2011 23:12:15 +0300
> From: "Andrew O. Shadoura" <bugzi...@tut.by>
> Message-ID: <20110413231215.189a2fc2@ileemo>
>
> On Wed, 13 Apr 2011 22:04:54 +0200
> Luk Claes <l...@debian.org> wrote:
>
> > Unless you show that you:
> >
> > 1) have bash 4.1-3 or later installed ('apt-cache policy bash' for
> > instance) 2) are using bash as shell ('exec bash' for instance)
> > 3) sunrpc service is running ('lsof -i :111' for instance)
> > 4) still have this issue
> >
> > It's going to stay closed as only in that case it's supposed to
> > work.
>
> If it's the only case, it should be specified explicitly.
$ dpkg-query --showformat='Depends: ${Depends}\n' --show nfs-common
Depends: libc6 (>= 2.4), libcap2 (>= 2.10), libcomerr2 (>= 1.01),
libevent-1.4-2 (>= 1.4.13-stable), libgssapi-krb5-2 (>= 1.6.dfsg.2),
libgssglue1, libk5crypto3 (>= 1.6.dfsg.2), libkrb5-3 (>= 1.6.dfsg.2),
libnfsidmap2, libtirpc1, libwrap0 (>= 7.6-4~), rpcbind | portmap, adduser, ucf,
lsb-base (>= 1.3-9ubuntu3), netbase (>= 4.24), initscripts (>= 2.86.ds1-38.1)
No mention of bash at all. If a specific version of bash is required,
that must be expressed as a dependency.
> And, after all, why not use the utility that is supposed to be used,
> and not this hackish thing?
The patch supplied with the original message on this bug report works,
AFAICT. I ask again that it be applied, to avoid needing to use
version-specific Bash features.
--
\ “We can't depend for the long run on distinguishing one |
`\ bitstream from another in order to figure out which rules |
_o__) apply.” —Eben Moglen, _Anarchism Triumphant_, 1999 |
Ben Finney <b...@benfinney.id.au>
signature.asc
Description: Digital signature
