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

version graph

Package: reportbug; Maintainer for reportbug is Mark Hindley <>;

Reported by: Jens Korte <>

Date: Sat, 23 May 2020 15:03:02 UTC

Severity: wishlist

Tags: upstream

Found in version 7.5.3+devuan3

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to,, Devuan Developers <>:
bug#476; Package reportbug. (Sat, 23 May 2020 15:03:02 GMT) (full text, mbox, link).

Acknowledgement sent to Jens Korte <>:
New bug report received and forwarded. Copy sent to, Devuan Developers <>. (Sat, 23 May 2020 15:03:05 GMT) (full text, mbox, link).

Message #5 received at (full text, mbox, reply):

From: Jens Korte <>
To: Devuan Bug Tracking System <>
Subject: reportbug and the server interface aren't fluffy
Date: Sat, 23 May 2020 16:51:49 +0200
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

Information forwarded to, Devuan Developers <>:
bug#476; Package reportbug. (Sat, 23 May 2020 15:33:01 GMT) (full text, mbox, link).

Acknowledgement sent to Jens Korte <>:
Extra info received and forwarded to list. Copy sent to Devuan Developers <>. (Sat, 23 May 2020 15:33:03 GMT) (full text, mbox, link).

Message #10 received at (full text, mbox, reply):

From: Jens Korte <>
Subject: additional features
Date: Sat, 23 May 2020 17:11:42 +0200
* 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.

Send a report that this bug log contains spam.

Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

Devuan Bugs Owner <>.
Last modified: Thu Apr 15 17:11:23 2021;