Bug#753821: closed by atzlinux (bugreport is too old)

2020-05-06 Thread atzlinux 肖盛文
Control:  tags moreinfo Package: eject Version: 2.1.5+deb1+cvs20081104-15 This new version is not for Buster,but for bullseye.If you has chance,I hope test this new eject version on testing(bullseye). The orig bugreport had reported for many years ago,almost all of things is changed. It's no

Bug#753821: closed by atzlinux (bugreport is too old)

2020-05-06 Thread Steve McIntyre
Control: reopen -1 Ummm, no. You don't understand how this works it seems. Please do *not* just close bugs without checking if the bug is actually closed. I've just tested on a current Buster amd64 system and the bug is still there, just as described. On Thu, May 07, 2020 at 12:45:17AM +0800, at

Bug#753821: closed by atzlinux (bugreport is too old)

2020-05-06 Thread atzlinux 肖盛文
Hi,Steve McIntyre: There are some type errors in my last email,sorry! I write again: Please use reportbug to report it again. The code isn't change,this is true.But others all changed,hardware,kernel,OS,etc,. So,this bug close at first. 在 2020/5/7 上午12:45, atzlinux 肖盛文 写道: > please use bugrep

Bug#753821: closed by atzlinux (bugreport is too old)

2020-05-06 Thread atzlinux 肖盛文
please use bugreport to report it again. The code isn't change,this it true.But others all changed,hardware,kernel,OS,etc,. this bug close at first. 在 2020/5/6 下午8:39, Steve McIntyre 写道: > Control: reopen -1 > > Sorry, not good enough - you don't get to close a bug just because > it's "too old"

Bug#753821: closed by atzlinux (bugreport is too old)

2020-05-06 Thread Steve McIntyre
Control: reopen -1 Sorry, not good enough - you don't get to close a bug just because it's "too old". The code hasn't changed and still has the same problem; I've just looked in your latest upload. Steve On Sat, May 02, 2020 at 01:51:03AM +, Debian Bug Tracking System wrote: >This is an auto