Hi!
On Tue, 2014-12-02 at 03:38:42 +0100, Andreas Beckmann wrote:
> Package: dpkg
> Version: 1.17.22
> Severity: important
> while debugging another broken symlink-to-directory transition
> (libavifile-0.7-dev) I noticed that the proper maintainer script content
> is there, except for a superfluous slash after the PATHNAME argument:
>
> dpkg-maintscript-helper symlink_to_dir /usr/share/doc/libavifile-0.7-dev/
> /usr/share/doc/libavifile-0.7-common 1:0.7.48~20090503.ds-16.1~ -- "$@" --
> "$@"
>
> Digging into d-m-h, the old symlink is not recognized as a symlink and
> therefore no action is performed. This is because
>
> [ -h /path/to/link ]
>
> will succeed but
>
> [ -h /path/to/link/ ]
>
> will fail.
>
> Maybe
>
> local SYMLINK="${1%/}"
>
> could help (for single trailing slashes)
While true, this feels a bit like playing wack-a-mole.
> While the packages should not give such incorrect arguments,
> I think it would be easiest to fix d-m-h to cope with this.
I guess you set the severity to important, because it would avoid
having to fix the affected package? How many packages are we talking
about? Is it just that one?
I guess I could use your proposed fix (for both symlink_to_dir and
dir_to_symlink) or use «realphat -m» over the symlink or pathname, but
I'd need to carefully ponder about the consequences. I'd rather do this
if at all for 1.18.x, but that would defeat your bug report I guess. :)
Thanks,
Guillem
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
