Your message dated Sat, 19 Nov 2022 22:10:32 +0000
with message-id <[email protected]>
and subject line Bug#999754: fixed in tcsh 6.21.00-2
has caused the Debian Bug report #999754,
regarding tcsh: character class expansion is badly broken
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 [email protected]
immediately.)
--
999754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999754
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tcsh
Version: 6.21.00-1.1
Severity: grave
Tags: newcomer
Justification: causes non-serious data loss
Dear Maintainer,
tcsh does not respect character classes. Minimal example:
$ mkdir a
$ touch a/a a/B
$ echo a/[a-z]
a/a a/B
I expect the result to simply be 'a/a' since 'B' is not in [a-z]. The behavior
generalizes to character classes in wildcards - it is not just about the
trivial one-character filename example seen here.
This is in locale en_US.UTF-8, but switching to locale "C" has the same
behavior.
This behavior can result in data loss with e.g. 'rm [a-z]*' removing unexpected
files, and can also result in operating on the wrong files, so I have
tentatively
classified it 'grave'. tcsh as packaged is unusable for my purposes.
I have verified that tcsh built from the current upstream (version 6.23.00)
with
$ git clone [email protected]:tcsh-org/tcsh.git
$ cd tcsh
$ configure && make
Does NOT suffer this behavior, while tcsh built from the Debian source package
with
$ apt-get --build source tcsh
DOES suffer this behavior. The 6.23.00 built from upstream has the same
$version
string options as the Debian 6.21.00 except for "nd" (NODOT).
I attempted to build from the upstream repository at version 6.21.00 but could
not successfully build after 'configure', so I cannot tell if this is a bug
introduced by the Debian-specific changes, or a bug in the upstream 6.21.00.
The differences between the Debian source package with patches applied vs.
upstream 6.21.00 source are smallish and don't obviously implicate character
classes but that proves nothing.
Suggested resolutionn is to update the buster package to tcsh 6.23.00. I
believe
this will also result in elimination of a large number of warning messages
during
the build of form
/usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use
_DEFAULT_SOURCE"
| ^~~~~~~
-- System Information:
Debian Release: 11.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages tcsh depends on:
ii libc6 2.31-13+deb11u2
ii libcrypt1 1:4.4.18-4
ii libtinfo6 6.2+20201114-2
tcsh recommends no packages.
tcsh suggests no packages.
--- End Message ---
--- Begin Message ---
Source: tcsh
Source-Version: 6.21.00-2
Done: Adrian Bunk <[email protected]>
We believe that the bug you reported is fixed in the latest version of
tcsh, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk <[email protected]> (supplier of updated tcsh 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 19 Nov 2022 23:13:18 +0200
Source: tcsh
Architecture: source
Version: 6.21.00-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Adrian Bunk <[email protected]>
Closes: 999754 1020064
Changes:
tcsh (6.21.00-2) unstable; urgency=medium
.
* QA upload.
* Set Maintainer to Debian QA Group. (see #1019858)
* Add upstream fix for FTBFS with bash 5.2. (Closes: #1020064)
* Add upstream fix for range comparison bug. (Closes: #999754)
Checksums-Sha1:
4ae67768a0c22ca78b7045f1f7e0a15eee003082 1802 tcsh_6.21.00-2.dsc
1f6fd47ee6e525e998068127a578234682def87c 24980 tcsh_6.21.00-2.diff.gz
Checksums-Sha256:
141e325b24be90b9f35eb390ef2d7b110d608135542679983ebd439c9ef59801 1802
tcsh_6.21.00-2.dsc
ad73f0dd65b0d224ed1cc14a5f9b4506ee805711c30e3c034db32516ce4e55a6 24980
tcsh_6.21.00-2.diff.gz
Files:
a973a14bc784207670908c3c4954c23b 1802 shells optional tcsh_6.21.00-2.dsc
40f3e929319f02f9b09c581a68356dad 24980 shells optional tcsh_6.21.00-2.diff.gz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmN5SmAACgkQiNJCh6LY
mLGqpw/7BhkqIfPwf2Q1tVVsR+lERWsloxNkyJXwLHEFWoIN16D776dXbLKpEHEx
LLCi/yrJd2bmgR8m2v5k9Moz0kug7u/ZCZaL2Dx1z7XC7p5h0YBEVmXKxnGA8/SV
duJhny585tmoShLbToNTgTrIXvR8ybHLgwBQpErga78E1NOpTYbXejlSHU4K7CM7
cuBWodRJpkq2P63Rj9o6XuctWu+Y6ksbTzHkyJc/1LPJNDaJZoRZO8+BcHh5F5DL
+RNMZJVb5i36DxFVUYDmC+KP6nvauDFQxrHJ6EF7GUaOQ90T60FOY/TotoTNs/Br
OcJbhfv32x1azh750eyoxQ4Q5R0BT0Td/BSg9bw+Ko/KTpGPfm2KA8ILt7wIkVc5
+KDbJ4m7ojGF3Q1+uZkQ1vra+UfnFFEeISz5yEmurQTryKT7FqHHDbMJWLiq0NPO
l2n4kRSVw5T2rhY7U1JmTYNMfpKUvWxPs5AYJZalA8C0FDh/ofile/o5v7MfvSW5
juQc3dIEyU9+zDOzE682xyEfbYpYgPgUJ/VibOe39CBTL2n6Y8XtUUibjoqt1OPd
JEDsvqyp9d+O/5R9CE2Nyowyuh0gfX3d3UXprDOIDQJUOdyuMZ7kYYqeG6SahzkQ
8GNl30d5yJIRw/pceh7j1e/v5S9Vgnrxkz6afguApDBVph1+TzY=
=MwwV
-----END PGP SIGNATURE-----
--- End Message ---
