Bug#392587: lintian: doc-base check: shell glob not correctly expanded
retitle 392587 doc-base: clarify allowable shell glob patterns severity 392587 wishlist reassign 392587 doc-base thanks Currently, the doc-base documentation says the following about the Files field: Files Space separated list of filenames or shell globs representing the files which constitute the documentation in this format. Required field. Since the type of shell glob isn't specified, lintian assumes that this means a POSIX shell glob and supports *, ?, and [] but not {,}. Is that the intention? If so, could that be stated explicitly? If not, could you mention the specific wildcards that are supported and let me know so that I can update lintian accordingly? Thanks! -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392587: lintian: doc-base check: shell glob not correctly expanded
On Thu, Oct 12, 2006 at 09:31:14AM -0700, Russ Allbery wrote: Lionel Elie Mamane [EMAIL PROTECTED] writes: lintian triggers an error on scsh-doc-0.6 (source scsh-0.6), while I don't see any problem: E: scsh-0.6-doc: doc-base-file-references-missing-file scsh:8 /usr/share/doc/scsh-0.6-doc/scsh-manual/html/*.{html,css,gif} E: scsh-0.6-doc: doc-base-file-references-missing-file scsh-paper:8 /usr/share/doc/scsh-0.6-doc/scsh-paper/html/*.{html,css} The doc-base documentation isn't horribly clear, so right now lintian is erring on the side of caution and assuming that shell globs only means something that works with a POSIX shell. {} globs are a bashism Ah, I see. I'm happy to change lintian if the doc-base specification intended to allow this, but right now it's really unclear. The right course of action may be to reassign this bug to doc-base (or to both doc-base and lintian) and ask the doc-base maintainer to clarify the specification. Yup. Let's do that. -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392587: lintian: doc-base check: shell glob not correctly expanded
Package: lintian Version: 1.23.24 Severity: normal lintian triggers an error on scsh-doc-0.6 (source scsh-0.6), while I don't see any problem: E: scsh-0.6-doc: doc-base-file-references-missing-file scsh:8 /usr/share/doc/scsh-0.6-doc/scsh-manual/html/*.{html,css,gif} E: scsh-0.6-doc: doc-base-file-references-missing-file scsh-paper:8 /usr/share/doc/scsh-0.6-doc/scsh-paper/html/*.{html,css} but: [EMAIL PROTECTED]:~$ for f in /usr/share/doc/scsh-0.6-doc/scsh-manual/html/*.{html,css,gif}; do dpkg -S $f; done scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-H-10.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-H-11.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-H-12.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-H-13.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-H-1.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-H-2.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-H-3.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-H-4.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-H-5.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-H-6.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-H-7.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-H-8.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-H-9.html scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-S.css scsh-0.6-doc: /usr/share/doc/scsh-0.6-doc/scsh-manual/html/man-Z-G-D-1.gif Probably it doesn't expand the shell glob (which the doc-base documentation says is allowed in this filed) correctly? -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-amd64 Locale: LANG=fr_LU.UTF-8, LC_CTYPE=fr_LU.UTF-8 (charmap=UTF-8) Versions of packages lintian depends on: ii binutils 2.17-2 The GNU assembler, linker and bina ii diffstat 1.43-1 produces graph of changes introduc ii dpkg-dev 1.13.22 package building tools for Debian ii file 4.17-3 Determines file type using magic ii gettext 0.15-2 GNU Internationalization utilities ii intltool-debian 0.35.0+20060710 Help i18n of RFC822 compliant conf ii libparse-debianchangelog 1.0-1 parse Debian changelogs and output ii man-db 2.4.3-3 The on-line manual pager ii perl [libdigest-md5-perl 5.8.8-6.1 Larry Wall's Practical Extraction lintian recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392587: lintian: doc-base check: shell glob not correctly expanded
Lionel Elie Mamane [EMAIL PROTECTED] writes: Package: lintian Version: 1.23.24 Severity: normal lintian triggers an error on scsh-doc-0.6 (source scsh-0.6), while I don't see any problem: E: scsh-0.6-doc: doc-base-file-references-missing-file scsh:8 /usr/share/doc/scsh-0.6-doc/scsh-manual/html/*.{html,css,gif} E: scsh-0.6-doc: doc-base-file-references-missing-file scsh-paper:8 /usr/share/doc/scsh-0.6-doc/scsh-paper/html/*.{html,css} The doc-base documentation isn't horribly clear, so right now lintian is erring on the side of caution and assuming that shell globs only means something that works with a POSIX shell. {} globs are a bashism (or possibly a Kornish, but either way, same effect), so the warning is currently intentional. I'm happy to change lintian if the doc-base specification intended to allow this, but right now it's really unclear. The right course of action may be to reassign this bug to doc-base (or to both doc-base and lintian) and ask the doc-base maintainer to clarify the specification. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]