Your message dated Sat, 25 Jan 2014 17:19:38 +0000 with message-id <e1w76to-0006fx...@franck.debian.org> and subject line Bug#701549: fixed in refdb 1.0.0-1 has caused the Debian Bug report #701549, regarding refdb-clients: bashism in /bin/sh script to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 701549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: refdb-clients Version: 0.9.9-3 Severity: serious User: debian-rele...@lists.debian.org Usertags: goal-dash Hello maintainer, While performing an archive wide checkbashisms (from the 'devscripts' package) check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' output: >possible bashism in ./usr/bin/refdb-backup line 158 (should be >word >2>&1): >${refdba} -C listdb &> /dev/null || \ > endScript "Error: Unable to access RefDB using client 'refdba'." > "failed" > >possible bashism in ./usr/bin/refdb-backup line 160 (should be >word >2>&1): >${refdbc} -C listdb &> /dev/null || \ > endScript "Error: Unable to access RefDB using client 'refdbc'." > "failed" > >possible bashism in ./usr/bin/refdb-backup line 187 (should be >word 2>&1): > mkdir ${dirname} &> /dev/null > >possible bashism in ./usr/bin/refdb-backup line 193 (should be >word 2>&1): > ${refdbc} -C getref -d ${db} -t ${format} -o ${reffile} ":ID:>0" \ > &> /dev/null > >possible bashism in ./usr/bin/refdb-backup line 199 (should be >word 2>&1): > ${refdbc} -C getnote -d ${db} -t xnote -o ${notefile} ":NID:>0" \ > &> /dev/null > >possible bashism in ./usr/bin/refdb-backup line 206 (should be >word >2>&1): >mkdir ${styles_directory} &> /dev/null >possible bashism in ./usr/bin/refdb-backup line 217 (should be >word 2>&1): > ${refdba} -C getstyle -o ${stylefile} ${style} &> /dev/null >possible bashism in ./usr/bin/refdb-backup line 235 (should be >word >2>&1): >mv -f ${archive} ${backup_dir} &> /dev/null >possible bashism in ./usr/bin/refdb-restore line 133 (should be >word >2>&1): >tar -tzf ${archive} &> /dev/null || \ > endScript "'${archive}' is not a valid archive." "failed" > >possible bashism in ./usr/bin/refdb-restore line 137 (should be >word >2>&1): > ${refdba} -C listdb &> /dev/null || \ > endScript "Error: Unable to access RefDB using client 'refdba'." > "failed" > >possible bashism in ./usr/bin/refdb-restore line 139 (should be >word >2>&1): >${refdbc} -C listdb &> /dev/null || \ > endScript "Error: Unable to access RefDB using client 'refdbc'." > "failed" > >possible bashism in ./usr/bin/refdb-restore line 167 (should be >word 2>&1): > tar -xzf ${archive} ${reffile} &> /dev/null > >possible bashism in ./usr/bin/refdb-restore line 171 (should be >word >2>&1): > refdba -C createdb ${db} &> /dev/null > >possible bashism in ./usr/bin/refdb-restore line 176 (should be >word >2>&1): > refdbc -C addref -d ${db} -t ${format} ${reffile} &> > /dev/null > >possible bashism in ./usr/bin/refdb-restore line 183 (should be >word >2>&1): > tar -xzf ${archive} ${notefile} &> /dev/null > >possible bashism in ./usr/bin/refdb-restore line 187 (should be >word >2>&1): > refdbc -C addnote -d ${db} ${notefile} &> /dev/null >possible bashism in ./usr/bin/refdb-restore line 197 (should be >word >2>&1): > tar -xzf ${archive} ${stylefile} &> /dev/null > >possible bashism in ./usr/bin/refdb-restore line 206 (should be >word >2>&1): > refdba -C addstyle ${stylefile} &> /dev/null Not using bash (or a Debian Policy conformant shell interpreter which doesn't provide such an extra feature) as /bin/sh is likely to lead to errors or unexpected behaviours. You can find hints about how to fix bashisms at: https://wiki.ubuntu.com/DashAsBinSh Thank you, Raphael Geissert
--- End Message ---
--- Begin Message ---Source: refdb Source-Version: 1.0.0-1 We believe that the bug you reported is fixed in the latest version of refdb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 701...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Malaterre <ma...@debian.org> (supplier of updated refdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sat, 25 Jan 2014 12:03:59 +0100 Source: refdb Binary: refdb-clients refdb-server refdb-www refdb-doc Architecture: source amd64 all Version: 1.0.0-1 Distribution: unstable Urgency: low Maintainer: Debian XML/SGML Group <debian-xml-sgml-p...@lists.alioth.debian.org> Changed-By: Mathieu Malaterre <ma...@debian.org> Description: refdb-clients - Reference database and bibliography tool - clients refdb-doc - Reference database and bibliography tool - doc refdb-server - Reference database and bibliography tool - sql server refdb-www - Reference database and bibliography tool - www server Closes: 701549 701873 724430 733330 733484 Changes: refdb (1.0.0-1) unstable; urgency=low . * New release: 1.0.0 ! Closes: #733330, #724430, #701549 * Fix refdb-init test. Closes: #701873 * Add missing depends. Closes: #733484 Checksums-Sha1: dd7412e452451cafdc67e8506d4ccfc67573feac 2404 refdb_1.0.0-1.dsc 8ea265ddf9ae5ac880e4b28ca11e042b4352cc68 3315959 refdb_1.0.0.orig.tar.gz d8d506cccc6986854ae0a58cfa37c839a612f758 12732 refdb_1.0.0-1.debian.tar.xz 8e9f7b4d1e8aaed2dca8909107652312d34969bf 350496 refdb-clients_1.0.0-1_amd64.deb a850cd7a14f7917e7ca4f6dac473e0523e7ddce5 246446 refdb-server_1.0.0-1_amd64.deb 8ca080f03abd52ae6a6c019bc1b81883f75c89d7 78442 refdb-www_1.0.0-1_all.deb 129b5423ed27176ae00f71dca52688544d5d3101 1450032 refdb-doc_1.0.0-1_all.deb Checksums-Sha256: b5ac6eaef02f7324620b2dbaaeb87d702fe2905ba2b8f9d83ca574984e27be34 2404 refdb_1.0.0-1.dsc 6c4bdff0cc1cd509c1e1ce8558862c05f5eb193fb10bf8b3144cd8f1cd45660d 3315959 refdb_1.0.0.orig.tar.gz 55a2a12871692905f74c8f2bf5dd0ace3dfa50673019dd4f6c5ef41ace9a58e1 12732 refdb_1.0.0-1.debian.tar.xz b8b823ec3b8dd00c9ebb906a2ddc430ef2e76219b23474449ffe6d86da294400 350496 refdb-clients_1.0.0-1_amd64.deb 333d6bfd0c8747c511932d5c106e67d0737a0daa73fd4e9c0adef96ad1837bf5 246446 refdb-server_1.0.0-1_amd64.deb 45e3a359283e9febeb02357d037f4d0b1267b9bdc2d879c470a43509930e59cd 78442 refdb-www_1.0.0-1_all.deb 271f660fcdf32027ff3195534f50cb815d1b4c13864c9f3395c1c48f9d7a44b2 1450032 refdb-doc_1.0.0-1_all.deb Files: 64c2a096294da3b5988c33f43462caa3 2404 text optional refdb_1.0.0-1.dsc fab95d1f4f1e126368ae43d1f3696217 3315959 text optional refdb_1.0.0.orig.tar.gz 46fc0744db0c72f1d3b74dcb2fcc3f76 12732 text optional refdb_1.0.0-1.debian.tar.xz 325eec30d08e38986d9dcdef956fd08f 350496 text optional refdb-clients_1.0.0-1_amd64.deb ccbc4e7486eae13b03263591a690e3ec 246446 text optional refdb-server_1.0.0-1_amd64.deb 5571beaa82affaa61e5f85090a9092df 78442 text optional refdb-www_1.0.0-1_all.deb 6011cd9eb6a2dd28a5b9b77d73504a9d 1450032 doc optional refdb-doc_1.0.0-1_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBAgAGBQJS4+/LAAoJEAFx4YKK4JNF+hQP+wXejl8BLGsYdANo7JM9Qiqu CqXDSeszJ7XofW5VToqQE5G+AlNXNVfOF8C47p4/GXstGq16ANFvkO12zf2LMFvn VtKHRJkgKJTq1GuQXXv0h2quP51gNuxZg2L7ORsFDXzIACyeU95dVPL4v0RKRnR6 zywZdxh5cMcp9Xmf/nWNx2I6vdsBPyJN91JBr+VkYTyTI2JzUG78KKuKh63FjVI8 64su34wsgn4JKPcBJrjGg4hXWcO9YjOb1bFlNU+C0dWShPghmnoxNcSRehS01mxJ yDd3/Ggg3UjfXtwcZVGE0X0SAH8zg8nQ+SLIgrXaqj9JERi/L+262UswViU+Arui gUIY4FyGKZLzvtj8yviNUObz5HQR4HFtVensD4szJpK/xAlrQqYsCgWDl8ITxNQm SXlw9UzzrhSeNn1sjq0bDsWb43skbjGeiIMZq19LvtUk7WMP5UKwLYQ3ZkTFIe7/ Rpcn5XQe+RqZjiHCUWCnfcObsYCRH3VU1SsbC0oSjKfVf1dXk1CluN4sQHw4yR6L ZL4oqQlGckLzreV6+c32F4eaJlAzrvbYRKX1aBgmmVHkr2dt+Qr3AFHxreuy3Mbp RHlVYovfkPlcdSsy/2zkWpzv038buB3wzUj1QyEaVnCl7tjUQ8p38cNJS+gH2bWT JVq5HAzxPClK75ojAo9j =mu3X -----END PGP SIGNATURE-----
--- End Message ---
