Vincent Lefevre wrote on Fri, 12 Dec 2025 02:05 +00:00: > On 2025-12-12 00:28:17 +0100, Michael Prokop wrote: >> Hi, >> >> * Vincent Lefevre [Thu Dec 11, 2025 at 01:22:17PM +0100]: >> >> > Forwarded: https://www.zsh.org/mla/workers/2025/msg00816.html >> > >> > The zshexpn(1) man page says: >> [...] >> >> Thanks for reporting this towards upstream. >> >> Is there any specific reason why we should track this - AFAICT >> very minor issue - also within Debian's BTS? > > The issue is that upstream does not have a bug tracker, and > this makes difficult to know which versions are affected, > and which bugs need to be tested to check whether they are > still there in Debian.
Upstream does have the Etc/BUGS file to track bugs in. Why don't you help maintain it? Or if you want to help upstream set up some less-barebones bug tracker, something that can track "affected versions" metadata too, I'm sure upstream's -workers@ and -infra@ would be happy to have you on board. Cheers, Daniel (upstream hat on) > Note that though this bug probably occurs very rarely, it can > introduce obscure incorrect behavior in scripts. > >> I'm asking, because our list of open bugs at >> https://bugs.debian.org/zsh is already quite long, as you might be >> aware of, and AFAICS ~32 of those bug reports got submitted by you. >> >> The current maintainers of pkg-zsh are quite overloaded already, so >> any assistance in improving the actual situation would be very >> welcome. Given your track record, maybe you wanna join us? :) > > I check old bugs from time to time (in particular when there > are new versions of packages, but which hasn't happened for a > long time concerning zsh).
