[Reportbug-maint] Emotional Intimacy Expossed

2009-05-01 Thread Princiotta
inline: image/png___ Reportbug-maint mailing list Reportbug-maint@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint

Re: [Reportbug-maint] repotbug not loading ui

2009-05-01 Thread Dave Witbrodt
Amit Uttamchandani wrote: I have used reportbug successfully a few times with the urwid interface without any problems. However, recently I can't get reportbug to load urwid or even gtk2 ui settings. Tried to look at the bug reports posted on debian but no luck. Even tried reconfiguring and

[Reportbug-maint] Bug#500276: reportbug: Same problem here!

2009-05-01 Thread Francesco Poli (t1000)
Package: reportbug Version: 4.1 Severity: normal Hi! I have had the same exact problem, since I set the DEBFULLNAME environment variable. I consider this issue a bit annoying. Could you please fix this bug soon? Thanks in advance! -- Package-specific info: ** Environment settings:

[Reportbug-maint] Processing of reportbug_4.2_amd64.changes

2009-05-01 Thread Archive Administrator
reportbug_4.2_amd64.changes uploaded successfully to localhost along with the files: reportbug_4.2.dsc reportbug_4.2.tar.gz reportbug_4.2_all.deb python-reportbug_4.2_all.deb Greetings, Your Debian queue daemon ___ Reportbug-maint

[Reportbug-maint] reportbug_4.2_amd64.changes ACCEPTED

2009-05-01 Thread Debian Installer
Accepted: python-reportbug_4.2_all.deb to pool/main/r/reportbug/python-reportbug_4.2_all.deb reportbug_4.2.dsc to pool/main/r/reportbug/reportbug_4.2.dsc reportbug_4.2.tar.gz to pool/main/r/reportbug/reportbug_4.2.tar.gz reportbug_4.2_all.deb to pool/main/r/reportbug/reportbug_4.2_all.deb

[Reportbug-maint] Bug#523684: marked as done (reportbug: Wrong typing in lsb_release_info())

2009-05-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 May 2009 17:47:07 + with message-id e1lzwph-0006vs...@ries.debian.org and subject line Bug#523684: fixed in reportbug 4.2 has caused the Debian Bug report #523684, regarding reportbug: Wrong typing in lsb_release_info() to be marked as done. This means that you

[Reportbug-maint] Bug#524857: marked as done (reportbug: Always uses text interface)

2009-05-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 May 2009 17:47:08 + with message-id e1lzwpi-0006vy...@ries.debian.org and subject line Bug#524857: fixed in reportbug 4.2 has caused the Debian Bug report #524857, regarding reportbug: Always uses text interface to be marked as done. This means that you claim that

[Reportbug-maint] Bug#525856: marked as done (smpthost warning lacks vital information)

2009-05-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 May 2009 17:47:08 + with message-id e1lzwpi-0006w2...@ries.debian.org and subject line Bug#525856: fixed in reportbug 4.2 has caused the Debian Bug report #525856, regarding smpthost warning lacks vital information to be marked as done. This means that you claim

[Reportbug-maint] Bug#524297: marked as done (`reportbug --configure' tries to decode u'')

2009-05-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 May 2009 17:47:08 + with message-id e1lzwpi-0006vw...@ries.debian.org and subject line Bug#524297: fixed in reportbug 4.2 has caused the Debian Bug report #524297, regarding `reportbug --configure' tries to decode u'' to be marked as done. This means that you claim

[Reportbug-maint] Bug#525407: marked as done (option -A makes reportbug fail completely)

2009-05-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 May 2009 17:47:08 + with message-id e1lzwpi-0006w0...@ries.debian.org and subject line Bug#525407: fixed in reportbug 4.2 has caused the Debian Bug report #525407, regarding option -A makes reportbug fail completely to be marked as done. This means that you claim

[Reportbug-maint] Bug#358555: marked as done (reportbug: command line querybts 'q' exits with vestigal Nothing new to report; )

2009-05-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 May 2009 17:47:07 + with message-id e1lzwph-0006vo...@ries.debian.org and subject line Bug#358555: fixed in reportbug 4.2 has caused the Debian Bug report #358555, regarding reportbug: command line querybts 'q' exits with vestigal Nothing new to report; to be

[Reportbug-maint] Bug#523816: marked as done (reportbug: hanlde platform dependent modules with more care)

2009-05-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 May 2009 17:47:07 + with message-id e1lzwph-0006vu...@ries.debian.org and subject line Bug#523816: fixed in reportbug 4.2 has caused the Debian Bug report #523816, regarding reportbug: hanlde platform dependent modules with more care to be marked as done. This

[Reportbug-maint] Bug#526054: marked as done (reportbug: UnboundLocalError: local variable 'iface' referenced before assignment)

2009-05-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 May 2009 17:47:08 + with message-id e1lzwpi-0006w4...@ries.debian.org and subject line Bug#526054: fixed in reportbug 4.2 has caused the Debian Bug report #526054, regarding reportbug: UnboundLocalError: local variable 'iface' referenced before assignment to be

[Reportbug-maint] Bug#364626: marked as done (reportbug: Drop problem description when it's too long.)

2009-05-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 May 2009 17:47:07 + with message-id e1lzwph-0006vq...@ries.debian.org and subject line Bug#364626: fixed in reportbug 4.2 has caused the Debian Bug report #364626, regarding reportbug: Drop problem description when it's too long. to be marked as done. This means

[Reportbug-maint] Bug#525129: marked as done (reportbug crashes every time)

2009-05-01 Thread Debian Bug Tracking System
Your message dated Fri, 01 May 2009 17:47:08 + with message-id e1lzwpi-0006vw...@ries.debian.org and subject line Bug#524297: fixed in reportbug 4.2 has caused the Debian Bug report #524297, regarding reportbug crashes every time to be marked as done. This means that you claim that the

[Reportbug-maint] Bug#526523: marked as done (reportbug: gtk frontend does not come up)

2009-05-01 Thread Debian Bug Tracking System
Your message dated Fri, 1 May 2009 20:23:50 +0200 with message-id 8b2d7b4d0905011123x3eea7b71h950a6677ae2dd...@mail.gmail.com and subject line Re: Bug#526523: reportbug: gtk frontend does not come up has caused the Debian Bug report #526523, regarding reportbug: gtk frontend does not come up to

[Reportbug-maint] Bug#526372: marked as done (option -A causes crash)

2009-05-01 Thread Debian Bug Tracking System
Your message dated Fri, 1 May 2009 20:29:24 +0200 with message-id 8b2d7b4d0905011129w48c4a3cs77768cdc30331...@mail.gmail.com and subject line Re: Bug#526372: option -A causes crash has caused the Debian Bug report #526372, regarding option -A causes crash to be marked as done. This means that

[Reportbug-maint] Bug#526523: reportbug: gtk frontend does not come up

2009-05-01 Thread Sandro Tosi
On Fri, May 1, 2009 at 20:25, Christoph Egger deb...@christoph-egger.org wrote: On Fri, May 01, 2009 at 08:23:50PM +0200, Sandro Tosi wrote: Version: 4.2 On Fri, May 1, 2009 at 20:13, Christoph Egger deb...@christoph-egger.org wrote:        Starting reportbug with --ui gtk2 does not bring

[Reportbug-maint] Processed: Moreinfo

2009-05-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: tags 450674 moreinfo Bug#450674: reportbug: should handle invalid UTF-8 output gracefully There were no tags set. Bug#487674: reportbug: locks up on non 8-bit chars in subject line Tags added: moreinfo thanks Stopping processing here. Please

[Reportbug-maint] Bug#372250: patch to allow -f option to cancel configure mode

2009-05-01 Thread chaica
tags 372250 patch thanks Hi, Here is the patch to solve this issue, allowing reportbug to have the same behavior when configuration files have not been defined and using -f option or not e.g : $ reportbug chmod and $ reportbug -f chmod These two commands now don't launch the configuration