Control: reopen -1 Control: tags -1 unreproducible moreinfo Control: severity -1 normal
If 3.1.0+dfsg1-4 doesn't have any changes from 3.1.0+dfsg1-3, why was it uploaded? That uses additional mirror space and rebuilds all of the packages. It also marks the bug as fixed in 3.1.0+dfsg1-4. Instead, if a bug isn't being fixed by a new upload, send the reason you're closing it to 940463-done@b.d.o with a Version: header reflecting if a version does have a fix. > As my last e-mail tells, I "Checked that falkon-3.1.0+dfsg1-3 does not > crash", which can be considered as being unable to reproduce the bug. Bugs shouldn't be closed solely for being unreproducible. Instead, add the tags and contact the submitter. I see you might've been desperate to get Falkon back into testing since the upload was the same day it was removed. Bugs serious, grave, and critical cause removal, so I've downgraded the bug to normal. > I got no reply from Xeno Idaltu <xenoida...@gmail.com>, so I believe > that either he is not using falkon again, or he installed falkon's new > package and found the bug fixed. Did you reply to him separately from the bug report? The log doesn't show anyone reaching out to him. Additionally, I'm curious about this changelog entry > falkon (3.1.0+dfsg1-5) unstable; urgency=medium > * removed the dependency on libgnome-keyring-dev, since this package > is no longer part of Debian. Together with the upstream version > change, this ... Closes: #943769 since #943769 doesn't appear to be related to GNOME Keyring. I am also seeking to know why 3.1.0+dfsg1-3 has a +dfsg1-3 since the prior uploads were 3.0 and didn't have the +dfsg1. I haven't been able to find the reason for the change documented. I haven't been able to reproduce the bug. However, I hope my suggestions are helpful for you and that I'll be able to help Falcon in this way. Sincerely, John Scott
signature.asc
Description: This is a digitally signed message part.
