Bug#264241: Some corrections regardings statements in this bug
On 11.08.04 Adrian Bunk (bunk@fs.tum.de) wrote:
Hi,
> Some corrections regarding statements in this bug ("postrm assumes
> mktexlsr is available").
>
> <-- snip -->
>
> Ryan Murray:
> > You can't assume that any of your dependencies are available in
> > your postrm script, so you need to handle the case where mktexlsr
> > has already been removed.
>
> mktexlsr is in tetex-bin.
>
> tetex-extra depends on tetex-bin.
>
> Section 7.2. of your policy states:
>
> <-- snip -->
> ...
> The `Depends' field should also be used if the `postinst',
> `prerm' or `postrm' scripts require the package to be present in
> order to run. Note, however, that the `postrm' cannot rely on
> any non-essential packages to be present during the `purge'
> phase.
> ...
> <-- snip -->
>
> Could you explain your statement which exactly contradicts your policy
>
So, what are you trying to tell me? As far as I understand you tell
me, that this bug is not a bug.
> (note that the tetex-extra postinst does nothing during purge)?
>
mktexlsr is intended to be called in case of upgrade, remove or purge.
Hence we don't check $1, but call it unconditionally.
> Can you reproduce the bug?
> If yes, does it help to let /var/lib/dpkg/info/tetex-extra.postrm start
> with
> #!/bin/bash
> ?
>
> <-- snip -->
>
> Hilmar Preusse:
>
> > The man page of bash tells us, that it should be sufficient to do so
> > if /bin/sh points to /bin/bash. I guess we have to remove the bashism
> > in that script and are done. Correct?
>
>
> If the problem is a bashism, the trivial solution is to let the script
> start with
> #!/bin/bash
> instead of
> #!/bin/sh
>
> This is 100% correct since bash is Essential and /bin/bash is therefore
> garuanteed to be always available.
>
> <-- snip -->
>
The more convenient solution could be to remove to bashism. Should
not be that hard in this special case. I'm not sure, if command is a
bashism or if it is available in dash too.
I'd like to see another tetex-base package RSN and I'd like to have
this bug closed too.
Thanks,
H.
--
sigmentation fault
Reply to: