Devuan bug report logs -
#807
reportbug: should submit bug reports to Devuan & indicate distribution
Reported by: Ansgar <ansgar@debian.org>
Date: Mon, 27 Nov 2023 19:36:01 UTC
Severity: grave
Found in version 12.0.0+devuan2
Fixed in version 12.0.0devuan3
Done: dak@devuan.org
Reply or subscribe to this bug.
Toggle useless messages
Report forwarded
to devuan-bugs@lists.dyne.org, Mark Hindley <mark@hindley.org.uk>
:
bug#807
; Package reportbug
.
(Mon, 27 Nov 2023 19:36:01 GMT) (full text, mbox, link).
Acknowledgement sent
to Ansgar <ansgar@debian.org>
:
New bug report received and forwarded. Copy sent to Mark Hindley <mark@hindley.org.uk>
.
(Mon, 27 Nov 2023 19:36:02 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):
Package: reportbug
Version: 12.0.0+devuan2
Severity: grave
Devuan's reportbug must be fixed to
1) Submit bug reports to Devuan's bug tracker. Also for packages not
modified by Devuan as the environment matters. For example, Devuan uses
split-/usr which Debian no longer supports and which causes noise in
Debian's bug tracker.
(This is the same for all derivatives, for example Ubuntu reports bugs
to Launchpad.)
2) Include proper and honest information about the distribution. [1]
has no indication it is not from Debian except for the "X-Reportbug-
Version" header; in [2] there are also package versions with "devuan".
This makes investigating bugs hard.
Thanks,
Ansgar
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057002;msg=5
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057000;msg=5
Information forwarded
to devuan-bugs@lists.dyne.org
:
bug#807
; Package reportbug
.
(Tue, 28 Nov 2023 15:36:45 GMT) (full text, mbox, link).
Message #8 received at 807@bugs.devuan.org (full text, mbox, reply):
Ansgar,
Thanks for this.
I think you may misunderstand what Devuan's reportbug does.
By default it reports to Devuan's BTS.
For unforked packages it asks the user which BTS to use (whilst still defaulting to
Devuan).
The reportbug System Information identifies the Distribution as Devuan.
What more do you suggest?
Thanks and best wishes
Mark
Information forwarded
to devuan-bugs@lists.dyne.org, Mark Hindley <mark@hindley.org.uk>
:
bug#807
; Package reportbug
.
(Tue, 28 Nov 2023 20:00:01 GMT) (full text, mbox, link).
Acknowledgement sent
to Ansgar <ansgar@debian.org>
:
Extra info received and forwarded to list. Copy sent to Mark Hindley <mark@hindley.org.uk>
.
(Tue, 28 Nov 2023 20:00:53 GMT) (full text, mbox, link).
Message #13 received at 807@bugs.devuan.org (full text, mbox, reply):
Hi,
On Tue, 2023-11-28 at 15:34 +0000, Mark Hindley wrote:
> Thanks for this.
>
> I think you may misunderstand what Devuan's reportbug does.
>
> By default it reports to Devuan's BTS.
>
> For unforked packages it asks the user which BTS to use (whilst still
> defaulting to Devuan).
It should recommend users to file the bug report with Devuan if they
are not sure whether it is not a Devuan-specific bug or not. This is
recommended by Debian's derivative guidelines[1], though AFAIU Devuan
often does the opposite:
+---
| For distributions that modify core or non-leaf packages
| (especially libraries), it is recommended to redirect all bug
| reports to your distribution's tracker.
| [...]
| For distributions that modify configuration in ways that affect
| other packages, it is recommended to redirect all bug reports to
| your distribution's tracker.
+---
[1]: https://wiki.debian.org/Derivatives/Guidelines#Bug_reports
As Devuan introduces major differences like split-usr, it is
increasingly likely that a large class of issues will only happen on
Devuan, but not Debian.
> The reportbug System Information identifies the Distribution as
> Devuan.
It does not. From the bug report I referenced in the initial mail:
+---
| -- System Information:
| Debian Release: trixie/sid
| APT prefers experimental
| APT policy: (1, 'experimental')
| merged-usr: no
| Architecture: amd64 (x86_64)
| Foreign Architectures: i386
+---
which does not say "Devuan" anywhere, except in the header "X-
Reportbug-Version: 12.0.0+devuan2" and some package versions which
include "devuan".
It might be a bug when the report is submitted to Debian's BTS instead
of Devuan's BTS. No idea.
Ansgar
Information forwarded
to devuan-bugs@lists.dyne.org
:
bug#807
; Package reportbug
.
(Wed, 29 Nov 2023 17:02:01 GMT) (full text, mbox, link).
Message #16 received at 807@bugs.devuan.org (full text, mbox, reply):
Control: tags -1 pending
Ansgar,
On Tue, Nov 28, 2023 at 08:59:11PM +0100, Ansgar wrote:
> It might be a bug when the report is submitted to Debian's BTS instead
> of Devuan's BTS.
Indeed this was correct: we need not to use debian_infofunc() in this case.
Thanks for pointing it out.
Mark
Added tag(s) pending.
Request was from Mark Hindley <mark@hindley.org.uk>
to 807-submit@bugs.devuan.org
.
(Wed, 29 Nov 2023 17:02:03 GMT) (full text, mbox, link).
Information forwarded
to devuan-bugs@lists.dyne.org, Mark Hindley <mark@hindley.org.uk>
:
bug#807
; Package reportbug
.
(Wed, 29 Nov 2023 17:24:01 GMT) (full text, mbox, link).
Acknowledgement sent
to Ansgar <ansgar@debian.org>
:
Extra info received and forwarded to list. Copy sent to Mark Hindley <mark@hindley.org.uk>
.
(Wed, 29 Nov 2023 17:24:02 GMT) (full text, mbox, link).
Message #23 received at 807@bugs.devuan.org (full text, mbox, reply):
On Wed, 2023-11-29 at 17:01 +0000, Mark Hindley wrote:
> On Tue, Nov 28, 2023 at 08:59:11PM +0100, Ansgar wrote:
> > It might be a bug when the report is submitted to Debian's BTS
> > instead
> > of Devuan's BTS.
>
> Indeed this was correct: we need not to use debian_infofunc() in this
> case.
>
> Thanks for pointing it out.
Thanks for fixing this.
Ansgar
Reply sent
to dak@devuan.org
:
You have taken responsibility.
(Wed, 29 Nov 2023 17:34:02 GMT) (full text, mbox, link).
Notification sent
to Ansgar <ansgar@debian.org>
:
bug acknowledged by developer.
(Wed, 29 Nov 2023 17:34:04 GMT) (full text, mbox, link).
Message #28 received at 807-done@bugs.devuan.org (full text, mbox, reply):
Version: 12.0.0devuan3
Source package reportbug (12.0.0devuan3) added to Devuan suite unstable.
This closes bug report 807.
Thanks
DAK managing the Devuan archive
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 29 Nov 2023 17:03:42 +0000
Source: reportbug
Architecture: source
Version: 12.0.0devuan3
Distribution: unstable
Urgency: medium
Maintainer: Mark Hindley <mark@hindley.org.uk>
Changed-By: Mark Hindley <mark@hindley.org.uk>
Closes: 807
Changes:
reportbug (12.0.0devuan3) unstable; urgency=medium
.
* Add new BTS desktop-live pseudopackage.
* Don't use debian_infofunc() for unforked reports to Debian to ensure
system is correctly identified. (Closes: #807)
* Clarify question about sending unforked package reports to Debian.
Checksums-Sha1:
87254d4020a7f4795a8f8176d04d9590f093b746 1523 reportbug_12.0.0devuan3.dsc
c9b042cb2deb0e0b55bb80ae2b216d4926b208e6 216060 reportbug_12.0.0devuan3.tar.xz
efb0339254587ea717da8fc1070cb2d7556892d0 5793 reportbug_12.0.0devuan3_source.buildinfo
Checksums-Sha256:
74cae58e53738acdb9cffb87476e2dc3fa11fd592ff19e197315ef0df78a05d2 1523 reportbug_12.0.0devuan3.dsc
7f827b4ba4d81349f077554de7c32d41ad40e36ccf344be76e519619fedfb1a2 216060 reportbug_12.0.0devuan3.tar.xz
0db3458bc265b0033f898b0eb21d83e108a95f9d04ef4c22d5b75e5a0e7d4c0d 5793 reportbug_12.0.0devuan3_source.buildinfo
Files:
7b3f695d115aebc285782df9ea2ea807 1523 utils standard reportbug_12.0.0devuan3.dsc
01acf972a40a15846899411ec9296c7b 216060 utils standard reportbug_12.0.0devuan3.tar.xz
475d7cc95ae89704fa8fcfcb0ca491d5 5793 utils standard reportbug_12.0.0devuan3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQEyBAEBCgAdFiEEcuPLdzMV36LkZHQ9lFMhJFQZIvsFAmVndU0ACgkQlFMhJFQZ
IvvTwAf46ty7Ju0Q+DiMFOjRaGytZq0fpcrtw6meD6eAa1yPUBiWR2X+u8UVy2B0
LfEMeC5cXAF3exJP0HsykSLlzY/JFDbzUbmDU87+V8Qu+eG2ks6U/N5BIHj062k6
EAXMbNsFJmeAqCPc+V88/KxdYrIYAvtY5tqYad2UXiBAb+nZ4aWMgwlmvJzY7oyP
kCg1GUzKaqj+igNzW1HnN0PKyM76xoq2UAzTK85rHRUgidIHMOqEjnvX9bUFWXib
U2/4wvRGYgav2TzQGCMZd27WIu1fjON7kkutrhGTPt+rqnuJUd6KnnPPiAMr3OPj
mLfJ6oMu/iushX08PFQt13p5nNOZ
=WeHV
-----END PGP SIGNATURE-----
Send a report that this bug log contains spam.