Devuan bug report logs - #476
reportbug and the server interface aren't fluffy

Package: reportbug; Severity: wishlist; Reported by: Jens Korte <>; Keywords: upstream; dated Sat, 23 May 2020 15:03:02 UTC; Maintainer for reportbug is Mark Hindley <>.

Message received at

Received: (at 476) by; 23 May 2020 15:20:03 +0000
Return-Path: <>
Received: from []
	by with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Sat, 23 May 2020 15:20:03 +0000 (UTC)
Received: from ( [])
	(using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits))
	(No client certificate requested)
	by (Postfix) with ESMTPS id F32E7F60D3D
	for <>; Sat, 23 May 2020 17:11:46 +0200 (CEST)
	dkim=pass (2048-bit key; secure) header.b="W9ucH3k3";
	dkim=pass (2048-bit key) header.b="D1JePDjV";
Received: from ( [])
	(using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits))
	(No client certificate requested)
	by (Postfix) with ESMTPS id 49TmzQ2qt0zKmcr
	for <>; Sat, 23 May 2020 17:11:46 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; h=
	:message-id:subject:subject:from:from:date:date:received; s=
	mail20150812; t=1590246703; bh=7taCYw/pmI5/6L5dRDz8Vsd0aV0cMRZ3b
	4P87BsxPo8=; b=W9ucH3k360iZNKVJMfKoyu8KQB3t/eYuYodZ7iOTxl6QZqepO
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=mail20150812;
X-Virus-Scanned: amavisd-new at
Received: from ([])
	by ( []) (amavisd-new, port 10030)
	with ESMTP id ls41tgzKkGDI for <>;
	Sat, 23 May 2020 17:11:43 +0200 (CEST)
Date: Sat, 23 May 2020 17:11:42 +0200
From: Jens Korte <>
Subject: additional features
Message-ID: <20200523171142.3d938b3f@devuan>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: 659C4175A
X-Rspamd-Score: -4.16 / 15.00 / 15.00
X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on

* reportbug --browser <package> should open the webinterface for
  reporting bugs with pasting the additional data for debugging into
  the browser
* if I download and compile a package by hand it would be nice if I
  could use the bug reporting tool like reportbug <filename> and
  reportbug recognizes that the file isn't covered by a package from
  the distribution and searches for a .reportbug.cfg in the current and
  all upper dirs and reports the bug to the configured bug server.
  Of course the .reportbug.cfg should come with the .tgz file I
  downloaded or with the git clone command.

Acknowledgement sent to Jens Korte <>:
Extra info received and forwarded to list. Copy sent to Devuan Developers <>. Full text available.
Information forwarded to, Devuan Developers <>:
bug#476; Package reportbug. Full text available.

Message received at

Received: (at submit) by; 23 May 2020 15:00:02 +0000
Return-Path: <>
Received: from []
	by with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Sat, 23 May 2020 15:00:02 +0000 (UTC)
Received: from [] ( [])
	by (Postfix) with ESMTP id DC65AF60D27
	for <>; Sat, 23 May 2020 16:51:49 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Jens Korte <>
To: Devuan Bug Tracking System <>
Subject: reportbug and the server interface aren't fluffy
Message-ID: <159024550933.15492.17108049949084898751.reportbug@devuan>
X-Mailer: reportbug 7.5.3+devuan3
Date: Sat, 23 May 2020 16:51:49 +0200
X-Spam-Status: No, score=4.8 required=5.0 tests=HELO_MISC_IP,KHOP_DYNAMIC,
	RCVD_IN_PBL,RDNS_DYNAMIC,SPF_NEUTRAL autolearn=disabled version=3.4.2
X-Spam-Level: ****
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on

Package: reportbug
Version: 7.5.3+devuan3
Severity: wishlist
Tags: upstream

Dear Maintainer,

   * What led up to the situation?
Trying to report #474 and #475 at devuan I got problems with reportbug
and the lacking possibility of forwarding a bug upstream. If I compare
the webinterface of gitlab/github for issues with reportbug and the
webinterface I judge the devuan/debian solution as some steps behind.

   * What exactly did you do (or not do) that was effective (or
I used the link at to have a
workaround to report an upstream bug to debian.

   * What was the outcome of this action?
It worked.

   * What outcome did you expect instead?
An easier and faster solution to report bugs, forward bugs upstream and
a project independent solution and standard for bugs. If a bug is referred by #bugnr
it should be replaced by a link in the webinterface.

Don't get me wrong, the bug reporting system is working, but it lacks
some features I got used to from other systems. The feature of creating
bugs offline and reporting it using a slow connection is still valuable.

## Some buzzwords I would like to see supported:

* a project independet XML standard for describing a bug
* forwarding a bug upstream/rejecting downstream
* connecting two bug reports on different server as if it was one
* splitting and joining bugs
* support for markdown
* webinterface with and without user registration
* support for offline/dial-in connections
* the choice to replace mail by XMPP
* white- and blacklist for the bug server of other projects to (not)

Maybe the interface from the GitLab CE could be reused.

-- Package-specific info:
** Environment settings:

** /home/j/.reportbugrc:
reportbug_version "7.5.3+devuan3"
mode standard
ui text
realname "Jens Korte"
email ""

-- System Information:
Distributor ID:	Debian
Description:	Devuan GNU/Linux 3 (beowulf)
Release:	3
Codename:	beowulf
Architecture: x86_64

Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages reportbug depends on:
ii  apt      
ii  python3            3.7.3-1
ii  python3-reportbug  7.5.3+devuan3
ii  sensible-utils     0.0.12

reportbug recommends no packages.

Versions of packages reportbug suggests:
ii  claws-mail                                 3.17.3-2
pn  debconf-utils                              <none>
pn  debsums                                    <none>
ii  dlocate                                    1.07+nmu1
pn  emacs-bin-common                           <none>
ii  exim4                                      4.92-8+deb10u4
ii  exim4-daemon-light [mail-transport-agent]  4.92-8+deb10u4
ii  file                                       1:5.35-4+deb10u1
ii  gnupg                                      2.2.12-1+deb10u1
pn  python3-urwid                              <none>
ii  reportbug-gtk                              7.5.3+devuan3
ii  xdg-utils                                  1.1.3-1+deb10u1

Versions of packages python3-reportbug depends on:
ii  apt      
ii  file               1:5.35-4+deb10u1
ii  python3            3.7.3-1
ii  python3-apt
ii  python3-debian     0.1.35
ii  python3-debianbts  2.8.2
ii  python3-requests   2.21.0-1
ii  sensible-utils     0.0.12

python3-reportbug suggests no packages.

-- no debconf information

Acknowledgement sent to Jens Korte <>:
New bug report received and forwarded. Copy sent to, Devuan Developers <>. Full text available.
Report forwarded to,, Devuan Developers <>:
bug#476; Package reportbug. Full text available.

Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.

Devuan Bugs Owner <>.
Last modified: Sun, 22 May 2022 18:39:02 UTC