Adam D. Barratt wrote:

> On Sat, 2008-11-08 at 14:41 +0100, Filippo Giunchedi wrote:
>> Hi,
>> 
>> On Sun, Nov 02, 2008 at 04:15:41PM +0000, Adam D. Barratt wrote:
>> > We are aware of the $'' bashism - indeed checkbashisms contains a
>> > commented-out check for it. The reason the check is disabled is that
>> > when it and a similar check for $"" were tested against the wide range
>> > of shell scripts available in Debian, they produced a high level of
>> > false positives and were disabled in devscripts 2.10.30, only one
>> > package after having been introduced.
>> 
>> Are there any examples of such false positives? A list of packages is fine :)

Examples:
possible bashism in ./usr/sbin/afserverconfig line 173 ($'...' should be 
"$(printf '...')"):
    eval num_var_params='"$'values__$num_var_sp_idx'"'

possible bashism in ./etc/cron.daily/changetrack line 22 ($'...' should be 
"$(printf '...')"):
    find /var/lib/dpkg/info -name '*.conffiles' -exec grep -v '.schemas$' '{}' 
';' | \

Complete list from one of the archive-wide checks:

afbackup_3.5.1pl2-4_i386.deb
afbackup-client_3.5.1pl2-4_i386.deb
changetrack_4.3-3_all.deb
cron_3.0pl1-104_i386.deb
dbmail_2.2.10-1+b1_i386.deb
debian-edu-install_0.669_all.deb
deborphan_1.7.24_i386.deb
groff_1.18.1.1-20_i386.deb
insserv_1.11.0-9_i386.deb
jigdo-file_0.7.3-1.1_i386.deb
latex-cjk-chinese_4.7.0+git20080122-1_i386.deb
latex-cjk-japanese_4.7.0+git20080122-1_i386.deb
libsidl-dev_1.2.0.dfsg-4_i386.deb
nsd3_3.0.7-3_i386.deb
snort_2.7.0-17_i386.deb
snort-mysql_2.7.0-17_i386.deb
snort-pgsql_2.7.0-17_i386.deb
vtun_3.0.1-2.1_i386.deb
wims_3.62-13_i386.deb

> 
> 
> I don't have an easily accessible list at the moment, I'm afraid; it's
> been a while since I've personally run an archive-wide scan.
> 
> I'll have a look over the next couple of days and see if I can find one
> of the older sets of results.

I guess you won't need to do it anymore ;)

> 
> Regards,
> 
> Adam

Cheers,
-- 
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to