Your message dated Thu, 15 Feb 2018 05:49:38 +0000 with message-id <e1emcqm-00056g...@fasolo.debian.org> and subject line Bug#890421: fixed in chocolate-doom 3.0.0-4 has caused the Debian Bug report #890421, regarding chocolate-doom: Bash autocomplete starts the game 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.) -- 890421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: chocolate-doom Version: 3.0.0-3 Severity: normal Dear Maintainer, When I'm using autocomplete in Bash for a chocolate-doom/heretic/hexen/strife command line (e.g. to complete the file name for the -iwad option) the game is launched by Bash with the following command: `chocolate-xxx - historically compatible xxx engine`, where `xxx` is the game name. The parameters entered up to that point are not passed to the executable. After exiting the game (or dismissing the 'iwad file missing' dialog), the autocomplete finishes as usual. Expected behavior: I would expect Bash to either suggest files as usual, or to restrict the output in some way depending on the last entered command line parameter (e.g. restrict suggested files to *.wad and *.WAD for the -iwad option). Autocomplete should not start the game in the normal way. Minor nitpick: I also noticed that when launching Strife in this way, the resulting command line is `chocolate-strife - historically compatible strife engine`. Here the game title is not capitalised, while the title is capitalised for the other games. Bash version used: GNU bash 4.4.12(1)-release (x86_64-pc-linux-gnu) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chocolate-doom depends on: ii libc6 2.26-4 ii libpng16-16 1.6.34-1 ii libsamplerate0 0.1.9-1 ii libsdl2-2.0-0 2.0.7+dfsg1-3 ii libsdl2-mixer-2.0-0 2.0.2+dfsg1-2 ii libsdl2-net-2.0-0 2.0.1+dfsg1-3 Versions of packages chocolate-doom recommends: ii freedm 0.11.3-1 chocolate-doom suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: chocolate-doom Source-Version: 3.0.0-4 We believe that the bug you reported is fixed in the latest version of chocolate-doom, 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 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Greffrath <fab...@debian.org> (supplier of updated chocolate-doom 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: SHA256 Format: 1.8 Date: Wed, 14 Feb 2018 22:16:30 +0100 Source: chocolate-doom Binary: chocolate-doom chocolate-common Architecture: source all amd64 Version: 3.0.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Games Team <pkg-games-de...@lists.alioth.debian.org> Changed-By: Fabian Greffrath <fab...@debian.org> Description: chocolate-common - dummy transitional package for chocolate-doom related packages chocolate-doom - Doom engines closely-compatible with Vanilla Doom Closes: 890421 Changes: chocolate-doom (3.0.0-4) unstable; urgency=medium . * Backport patch from upstream GIT to build bash-completion from actual shell script templates (Closes: #890421). * Bump debhelper compat to 11. * Bump Standards-Version to 4.1.3. * Use secure debian/copyright format URI. Checksums-Sha1: 308a7a5b475bd7ec1c81a2352edb927e81520927 2242 chocolate-doom_3.0.0-4.dsc 48a92efb57ebcc3907b39de2e8ec9f58fb1ab105 19436 chocolate-doom_3.0.0-4.debian.tar.xz 55e3a62687c3b7a0b209c4f867d9207d1b137188 31184 chocolate-common_3.0.0-4_all.deb 450b0d50145c0931ef962892cde56c86ca4f1eb6 4493620 chocolate-doom-dbgsym_3.0.0-4_amd64.deb 76ef4147cb92be02556cc856f9ba7deb4b7236ce 11699 chocolate-doom_3.0.0-4_amd64.buildinfo cea799277b62a4356c53d97267f9bb7b9fe2c63c 918972 chocolate-doom_3.0.0-4_amd64.deb Checksums-Sha256: 40d102f12378bf8ebf629f3ba650c0f276c7044f07a1f374f03efda1951f6229 2242 chocolate-doom_3.0.0-4.dsc cd9ce31f48be6f0903ab1c8fc7b19a5f5b0fa80aaf0f8df85a8d9d62f441ec2f 19436 chocolate-doom_3.0.0-4.debian.tar.xz 6a9ccbea7a69d30f00b3607167face6575a59f0c91eec5f8f603f0432098a504 31184 chocolate-common_3.0.0-4_all.deb ff298c998f98ef4185034001b18d0bc1341829e595e6c1edbf67ffc846150ffe 4493620 chocolate-doom-dbgsym_3.0.0-4_amd64.deb f34fa0e8d2be13f5cfb731e5ff11b5121f01654594d19f6bf49db33144c64c87 11699 chocolate-doom_3.0.0-4_amd64.buildinfo bde7007977bd8898f8063eb4d564d9f5c806a323e5a1d134c7b507be74104921 918972 chocolate-doom_3.0.0-4_amd64.deb Files: 42cf07254a883e0118a8782a0960b5e6 2242 games optional chocolate-doom_3.0.0-4.dsc d85a3ae1e85fb04683206e765dc1a6e0 19436 games optional chocolate-doom_3.0.0-4.debian.tar.xz c32132244ebed4c68bad7b5e52119a06 31184 oldlibs optional chocolate-common_3.0.0-4_all.deb 75e5a2983f3bc0eabbf64839ae468049 4493620 debug optional chocolate-doom-dbgsym_3.0.0-4_amd64.deb 76707a42fc7dd5181d542f0547413d65 11699 games optional chocolate-doom_3.0.0-4_amd64.buildinfo 02865267169a9eed65db401971261022 918972 games optional chocolate-doom_3.0.0-4_amd64.deb -----BEGIN PGP SIGNATURE----- iQJGBAEBCAAwFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAlqFGx0SHGZhYmlhbkBk ZWJpYW4ub3JnAAoJEMvqjpcMzVnfYUMP/j6aBlKgNTKgKOAqyQliZNjEXPryKR+0 aZePfjULyz83X6U9tsfchfzdazkgm1Q1btlUzJKZVtvr2aDtL4TLiAtCuadjWPZo iBCd09ec/KaS2cmPrxB4CSOPXRBOS5YOZrearYDdL7SPJ8soA0fKEOOYmU6KB4ZS f/nFuyKxPVUp0ZpGOek7HESe8fHXLEk/dcLeuvyAac7jGTS4oGc6cHpol+XKRiwL Uk/rrdhrBLSaM125f2b4zZvM+g7MRoUosb51wSiaafxbB6bkS40kYX5cRi3KOkmp cF0eGw3tNC3f5MYxbbEfuDWdZu5fHczKtXU2VqrPtF48jSxnGBOH6iU61ucoTw/c Kd8f9FzitWmFABRbAU/HVeRGqxLt71RCjPmHMQg+uiZXYYJ2jIXj7jydga27Khhe 9hRCvWB1+FazF7M1hoDndjvv36KZDTBq5PKMDrICvvEjFyDkSMR1DxjFfJboPAUk 1EhoV/+PP8MMv/KvhW4bYp6SbG2gCSHtI3XgqBK1OOpY2mTnt6QjWvAUXxMzVv7v HbZjRJyFQ/Buhi2wq8r98g+3mCw2S833TeWCS89m2Tn/gPRV1ihBlXlhAwLfbZQo pWgrCbLtxi9BcjgVkOYdJAg35f7ZlRM8GcCN0USWFRrjCVIMs9ujUJaXvnh5UHWn PDnSrVnSS8rI =vZk+ -----END PGP SIGNATURE-----
--- End Message ---
