On Sun, Jan 19, 2014 at 11:14 AM, John Paul Adrian Glaubitz <glaub...@physik.fu-berlin.de> wrote: > On 01/19/2014 10:23 AM, Sandro Tosi wrote: >> (and you tell the reportbug maintainer?) > > What does this have to do with the maintainer of reportbug? reportbug is > just the utility used to report canonical bug reports.
that means I may know a thing or two about bug reporting, what's a bug and what's not. >> don't judge too quick: the >> fact that there was an error during installation doesn't mean there >> was anything wrong on my part, only a series of situations which lead >> there without being able to replicate it. think before you preach. > > Several people were unable to reproduce it and you couldn't provide > any more useful information either. like what, reproduce a dist-upgrade? > It's definitely a bug when it occurs during a fresh installation and > might be considered a bug if it happens for certain dist-upgrades. > Both don't seem to be the case. it is a bug even if it occurs in a weird upgrade path, which is near-to-impossibile to reproduce, but it can be decided to be "ignored" that given the time required to have a clue about how to reproduce it. > If you are able to reliably reproduce the problem, please feel free > to re-open this bug report. if you know a way to "reliably reproduce" the upgrade path that generated the problem, please tell. Mind you, I'm not against the bug closing, but the preaching which came with it. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
