Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1022483

Bug#842626:

From Samuel Thibault <sthibault@debian.org>
Newsgroups linux.debian.bugs.dist, linux.debian.maint.boot
Subject Bug#842626:
Date 2020-08-23 10:30 +0200
Message-ID <AGTy1-45o-1@gated-at.bofh.it> (permalink)
References (5 earlier) <sy5Gh-1vU-3@gated-at.bofh.it> <AGSiB-3qH-3@gated-at.bofh.it> <AGTeF-3YU-3@gated-at.bofh.it> <sy5Gh-1vU-3@gated-at.bofh.it> <AGTeF-3YU-3@gated-at.bofh.it>
Organization I am not organized

Cross-posted to 2 groups.

Show all headers | View raw


Geert Stappers, le dim. 23 août 2020 09:57:23 +0200, a ecrit:
> He is preventing that (potential) developers get tired
> by seeing again and again bug reports no one cares about.

? I don't understand the logic.

If a bug is raised again and again, that should raise developers'
attention. Agree here I seem to be alone raising the concern. I tend to
think that my colleague wouldn't be alone making the mistake, and we
just do not get the grumbling signal of people realizing after
installation that they got a 32bit system, and will just think "bleh,
dumb Debian again" and not bother making a report.

> Samuel please respect the work of Holger Wansing and leave this BR closed and
> > > > If you know, that the issue you reported (and gets closed here) is still existing
> > > > in recent installation images, please file a new report for that!

I even less understand the logic. Yes, the bug is still existing: the
installer doesn't warn about installing 32bit on 64bit. But reporting
a new bug report would leave the old one unseen. And it'd then be even
less informative: with the new bug report only we would not remember
that nobody took the care to implement it while it was reported 4 years
ago.

> The win-win-win situation is
> * There is a BR that i386 image checks for amd64 host and informs user about it
> * Holgers good work is respected
> * BTS has only open BR that deserve attention, which keeps developers
>   motivated to check BTS for what needs to be done

I completely support Holgers' good work, that's not the question!

But point 3 contradicts what you wrote above: not having the information
that the bug was already reported 4 years ago gives a wrong signal to
developers: possibly we don't actually want to spend time implementing
it, and just re-filing a bug report "just because yes it is still not
implemented" gives a wrong priority signal.

Samuel

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Mass-closing old installation-report bugs Holger Wansing <hwansing@mailbox.org> - 2020-08-04 00:10 +0200
  Re: Mass-closing old installation-report bugs  ---  round 2 Holger Wansing <hwansing@mailbox.org> - 2020-08-05 00:10 +0200
  Re: Mass-closing old installation-report bugs  ---  round 4 Holger Wansing <hwansing@mailbox.org> - 2020-08-07 23:50 +0200
  Re: Mass-closing old installation-report bugs  ---  round 6 Holger Wansing <hwansing@mailbox.org> - 2020-08-22 22:40 +0200
    Bug#842626: closed by Holger Wansing <hwansing@mailbox.org> (Re: Mass-closing old installation-report bugs  ---  round 6) Samuel Thibault <sthibault@debian.org> - 2020-08-22 22:50 +0200
      Bug#842626: closed by Holger Wansing <hwansing@mailbox.org> (Re: Mass-closing old installation-report bugs  ---  round 6) Holger Wansing <hwansing@mailbox.org> - 2020-08-23 09:10 +0200
        Bug#842626: closed by Holger Wansing <hwansing@mailbox.org> (Re: Mass-closing old installation-report bugs  ---  round 6) Samuel Thibault <sthibault@debian.org> - 2020-08-23 10:20 +0200
        Bug#842626:  Samuel Thibault <sthibault@debian.org> - 2020-08-23 10:30 +0200
          Bug#842626: Having history is good Geert Stappers <stappers@debian.org> - 2020-08-23 13:30 +0200
          Bug#842626:  Richard Hector <richard@walnut.gen.nz> - 2020-08-23 14:50 +0200
  Re: Mass-closing old installation-report bugs  ---  round 7 Holger Wansing <hwansing@mailbox.org> - 2020-08-30 14:00 +0200

csiph-web