[Reportbug-maint] Bug#894916: reportbug: print "Please install python3-urwid" instead of "Ignored bogus setting for --ui: urwid"
Package: reportbug Version: 7.1.10 Severity: minor When I tried the urwid UI for reportbug I got an error message: $ reportbug --ui urwid Ignored bogus setting for --ui: urwid After installing python3-urwid I got the urwid UI. I think it would be nicer to get this error message instead: $ reportbug --ui urwid Please install python3-urwid to use the urwid UI. -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages reportbug depends on: ii apt1.6~beta1 ii python33.6.4-1 ii python3-reportbug 7.1.10 ii sensible-utils 0.0.12 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail ii debconf-utils 1.5.66 ii debsums2.2.2 pn dlocate pn emacs24-bin-common | emacs25-bin-common ii exim4 4.90.1-5 ii exim4-daemon-light [mail-transport-agent] 4.90.1-5 ii file 1:5.32-2 ii gir1.2-gtk-3.0 3.22.29-2 ii gir1.2-vte-2.910.52.0-1 ii gnupg 2.2.5-1 ii python3-gi 3.28.1-1 ii python3-gi-cairo 3.28.1-1 pn python3-gtkspellcheck pn python3-urwid ii xdg-utils 1.1.2-2 Versions of packages python3-reportbug depends on: ii apt1.6~beta1 ii file 1:5.32-2 ii python33.6.4-1 ii python3-apt1.6.0~rc2 ii python3-debian 0.1.32 ii python3-debianbts 2.7.2 ii python3-requests 2.18.4-2 python3-reportbug suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
Re: [Reportbug-maint] reportbug-by-mail
On Thu, 2017-09-14 at 00:16 -0400, Sandro Tosi wrote: > ./pabs --verbose? I was attempting to make you aware of the reportbug-by-mail wiki page; in case you hadn't seen it yet, people are working around reportbug by embedding the reportbug template into a wiki page, because reportbug doesn't yet support launching the compose window of common desktop MUAs -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] reportbug-by-mail
https://wiki.debian.org/JensKorte/reportbug-by-mail -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#788045: reportbug: patch - use the default desktop mua
Control: tags -1 - patch Disclaimer: I'm not the maintainer of reportbug but... I don't think this patch is quite ready yet, see below. On Wed, 2017-06-28 at 10:41 -0400, David Steele wrote: > The attached patch adds a "desktop-default" option I might be wrong but I think individual options for choosing an MUA are deprecated and you should instead use a parameter to the --mua option. I also think you should call it xdg-email not desktop-default for precision about what it does, there is no /usr/bin/desktop-default. > via xdg-open and a "mailto" URI. I'd strongly suggest using xdg-email *not* xdg-open, the latter might not work for mailto but the former is more likely to work. In addition, xdg-email allows you to specify attachments, which IIRC reportbug can sometimes use. xdg-open cannot add attachments. > Note that this drops headers that are not I don't think that is acceptable since reportbug sets a number of other headers. mailto URLs can contain arbitrary headers anyway. > "X-Debbugs-Cc" would need to be moved to a pseudo-header. I think this should happen anyway, so that people receiving XCCs understand why they are getting a bug they did not expect. > I dropped a stopgap measure that moved X-Debug-Cc entries to Cc. You should never CC folks on a submit@ mail, so thanks for dropping it. PS: I think use of ui.system breaks this under the GTK+ UI. PPS: I note that the emacsclient MUA and viewing in a pager use it too. PPPS: *never* run external commands from python via os.system or equivalent (such as ui.system) unless you are using a hard-coded string for the command. Using dynamically calculated or user-provided data is likely to create issues when there are shell meta-characters present. S: if you are interested in expanding the MUA support of reportbug, I would suggest looking at reportbug-ng, which even supports webmail like gmail.com (in commented-out code that actually works). Personally, I think the MUA handling code of both reportbug and reportbug-ng needs to be factored out into a Python library that both tools can use. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#861153: reportbug: Architecture field split into two lines
Package: reportbug Version: 7.1.6 Severity: minor The architecture field is currently split into two lines: Architecture: amd64 (x86_64) With earlier versions of reportbug it was only one line: https://bugs.debian.org/823456 Architecture: amd64 (x86_64) -- System Information: Debian Release: 9.0 APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (860, 'testing-proposed-updates'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages reportbug depends on: ii apt1.4 ii python3-reportbug 7.1.6 pn python3:any reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail ii debconf-utils 1.5.60 ii debsums2.2 pn dlocate ii emacs24-bin-common 24.5+1-9 ii exim4 4.89-2 ii exim4-daemon-light [mail-transport-agent] 4.89-2 ii file 1:5.29-3 ii gir1.2-gtk-3.0 3.22.11-1 ii gir1.2-vte-2.910.46.1-1 ii gnupg 2.1.18-6 ii python3-gi 3.22.0-2 ii python3-gi-cairo 3.22.0-2 pn python3-gtkspellcheck pn python3-urwid ii xdg-utils 1.1.1-1 Versions of packages python3-reportbug depends on: ii apt1.4 ii file 1:5.29-3 ii python3-debian 0.1.30 ii python3-debianbts 2.6.1 ii python3-requests 2.12.4-1 pn python3:any python3-reportbug suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#847148: reportbug: validate that version numbers are or have been in Debian
Package: reportbug Severity: wishlist When reporting bugs to the Debian BTS (except for pseudo-packages), please check that provided version numbers match any of the versions known to have been in Debian and warn about unknown version numbers. Hopefully this will reduce the amount of bogus version numbers. Not sure if bugs.d.o has an API for this but snapshot.d.o has one: For bugs reported against source packages, you can use this JSON data: http://snapshot.debian.org/mr/package/example/ For bugs reported against binary packages, you can use this JSON data: http://snapshot.debian.org/mr/binary/example/ PS: version 7.0.0 works fine :) -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#835396: reportbug: detect ITPs on packages that were removed, mention reintroducing-pkgs docs
Package: reportbug Severity: wishlist Please detect ITPs on packages that were removed, mention the extra steps needed when reintroducing removed packages (as documented in the developers reference) and point ITPers at the old tracker.d.o pages. The detection could be done by using the snapshot API or the PTS API. https://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-pkgs https://anonscm.debian.org/cgit/mirror/snapshot.debian.org.git/plain/API https://bugs.debian.org/824912 https://wiki.debian.org/qa.debian.org/pts/SoapInterface -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
Re: [Reportbug-maint] move reportbug to collab-maint
On Sat, 2015-12-05 at 09:40 +, Sandro Tosi wrote: > I'd rather keep the team setup as it, but thanks for asking! Would it be possible for someone to merge the patches in #804504 then? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] move reportbug to collab-maint
Hi, What do you think about moving reportbug to collab-maint? This would mean that things like #804504 could be merged into the VCS without the reportbug team needing to be active. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#804504: reportbug: [PATCH] move all release codename hardcoding to one place
Package: reportbug
Severity: wishlist
Tags: patch
Please apply the attached patches to move all the release name
hardcoding into one place so that it isn't possible to forget updating
one of the places where names are hardcoded after a release happens.
Also add an entry for buster since the release team announced that:
https://lists.debian.org/20141109115231.gb2...@lupin.home.powdarrmonkey.net
--
bye,
pabs
https://wiki.debian.org/PaulWise
From 226520a05940c64a8b504e052f81ae3a557343b9 Mon Sep 17 00:00:00 2001
From: Paul Wise <p...@debian.org>
Date: Sun, 18 Oct 2015 11:03:25 +0800
Subject: [PATCH 1/3] Rename SUITES2DISTS variable to CODENAME2SUITE as name is
incorrect.
The variable maps codenames like jessie to suites like stable.
Also adjust the comment.
---
reportbug/checkversions.py | 2 +-
reportbug/utils.py | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/reportbug/checkversions.py b/reportbug/checkversions.py
index bb7a3fd..b04f46b 100644
--- a/reportbug/checkversions.py
+++ b/reportbug/checkversions.py
@@ -134,7 +134,7 @@ def get_versions_available(package, timeout, dists=None, http_proxy=None, arch='
if len(l) != 4:
continue
# map suites name (returned by madison) to dist name
-dist = utils.SUITES2DISTS.get(l[2], l[2])
+dist = utils.CODENAME2SUITE.get(l[2], l[2])
versions[dist] = l[1]
return versions
diff --git a/reportbug/utils.py b/reportbug/utils.py
index 2b4d64c..aaabd40 100644
--- a/reportbug/utils.py
+++ b/reportbug/utils.py
@@ -89,8 +89,8 @@ NEWBIELINE = """Dear Maintainer,
fhs_directories = ['/', '/usr', '/usr/share', '/var', '/usr/X11R6',
'/usr/man', '/usr/doc', '/usr/bin']
-# A map between suites and distributions names
-SUITES2DISTS = {'squeeze': 'oldoldstable',
+# A map between codenames and suites
+CODENAME2SUITE = {'squeeze': 'oldoldstable',
'wheezy': 'oldstable',
'jessie': 'stable',
'stretch': 'testing',
--
2.6.2
From ec10d69e54001181abe03ee0a82916bace05d567 Mon Sep 17 00:00:00 2001
From: Paul Wise <p...@debian.org>
Date: Fri, 16 Oct 2015 01:27:06 +0800
Subject: [PATCH 2/3] Remove hard-coding of release names in the
release.debian.org handling
This means there is only one place to update after a release.
Pre-compute the codenames and then use them in the UI because some
members of the Debian release team prefer codenames in the UI:
is there any reason for the reportbug handling of the release.debian.org
pseudo-package to be hard-coding release names? I was thinking of sending
this to the maintainer http://paste.debian.net/315948/
it needs to set suite tags
ok. maybe tomorrow I'll update it to use the SUITES2DISTS mapping,
so there is only one place to update
so the tag is the only thing that needs to use the codename?
can the UI use the suite names for eg?
personally i think codenames are clearer
but that may just be me, and i don't maintainer reportbug
Inspired-by: https://wiki.debian.org/SuitesAndReposExtension
---
reportbug/debbugs.py | 30 --
reportbug/utils.py | 1 +
2 files changed, 21 insertions(+), 10 deletions(-)
diff --git a/reportbug/debbugs.py b/reportbug/debbugs.py
index ebde5c4..11831cf 100644
--- a/reportbug/debbugs.py
+++ b/reportbug/debbugs.py
@@ -387,6 +387,16 @@ def handle_debian_release(package, bts, ui, fromaddr, timeout, online=True, http
archs = None
version = None
+oldstable = utils.SUITE2CODENAME['oldstable']
+oldstable_pu = oldstable + '-pu'
+oldstable_backports = oldstable + '-backports'
+oldstable_security = oldstable + '-security'
+stable = utils.SUITE2CODENAME['stable']
+stable_pu = stable + '-pu'
+stable_backports = stable + '-backports'
+stable_security = stable + '-security'
+testing = utils.SUITE2CODENAME['testing']
+
tag = ui.menu('What sort of request is this? (If none of these '
'things mean anything to you, or you are trying to report '
'a bug in an existing package, please press Enter to '
@@ -395,8 +405,8 @@ def handle_debian_release(package, bts, ui, fromaddr, timeout, online=True, http
'britney': "testing migration script bugs",
'transition': "transition tracking",
'unblock': "unblock requests",
- 'wheezy-pu': "wheezy proposed updates requests",
- 'jessie-pu': "jessie proposed updates requests",
+ oldstable_pu: "%s proposed updates requests" % oldstable,
+ stable_pu: "%s proposed updates requests" % stable,
'rm': "Stable/Testing removal requests",
'other': "None of the other options",
[Reportbug-maint] [PATCH 1/2] Rename SUITES2DISTS variable to CODENAME2SUITE as name is incorrect.
The variable maps codenames like jessie to suites like stable.
Also adjust the comment.
---
reportbug/checkversions.py | 2 +-
reportbug/utils.py | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/reportbug/checkversions.py b/reportbug/checkversions.py
index bb7a3fd..b04f46b 100644
--- a/reportbug/checkversions.py
+++ b/reportbug/checkversions.py
@@ -134,7 +134,7 @@ def get_versions_available(package, timeout, dists=None,
http_proxy=None, arch='
if len(l) != 4:
continue
# map suites name (returned by madison) to dist name
-dist = utils.SUITES2DISTS.get(l[2], l[2])
+dist = utils.CODENAME2SUITE.get(l[2], l[2])
versions[dist] = l[1]
return versions
diff --git a/reportbug/utils.py b/reportbug/utils.py
index 2b4d64c..aaabd40 100644
--- a/reportbug/utils.py
+++ b/reportbug/utils.py
@@ -89,8 +89,8 @@ NEWBIELINE = """Dear Maintainer,
fhs_directories = ['/', '/usr', '/usr/share', '/var', '/usr/X11R6',
'/usr/man', '/usr/doc', '/usr/bin']
-# A map between suites and distributions names
-SUITES2DISTS = {'squeeze': 'oldoldstable',
+# A map between codenames and suites
+CODENAME2SUITE = {'squeeze': 'oldoldstable',
'wheezy': 'oldstable',
'jessie': 'stable',
'stretch': 'testing',
--
2.6.1
___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] [PATCH 2/2] Remove hard-coding of release names in the release.debian.org handling
This means there is only one place to update after a release.
Pre-compute the codenames and then use them in the UI because some
members of the Debian release team prefer codenames in the UI:
is there any reason for the reportbug handling of the release.debian.org
pseudo-package to be hard-coding release names? I was thinking of sending
this to the maintainer http://paste.debian.net/315948/
it needs to set suite tags
ok. maybe tomorrow I'll update it to use the SUITES2DISTS mapping,
so there is only one place to update
so the tag is the only thing that needs to use the codename?
can the UI use the suite names for eg?
personally i think codenames are clearer
but that may just be me, and i don't maintainer reportbug
Inspired-by: https://wiki.debian.org/SuitesAndReposExtension
---
reportbug/debbugs.py | 30 --
reportbug/utils.py | 1 +
2 files changed, 21 insertions(+), 10 deletions(-)
diff --git a/reportbug/debbugs.py b/reportbug/debbugs.py
index ebde5c4..11831cf 100644
--- a/reportbug/debbugs.py
+++ b/reportbug/debbugs.py
@@ -387,6 +387,16 @@ def handle_debian_release(package, bts, ui, fromaddr,
timeout, online=True, http
archs = None
version = None
+oldstable = utils.SUITE2CODENAME['oldstable']
+oldstable_pu = oldstable + '-pu'
+oldstable_backports = oldstable + '-backports'
+oldstable_security = oldstable + '-security'
+stable = utils.SUITE2CODENAME['stable']
+stable_pu = stable + '-pu'
+stable_backports = stable + '-backports'
+stable_security = stable + '-security'
+testing = utils.SUITE2CODENAME['testing']
+
tag = ui.menu('What sort of request is this? (If none of these '
'things mean anything to you, or you are trying to report '
'a bug in an existing package, please press Enter to '
@@ -395,8 +405,8 @@ def handle_debian_release(package, bts, ui, fromaddr,
timeout, online=True, http
'britney': "testing migration script bugs",
'transition': "transition tracking",
'unblock': "unblock requests",
- 'wheezy-pu': "wheezy proposed updates requests",
- 'jessie-pu': "jessie proposed updates requests",
+ oldstable_pu: "%s proposed updates requests" % oldstable,
+ stable_pu: "%s proposed updates requests" % stable,
'rm': "Stable/Testing removal requests",
'other': "None of the other options",
}, 'Choose the request type: ', empty_ok=True)
@@ -441,7 +451,7 @@ def handle_debian_release(package, bts, ui, fromaddr,
timeout, online=True, http
else:
package = info[12] or package
-if tag in ('binnmu', 'unblock', 'jessie-pu', 'wheezy-pu', 'rm'):
+if tag in ('binnmu', 'unblock', stable_pu, oldstable_pu, 'rm'):
# FIXME: pu/rm should lookup the version elsewhere
version = info and info[0]
if online and tag.endswith('-pu'):
@@ -480,13 +490,13 @@ def handle_debian_release(package, bts, ui, fromaddr,
timeout, online=True, http
if tag == 'binnmu':
suite = ui.menu("For which suite are you requesting this binNMU?"
" Don't select anything for \"unstable\"", {
-'jessie': "",
-'jessie-backports': "",
-'jessie-security': "",
-'wheezy': "",
-'wheezy-backports': "",
-'wheezy-security': "",
-'stretch': "",
+stable: "",
+stable_backports: "",
+stable_security: "",
+oldstable: "",
+oldstable_backports: "",
+oldstable_security: "",
+testing: "",
'experimental': "",
}, 'Choose the suite: ', empty_ok=True)
if not suite:
diff --git a/reportbug/utils.py b/reportbug/utils.py
index aaabd40..8928b8c 100644
--- a/reportbug/utils.py
+++ b/reportbug/utils.py
@@ -96,6 +96,7 @@ CODENAME2SUITE = {'squeeze': 'oldoldstable',
'stretch': 'testing',
'sid': 'unstable',
'experimental': 'experimental'}
+SUITE2CODENAME = dict([(suite, codename) for codename, suite in
CODENAME2SUITE.items())])
def realpath(filename):
--
2.6.1
___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] [PATCH] Update the SUITES2DISTS mapping for the jessie release
---
reportbug/utils.py | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/reportbug/utils.py b/reportbug/utils.py
index 46476b5..2b4d64c 100644
--- a/reportbug/utils.py
+++ b/reportbug/utils.py
@@ -90,9 +90,10 @@ fhs_directories = ['/', '/usr', '/usr/share', '/var',
'/usr/X11R6',
'/usr/man', '/usr/doc', '/usr/bin']
# A map between suites and distributions names
-SUITES2DISTS = {'squeeze': 'oldstable',
-'wheezy': 'stable',
-'jessie': 'testing',
+SUITES2DISTS = {'squeeze': 'oldoldstable',
+'wheezy': 'oldstable',
+'jessie': 'stable',
+'stretch': 'testing',
'sid': 'unstable',
'experimental': 'experimental'}
--
2.6.1
___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#788045: reportbug: please use the xdg-email program to send bugs via the users preferred MUA
Package: reportbug Severity: wishlist When it is available, please use the xdg-email program to send bugs via the users preferred MUA. It supports setting To, CC, BCC, Subject, body text and adding attachments. It is provided by the xdg-utils package, so it might be a good idea to add that to Suggests/Recommends. xdg-email --cc address --bcc address --subject text --body text --attach file address -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#673270: reportbug: Use a future-proof URL for the rc_policy.txt document
On Thu, May 17, 2012 at 08:19:09PM +0800, Paul Wise wrote: Please apply the attached patch to use a future-proof URL for the rc_policy.txt document. The patch still applies as-is. Is there any reason not to apply it? If it is only due to lack of time, I will be happy to commit it git if you add me to the alioth project, give commit access to all Debian members or move it to collab-maint. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#748719: reportbug: check wnpp reports for spaces in proposed package names
Package: reportbug Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org On Mon, May 19, 2014 at 4:12 PM, Neil Williams wrote: On Sun, 18 May 2014 18:29:39 +0200 Jonas Smedegaard wrote: Package: wnpp Severity: wishlist Owner: Jonas Smedegaard d...@jones.dk * Package name: get directories of configuration files Maybe reportbug needs to check for whitespace in proposed package names Indeed, please add this. -- bye, pabs http://wiki.debian.org/PaulWise ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#696753: qa.debian.org: Reportbug bug for certain files.
Control: reassign -1 reportbug On Thu, Dec 27, 2012 at 3:26 AM, Zack wrote: Package: qa.debian.org Severity: important I think you meant to assign this bug to reportbug, not qa.debian.org, reassigning. I have been unable to use reportbug to report some bugs. Whilst trying to report bugs on gnome-tweak-tool, reportbug and reportbug-ng, reportbug closed suddenly with no warning or explanation. On gnome-tweak-tool, it repetatively did that when pressing continue (with mouse or keyboard), after I decided that my bug didn't apply to previously filed bugs. With reportbug when I tried to file this bug it did it repeatedly, after I clicked yes to a dailogue asking me if I am sure the bug is in reportbug, and with reportbug-ng it did it repetedly after selecting this package and clicking continue. -- bye, pabs http://wiki.debian.org/PaulWise ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#684540: Control: pseudo-headers are promoted to real headers
Package: reportbug Version: 6.4.2 Severity: normal I tried to use the new[1] Control: pseudo-headers but reportbug promoted them to normal mail headers. According to don, they are pseudo-headers: pabs dondelelcaro: are the Control: things headers, pseudo-headers or both? reportbug seems to promote them to real headers dondelelcaro pabs: they're pseudoheaders dondelelcaro it's possible that reportbug just doesn't know about them pabs ok, will file a bug I don't know if a fix for this would be accepted by the release team, but it would be nice if this were to be fixed in wheezy. 1. http://www.donarmstrong.com/posts/control_at_submit/ -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages reportbug depends on: ii apt 0.9.7.2 ii python2.7.3~rc2-1 ii python-reportbug 6.4.2 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail none ii debconf-utils 1.5.44 ii debsums2.0.52 pn dlocatenone ii emacs23-bin-common 23.4+1-3 ii exim4 4.80-4 ii exim4-daemon-light [mail-transport-agent] 4.80-4 ii file 5.11-2 ii gnupg 1.4.12-4+b1 ii python-gtk22.24.0-3 pn python-gtkspellnone ii python-urwid 1.0.1-2 ii python-vte 1:0.28.2-5 ii xdg-utils 1.1.0~rc1+git20111210-6 Versions of packages python-reportbug depends on: ii apt 0.9.7.2 ii python2.7.3~rc2-1 ii python-debian 0.1.21 ii python-debianbts 1.11 ii python-support1.0.15 -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#673270: reportbug: Use a future-proof URL for the rc_policy.txt document
Package: reportbug
Version: 6.3.1
Severity: normal
Tags: patch
Please apply the attached patch to use a future-proof URL for the
rc_policy.txt document.
--
bye,
pabs
http://wiki.debian.org/PaulWise
From e3625701dcd76854df45a72ef3e0d854fe2800aa Mon Sep 17 00:00:00 2001
From: Paul Wise p...@debian.org
Date: Wed, 7 Mar 2012 14:16:26 +0800
Subject: [PATCH] Use a future-proof URL for the rc_policy.txt document
---
reportbug/debbugs.py |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/reportbug/debbugs.py b/reportbug/debbugs.py
index 659f7dc..1d58032 100644
--- a/reportbug/debbugs.py
+++ b/reportbug/debbugs.py
@@ -72,7 +72,7 @@ SEVERITIES = {
(Package maintainers may also designate other bugs as 'serious' and thus
release-critical; however, end users should not do so.). For the canonical
list of issues worthing a serious severity you can refer to this webpage:
-http://release.debian.org/wheezy/rc_policy.txt .,
+http://release.debian.org/testing/rc_policy.txt .,
'important' : a bug which has a major effect on the usability
of a package, without rendering it completely unusable to
everyone.,
--
1.7.10
signature.asc
Description: This is a digitally signed message part
___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] [PATCH] Use a future-proof URL for the rc_policy.txt document
---
reportbug/debbugs.py |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/reportbug/debbugs.py b/reportbug/debbugs.py
index 2529062..9ebfe85 100644
--- a/reportbug/debbugs.py
+++ b/reportbug/debbugs.py
@@ -72,7 +72,7 @@ SEVERITIES = {
(Package maintainers may also designate other bugs as 'serious' and thus
release-critical; however, end users should not do so.). For the canonical
list of issues worthing a serious severity you can refer to this webpage:
-http://release.debian.org/wheezy/rc_policy.txt .,
+http://release.debian.org/testing/rc_policy.txt .,
'important' : a bug which has a major effect on the usability
of a package, without rendering it completely unusable to
everyone.,
--
1.7.9.1
___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#611600: reportbug: don't report debconf/depends/recommends/suggests info when there is none
Package: reportbug
Version: 4.12.6
Severity: minor
Tags: patch
Please add the attached two patches, which slightly reduce unneeded
clutter in bug reports.
--
bye,
pabs
http://wiki.debian.org/PaulWise
From 1d5c82355f1367c5a63fc954708b025898257479 Mon Sep 17 00:00:00 2001
From: Paul Wise p...@debian.org
Date: Mon, 31 Jan 2011 11:14:38 +0800
Subject: [PATCH 1/2] Don't report Depends/Recommends/Suggests if there are none.
---
reportbug/utils.py |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/reportbug/utils.py b/reportbug/utils.py
index cb64de7..1f16ab9 100644
--- a/reportbug/utils.py
+++ b/reportbug/utils.py
@@ -614,7 +614,7 @@ def packages_providing(package):
def get_dependency_info(package, depends, rel=depends on):
if not depends:
-return ('\n%s %s no packages.\n' % (package, rel))
+return ''
dependencies = []
for dep in depends:
--
1.7.2.3
From caf3c942731f0f0a05eb5a90cc9253d43d4a5984 Mon Sep 17 00:00:00 2001
From: Paul Wise p...@debian.org
Date: Mon, 31 Jan 2011 11:22:19 +0800
Subject: [PATCH 2/2] Don't report debconf information if there is none.
---
bin/reportbug |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/bin/reportbug b/bin/reportbug
index b659b23..769e60b 100755
--- a/bin/reportbug
+++ b/bin/reportbug
@@ -1782,8 +1782,6 @@ For more details, please see: http://www.debian.org/devel/wnpp/''')
conftext += u'\n-- debconf information:\n%s\n' % output
else:
conftext += u'\n-- debconf information excluded\n'
-else:
-conftext += u'\n-- no debconf information\n'
ewrite('\n')
prompted = False
--
1.7.2.3
signature.asc
Description: This is a digitally signed message part
___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
[Reportbug-maint] split MUA handling out of reportbug-ng and use in reportbug too?
Hi, As a result of filing #532150 ages ago, I'm wondering if the MUA handling could be split out of reportbug-ng and used in both reportbug-ng and reportbug. I would really like this because reportbug-ng supports my MUA (evolution), but reportbug does not and I have to go through a hacky procedure to get reportbug mails to the BTS. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#532150: Bug#532150: reportbug: [regression] no longer supports custom mua commands
That makes sense I guess. How about a custom-mua option for those of us who can write our own code to support MUAs reportbug doesn't (yet) support or will never support? If the script fails (returns != 0) you can assume that delivery failed. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#532150: reportbug: [regression] no longer supports custom mua commands
Package: reportbug Version: 4.4 Severity: important I just upgraded from lenny to squeeze and was disappointed to find that reportbug no longer supports custom MUAs. reportbug doesn't support my preferred MUA (evolution) so I use a custom MUA script to dump reportbug mails into my evolution drafts folder, where I edit them and send them on using evolution and its SMTP settings (which vary by mail address). p...@chianamo:~$ cat ~/.reportbugrc mode standard ui text #ui urwid #offline realname Paul Wise email p...@debian.org no-cc mua '/home/pabs/bin/evolution-bug-wrapper' p...@chianamo:~$ reportbug reportbug Specified mail user agent is not supported; exiting. p...@chianamo:~$ cat ~/bin/evolution-bug-wrapper #!/bin/sh echo 'From p...@debian.org -' ~/.evolution/mail/local/Drafts cat $* ~/.evolution/mail/local/Drafts rm -f $* p...@chianamo:~$ ls -l ~/bin/evolution-bug-wrapper lrwxrwxrwx 1 pabs pabs 42 2007-08-26 09:47 /home/pabs/bin/evolution-bug-wrapper - /home/pabs/devel/bin/evolution-bug-wrapper* p...@chianamo:~$ ls -l ~/devel/bin/evolution-bug-wrapper -rwxr-x--- 1 pabs pabs 125 2008-12-12 17:24 /home/pabs/devel/bin/evolution-bug-wrapper* Please fix reportbug to allow custom MUAs again. Using mutt as my MUA and making it dump postponed messages into evolution's drafts folder is slightly more cumbersome than just dumping them there via a script. It would also be nice if you could grab all the MUA stuff from reportbug-ng so I can just use evolution to report bugs in Debian, the custom MUA support is also important to keep though IMO. -- Package-specific info: ** Environment settings: EDITOR=nano REPORTBUGEMAIL=p...@debian.org DEBEMAIL=p...@debian.org EMAIL=p...@debian.org DEBFULLNAME=Paul Wise DEBNAME=Paul Wise NAME=Paul Wise INTERFACE=text ** /home/pabs/.reportbugrc: mode standard ui text realname Paul Wise email p...@debian.org no-cc -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages reportbug depends on: ii apt 0.7.21 Advanced front-end for dpkg ii python2.5.4-2An interactive high-level object-o ii python-reportbug 4.4Python modules for interacting wit Versions of packages reportbug suggests: pn debconf-utils none (no description available) pn debsums none (no description available) pn dlocate none (no description available) ii exim4 4.69-11metapackage to ease Exim MTA (v4) ii exim4-daemon-light [mail-tran 4.69-11lightweight Exim MTA (v4) daemon ii file 5.03-1 Determines file type using magic ii gnupg 1.4.9-4GNU privacy guard - a free PGP rep ii python-gnome2-extras 2.25.3-1 Extra Python bindings for the GNOM ii python-gtk2 2.14.1-2 Python bindings for the GTK+ widge ii python-urwid 0.9.8.4-1 curses-based UI/widget library for ii python-vte1:0.20.1-1 Python bindings for the VTE widget -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#415801: reportbug: SOAP support now more important due to BTS changes
On Mon, 2008-08-25 at 13:49 +0800, Paul Wise wrote: Lack of SOAP support in reportbug now more important due to the latest HTML changes in the bug tracking system. Some packages do not show the list of bugs, despite saying that there are bugs. I've been informed that the version in sid fixes this specific issue and has already been unblocked. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint
[Reportbug-maint] Bug#415801: reportbug: SOAP support now more important due to BTS changes
severity 415801 important thanks Lack of SOAP support in reportbug now more important due to the latest HTML changes in the bug tracking system. Some packages do not show the list of bugs, despite saying that there are bugs. One example is exiftran (reportbug says 7 bugs found, but doesn't show them), I have seen others but did not take note of them. Personally I think the lack of SOAP support should be RC, do the maintainers or the release team agree with that? $ reportbug exiftran Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Paul Wise [EMAIL PROTECTED]' as your from address. Getting status for exiftran... Checking for newer versions at packages.debian.org... Will send report to Debian (per lsb_release). Querying Debian BTS for reports on fbi (source)... 7 bug reports found: Maintainer for exiftran is 'Moritz Muehlenhoff [EMAIL PROTECTED]'. Looking up dependencies of exiftran... Please briefly describe your problem (you can elaborate in a moment; an empty response will stop reportbug). This will be the bug email subject, so write a concise summary of what is wrong with the package, for example, fails to send email or does not start with -q option specified. foo Rewriting subject to 'exiftran: foo' How would you rate the severity of this problem or report? 1 criticalmakes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package. 2 grave makes the package in question unusable by most or all users, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package. 3 serious is a severe violation of Debian policy (that is, the problem is a violation of a 'must' or 'required' directive); may or may not affect the usability of the package. Note that non-severe policy violations may be 'normal,' 'minor,' or 'wishlist' bugs. (Package maintainers may also designate other bugs as 'serious' and thus release-critical; however, end users should not do so.) 4 important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. 5 does-not-build a bug that stops the package from being built from source. (This is a 'virtual severity'.) 6 normal a bug that does not undermine the usability of the whole package; for example, a problem with a particular option or menu item. 7 minor things like spelling mistakes and other minor cosmetic errors that do not affect the core functionality of the package. 8 wishlistsuggestions and requests for new features. Please select a severity level: [normal] Do any of the following apply to this report? 1 l10n This bug reports a localization/internationalization issue. 2 patch You are including a patch to fix this problem. 3 none Please select tags: (one at a time) [none] Spawning /home/pabs/bin/evolution-bug-wrapper... [EMAIL PROTECTED]:~/tmp$ reportbug reportbug Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Paul Wise [EMAIL PROTECTED]' as your from address. Getting status for reportbug... Checking for newer versions at packages.debian.org... Will send report to Debian (per lsb_release). Querying Debian BTS for reports on reportbug (source)... 220 bug reports found: Outstanding bugs -- Uncategorized; Important bugs (4 bugs) 1) #420363 [i|M|] [reportbug] reportbug needs gettext however gettext is not a dependency Reported by: Daniel Dickinson [EMAIL PROTECTED]; Date: Sat, 21 Apr 2007 20:48:01 U 2) #440317 [i|M|=] [reportbug] reportbug crashes when trying to check packages.d.o Reported by: Greg Wooledge [EMAIL PROTECTED]; Date: Fri, 31 Aug 2007 13:30:01 UTC; Sever 3) #489447 [i||] [reportbug] reportbug: Will go on endless loop trying to login to smtp server (and looses all information) Reported by: alecs1 [EMAIL PROTECTED]; Date: Sat, 4) #491869 [i||] [reportbug] reportbug: Crash when attaching a file with a non-ascii character in filename Reported by: Sam Morris [EMAIL PROTECTED]; Date: Tue, 22 Jul 2008 Outstanding bugs -- Uncategorized; Normal bugs (15 bugs) 5) #213470 [n||] [reportbug] querybts terminal problems: LANG envariable involved Reported by: Matt Swift [EMAIL PROTECTED]; Date: Tue, 30 Sep 2003 16:48:04 UTC; Severity: 6) #259456 [n||] [reportbug] reportbug does not handle epochs correctly Reported by: Rene Engelhard [EMAIL PROTECTED]; Date: Wed, 14 Jul 2004 20:18:01 UTC; Severity: normal; F 7) #265554 [n||] [reportbug] reportbug: on receiving SIGTERM, should also signal child processes Reported by: Joey Hess [EMAIL PROTECTED]; Date: Fri, 13 Aug 2004 17:03:03 UTC 8) #310514 [n||] [reportbug] reportbug: bts vs. upstream issues Reported by: [EMAIL PROTECTED]; Date: Tue, 24 May
