Bug#949104: piuparts.debian.org: please deploy latest fixes on pejacevic

Package: piuparts.debian.org Severity: normal The latest logs[1] still show this error: Traceback (most recent call last): File "/srv/piuparts.debian.org/share/piuparts/master/detect_well_known_errors", line 182, in args.recheck_failed) File

Bug#947837: [Piuparts-devel] Bug#947837: piuparts.debian.org: please upgrade python3-debianbts on pejacevic

On 01.01.2020 15.05, Holger Levsen wrote: > Hi & happy new year, Happy new year, too! :) > for this to happen, we need python3-debianbts in buster-backports. Can > you make that happen? cc:ing Bastian, the python3-debianbts maintainer. Aren't backports taken from testing? python3-debianbts

Bug#947837: piuparts.debian.org: please upgrade python3-debianbts on pejacevic

Package: piuparts.debian.org Severity: normal Since 27 December the piuparts-analyze output is broken. E.g.: https://piuparts.debian.org/logs/2019/12/27/piuparts-analyze.txt The failure start date coincides with the date when the new code from the develop branch was deployed. I think the

Bug#947737: buster: please document the rpcbind NEWS on enabling remote calls in the Release Notes

Package: release-notes Severity: normal After the upgrade from stretch to buster on a NIS server it was no longer possible to log into NIS client machines. While the buster release notes warn that this can be caused by a change in ypbind, it turned out that rpcinfo can also cause this. However,

Bug#919170: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts

On 27.12.2019 Holger Levsen wrote: > I do hope to do a final piuparts upload in 2019. We'll see if I manage during > 36c3 ;) Just submitted a few more merge requests for the remaining issues I could find. Good luck and have fun! :)

Bug#919170: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts

On 26.12.2019 17.11, Holger Levsen wrote: > many thanks, merged and deployed, now this is left: > File > "/srv/piuparts.debian.org/lib/python3/dist-packages/piupartslib/__init__.py", > line 58, in readline > empty = not self._refill() > File >

Bug#919170: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts

> TypeError: mynext() takes 1 positional argument but 2 were given > > again, help very welcome! A new merge request has the next set of fixups: https://salsa.debian.org/debian/piuparts/merge_requests/17

Bug#919170: [Piuparts-devel] Bug#919170: Please update dependency to python3-debianbts

Hi Holger, On 9 Nov 2019 Holger Levsen wrote: > test piuparts master-slave mode in buster, this works, also on localhost and > just needs the piuparts-(master|slave) packages packages installed in eg > a chroot. then switch to sid, build the packages from the piuparts.git > develop branch and do

Bug#946963: reportbug: LANGUAGE environment variable reported as defined while it is not set

control: tags -1 patch Fix: https://salsa.debian.org/reportbug-team/reportbug/merge_requests/48

Bug#946963: reportbug: LANGUAGE environment variable reported as defined while it is not set

Package: reportbug Version: 7.5.3~deb10u1 Severity: normal Reportbug collects: Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8), LANGUAGE=da_DK.UTF-8 (charmap=UTF-8) while LANGUAGE is in fact not set: $ locale LANG=da_DK.UTF-8 LANGUAGE= LC_CTYPE="da_DK.UTF-8"

Bug#940532: reportbug: another Multi-Arch issue

control: tags -1 patch >> This should be fixed in reportbug 7.6.0. Could you please test and confirm? > > It’s not. Thank you for testing and the quick feedback. This should fix the debsums problem: https://salsa.debian.org/reportbug-team/reportbug/merge_requests/46

Bug#940532: reportbug: another Multi-Arch issue

On 17 Sep 2019 Thorsten Glaser wrote: > If I reportbug without M-A qualifier, I get an error: This should be fixed in reportbug 7.6.0. Could you please test and confirm? > If I reportbug *with* M-A qualifier, things work, but > I get a warning: Yes, using the M-A qualifier was simply a

Bug#946363: reportbug can't identify the package of a bug specified with -N when the bug is files against a source package

control: tags -1 patch > I think that most of the bugs you have in mind were probably originally > filed against a binary package built from the linux source package, then > reassigned to src:linux. Indeed no reassigning is necessary because the kernel package's bug control file uses Submit-As:

Bug#946363: reportbug can't identify the package of a bug specified with -N when the bug is files against a source package

On 07 Dec 2019 Sven Bartscher wrote: > I recently tried to submit an additional report for the bug #939875 > which is filed against src:linux, but apparently reportbug struggles > to identify src:linux as a proper package name: > Retrieving report #939875 from Debian bug tracking system... >

Bug#941961: reportbug: nudge novice bug submitters away from incorrectly using the newcomer tag

On 08.12.2019 23.36, Nis Martensen wrote: > On 08 Oct 2019 Paul Wise wrote: >> I was thinking that reportbug should hide the display of the newcomer >> tag from the tag list when the reportbug mode is novice. > > In novice mode reportbug does not initially show the tag menu

Bug#922014: reportbug: number of bugs equals the list of whshlist bugs

control: tags -1 patch On 11 Feb 2019 "J. Schreck" wrote: > The number of bugs refers to the wishlist bugs if all bugs are shown at > once (output line of another bug reporting of mine): > (13-17/17) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? n Thanks for noticing such a small

Bug#942261: reportbug: When searching for executables in packages, consider full PATH not first match

control: tags -1 patch On 13 Oct 2019 Witold Baryluk wrote: > $ ls -l / | grep bin > lrwxrwxrwx 1 root root7 Oct 10 14:23 bin -> usr/bin > lrwxrwxrwx 1 root root8 Oct 10 14:23 sbin -> usr/sbin > $ > > > reportbug can probably be smarter here about this. > > There might be multiple

Bug#941961: reportbug: nudge novice bug submitters away from incorrectly using the newcomer tag

control: tags -1 patch On 08 Oct 2019 Paul Wise wrote: > I was thinking that reportbug should hide the display of the newcomer > tag from the tag list when the reportbug mode is novice. In novice mode reportbug does not initially show the tag menu at all, only before submission the user can

Bug#941257: reportbug: If you choose to save the file rather than email it, you are not given the choice were the file to be saved or told where it has been saved on exit

control: tags -1 patch On 27 Sep 2019 David Goodenough wrote: > > In the absense of proper integration with kmail (I see there is another bug > reported about that) I use the save to file option and then load the file into > kmail to send. When you press the save to file option that is the last

Bug#946326: python3-reportbug: reportbug runs bugscript in "C" locale

On 07 Dec 2019 Changwoo Ryu wrote: > > reportbug seems to run bugscript in "C" locale. In /usr/lib/python3/dist- > packages/reportbug/utils.py: > > rc = runner('LC_ALL=C %s %s %s' % (handler, pipes.quote(bugscript), > pipes.quote(filename))) > > > It prevents the ibus bugscript from

Bug#945590: reportbug: Cannot copy missing gtk+ package from window to command line

On 27 Nov 2019 Attila Rajmund Nohl wrote: > when I start reportbug without the gir1.2-vte-2.91 package on my system, I get > a dialog that this package is missing and cannot use the GTK+ interface. > However, I cannot copy the package nem from the dialog to a shell to an > "apt-get install"

Bug#939177: reportbug: With "outfile" rc option, text file does not start with Package line

Hey Scott, On 2 Sep 2019 Scott wrote: > I run reportbug with the "outfile" option - that is, I don't have reportbug > SEND the bug report, just write the information to a text file that I then > cut/paste into the Compose field of my browser's email site. > > Despite that fact that the BRS

Bug#932383: reportbug: fails to report against Multi-Arch library, such as libc6

control: severity -1 normal control: tags -1 patch On 18 Jul 2019 Thorsten Glaser wrote: Why do I have to select the package manually, TWICE, and the second prompt does not even show which is which (the normal user would be confused from the same entry showing up two or more times), and it

Bug#936061: reportbug: querybts doesn't find a certain existing bug report for package linux-image-5.2.0-2-amd64

On 29 Aug 2019 Michael Meier wrote: I wanted to report a bug for linux-image-5.2.0-2-amd64. I've used reportbug-ng to find out if the bug was already reported. Yes, I know it's not maintained anymore, but it still just works better to find existing bug reports. The bug was already reported.

Bug#931609: Update release names after the Buster release.

control: clone 931609 -2 control: retitle -2 reportbug crash in version lookup for stable release control: severity -2 normal On 08 Jul 2019 Thomas Goirand wrote: I tried to do: "reportbug -b release.debian.org cloudkitty" selected stretch-pu, thinking I'll fix later on, but reportbug just

Bug#934472: reportbug: provider of virtual package dependency with versioned Provides is not reported

control: tags -1 patch On 11 Aug 2019 Simon McVittie wrote: I assume the fact that libpam-systemd has a *versioned* Provides is confusing the logic in reportbug that is meant to report the versions of providers of virtual packages. Yes. Thank you for the analysis and report. There is now a MR

Bug#933004: reportbug should default to smtphost reportbug.debian.org

On Thu, 25 Jul 2019 13:34:08 -0400 Chris Danis wrote: While reportbug-gtk will prompt the user about MTAs vs using a smtphost (and offer reportbug.debian.org as an option), plain reportbug will not. Can you check if you had a .reportbugrc around already when you tried the text ui? The

Bug#933177: network-manager-openvpn: unable to connect after upgrade to buster due to new OpenSSL minimum TLS version

Package: network-manager-openvpn Version: 1.8.10-1 Severity: normal Dear Maintainer, After upgrading my laptop to buster I could no longer connect to the one remote VPN server I need. This is caused by OpenSSL now disabling TLS version 1.0 and 1.1 by default. The system log provided a helpful

Bug#931467: reportbug-gtk: Crashes after setting package name

On 05 Jul 2019 David wrote: -- System Information: Distributor ID: PureOS Description:PureOS Release:8 Codename: green Thank you for the report, but this is probably specific to PureOS or a system administration error. The problem does not exist in Debian. Please see

Bug#930085: reportbug gtk gui crashes

On Thu, 06 Jun 2019 P D wrote: Traceback (most recent call last): File "/usr/bin/reportbug", line 2285, in main() File "/usr/bin/reportbug", line 1115, in main return iface.user_interface() File "/usr/bin/reportbug", line 1728, in user_interface

Bug#853915: reportbug: Retrieved base64 messages aren't decoded

control: reassign 853915 debbugs > >> When running e.g. `reportbug -N 853037`, a bunch of base64 is > >> displayed instead of the actual content of the messages. > > I'm not sure if this problem comes from the BTS which sends wrong > > SOAP or on my side for parsing it wrong. > My suspicion is

Bug#888988: reportbug: Retrieved base64 messages aren't decoded

control: tags -1 unreproducible moreinfo On 2 Feb 2017 Scott Leggett wrote: > The same thing occurs when saving a bug report to disk if the bug report > contains a non-ascii character - it is saved as base64 and then is > rejected by the bug tracking system if you try to send it later because >

Bug#868155: reportbug: no input line after pager

control: severity -1 normal This can probably be closed. I believe this was fixed in reportbug 7.1.8; nobody has been able to provide more information on the bug in more than a year. Downgrading the report to → normal severity ← in the meantime.

Bug#920328: override: reportbug-gtk:utils/optional

Thanks Michael for the confirmation. So according to: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920328#10 bug #903712 (override: reportbug-gtk:utils/optional) is now fixed, closing.

Bug#920328: priority of packages added to the archive

On 24 Jan 2019 Ansgar wrote: > FWIW I just changed the priority of both netplan.io and reportbug-gtk to > "optional". Are you saying #903712 can be closed now?

Bug#803675: [Reportbug-maint] Bug#803675: reportbug: unable to report bug on kernel

On 02/01/2019 22.57, Nis Martensen wrote: > On 01/01/2019 22.18, Sandro Tosi wrote: >> >> alternatively, we can force bugscript execution in an actual terminal, >> when using GTK, it may not be visually pleasing to see a window pop >> up, but it would be t

Bug#803675: [Reportbug-maint] Bug#803675: reportbug: unable to report bug on kernel

On 01/01/2019 22.18, Sandro Tosi wrote: > > alternatively, we can force bugscript execution in an actual terminal, > when using GTK, it may not be visually pleasing to see a window pop > up, but it would be the safest way to gather all the information the > maintainer wants via bugscripts > >

Bug#917617: reportbug-gtk: "Exception in Thread-n" when retrieving more information from BTS

On 29 Dec 2018 Bruno Kleinert wrote: > File "/usr/lib/python3/dist-packages/pysimplesoap/client.py", line > 175, in > > return lambda *args, **kwargs: self.call(attr, *args, **kwargs) > File "/usr/lib/python3/dist-packages/pysimplesoap/client.py", line > 213, in > call > for k, v in

Bug#917846: /usr/bin/querybts: querybts doesn't find bug that exists

On 31 Dec 2018 Manuel Bilderbeek wrote: > $ querybts 917782 > Retrieving report #917782 from Debian bug tracking system... > No report available: #917782 > No bug reports found. > > But that doesn't make sense, as this bug really exists! Thanks for the report. The actual bug is in

Bug#917397: reportbug: cannot find/fetch bug reports after initial listing

> I tried selecting a specific bug from the list reportbug presented, though > reportbug reports it can't find said bug: Thanks for the report. The actual bug is in python-debianbts (tracked in #917165), one of the libraries reportbug depends on. I'm not reassigning or closing this bug, in

Bug#917165: reportbug: Crashes in soap client, fails to retrive a bugreport

control: reassign -1 python-debianbts control: notforwarded -1 control: retitle -1 python-debianbts: incompatible with new pysimplesoap > File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 1154, in > get_report > log = debianbts.get_bug_log(number) > File

Bug#853915: reportbug: Retrieved base64 messages aren't decoded

> It seems like the core of the problem is that parts of the header -- i.e.: > > Content-Type: text/plain; charset="UTF-8" > > Content-Transfer-Encoding: base64 > > are assigned as part of the email body instead of the -header. The message is a multipart message, where

Bug#853915: reportbug: Retrieved base64 messages aren't decoded

>> When running e.g. `reportbug -N 853037`, a bunch of base64 is >> displayed instead of the actual content of the messages. > I'm not sure if this problem comes from the BTS which sends wrong > SOAP or on my side for parsing it wrong. My suspicion is that the BTS SOAP interface has trouble

Bug#917258: reportbug: -N, --bugnumber options seems to not work

control: reassign -1 pysimplesoap control: forcemerge 917165 917258 > > No report available: #541147 > > No such bug report. Thank you for the report. The problem is caused by a crash in pysimplesoap. Merging with another report which has more details.

Bug#917165: reportbug: Crashes in soap client, fails to retrive a bugreport

control: reassign -1 pysimplesoap control: severity -1 serious control: affects -1 reportbug control: affects -1 python-debianbts control: tags -1 upstream control: forwarded -1 https://github.com/pysimplesoap/pysimplesoap/issues/167 On 23 Dec 2018 Witold Baryluk wrote: > File

Bug#890680: [Reportbug-maint] Bug#890680: reportbug: python3-reportbug submodules are not well documented

perspective? What do you think? On 21/02/2018 23.17, Nis Martensen wrote: > On 20-02-2018 06:02, Sandro Tosi wrote: >> On Sun, Feb 18, 2018 at 5:03 AM, Nis Martensen wrote: >>> Extending the test suite is actually the goal here. It's just hard to >>> add tests for functi

Bug#916297: reportbug: crash after using "Display modified configuration files"

control: reopen 916297 control: tags 916297 patch On 13 Dec 2018 nemo Inis wrote: > > 3) the bug is in reportbug/ui/gtk2_ui.py, in the class 'SystemPage(Page)' > which defines > 'on_child_exited' with two parameters when it should be three (the third > parameter being the > child's exit status

Bug#916297: reportbug: crash after using "Display modified configuration files"

Sandro, To reproduce the bug, one can modify /etc/reportbug.conf and run `reportbug --ui gtk2 reportbug`. Display the config file, press q. The exception is caught by the Gtk interface to display an error dialog. Therefore there is no better traceback. Nis

Bug#873493: reportbug: confused with python-astroid

> Reportbug uses the ftp-master madison cgi to identify available > package versions. This was not correct. Reportbug uses the qa madison url, not the ftp-master one. It should switch to the latter, as a bug in the qa cgi contributes to the problem. To fully solve the problem, reportbug will need

Bug#873493: reportbug: confused with python-astroid

On 09 Sep 2018 David Nebauer wrote: > > I've encountered the exact same problem as Norbert. The incorrect > versions being reported for package 'astroid' are those for package > 'python-astroid', so it is clear that the underlying problem is that > reportbug looks for 'astroid' but matches with

Bug#882130: fixed in reportbug 7.1.8

control: tags 882130 + patch On 5 Jan 2018 Jochen Sprickerhof wrote: > this fix removes the error output of apt-cache showsrc when there is no > deb-src. > > reportbug-7.1.7: > > $ reportbug release.debian.org > [..] > Choose the request type: 7 > Please enter the name of the package:

Bug#906990: reportbug: wildcard globbing for attachments should attach in alphabetical order, not filesystem order

control: tags 906990 + patch On 22 Aug 2018 Daniel Kahn Gillmor wrote: > when using reportbug interactively, i write the report, and then > choose "a" to attach a file. > > it's very nice that i can use shell globbing there (e.g., by entering > "src/foo/fixup/00*.patch"). but when i do that,

Bug#803675: [Reportbug-maint] Bug#803675: reportbug: unable to report bug on kernel

control: merge 669038 771545 891468 On 6 Nov 2016 Ben Finney wrote: > On 01-Nov-2015, Sandro Tosi wrote: > > it's a limitation of the GTK interface, please use the text > > interface > > What is the limitation, specifically? Reportbug provides `getkey` and `yesno` helper functions for

Bug#908515: urwid interface can't call PAGER and crashes due to AttributeError

control: tags 908515 patch > AttributeError: module 'reportbug.ui.urwid_ui' has no attribute 'system' The pull request addressing #903969 fixes this one, too: https://salsa.debian.org/reportbug-team/reportbug/merge_requests/4

Bug#905737: reportbug: fails with '500 Internal Server Error' and 'No such bug report' retrieving only some bugnumbers

control: reassign 905737 python-debianbts On 08 Aug 2018 Santiago wrote: > Package: reportbug > Version: 7.5.0 > Severity: important > > Dear Maintainer, for several months, I reported without problems about the > bugnumber 885947 (the last correct was on 23-Jul-2018). > > > From 29-Jul-2018,

Bug#905353: reportbug: reports package on hold as not installed

control: tags 905353 patch On 03 Aug 2018 Sven Joachim wrote: > In the output of the last command, I would have expected emacsen-common > to be reported as > > hi emacsen-common 2.0.8 Thank you for the nice report. This should fix it:

Bug#564112: [Reportbug-maint] Bug#564112: use python-apt to look up package short descriptions

> changing utils.available_package_description() to use the try..except > with python3-apt sounds like a good idea. I take that back. We should just drop utils.available_package_description() and its tests. If we'd put the try..except into that function, we'd also need to either (i) put the

Bug#564112: [Reportbug-maint] Bug#564112: use python-apt to look up package short descriptions

> what should we do about utils.available_package_description()? it has a few > unittests associated with it, maybe we should re-use it to wrap that > try..except and adapt the tests? changing utils.available_package_description() to use the try..except with python3-apt sounds like a good idea.

Bug#564112: [Reportbug-maint] Bug#564112: use python-apt to look up package short descriptions

> @@ -560,7 +563,10 @@ def get_source_package(package): > packages += packlist > > for p in packages: > -desc = available_package_description(p) > +try: > +desc = apt_cache[p].versions[0].summary > +except KeyError: > +continue >

Bug#892270: [reportbug] Crash when report type set to None

control: tags -1 unreproducible moreinfo control: severity -1 important Hi Jérôme, On 7 Mar 2018 Jérôme Bardot wrote: > Reportbug (gtk2 ui) crash when i select package. > > The command line  output : > > Traceback (most recent call last): >   File "/usr/bin/reportbug", line 2265, in >    

Bug#892898: reportbug crashes due with UnicodeDecodeError

control: tags -1 patch Thank you for the report. This should fix the crash: https://salsa.debian.org/reportbug-team/reportbug/merge_requests/2 I could not reproduce the problem, though. What does DEBCONF_SYSTEMRC=1 DEBCONF_NOWARNINGS=yes debconf-show console-setup output on your system? Is the

Bug#878088: [Reportbug-maint] Bug#878088: reportbug: please inform security and lts teams about security update regressions

Thanks Sandro! One thing is missing, though: we now need a dependency on python3-apt.

Bug#890680: [Reportbug-maint] Bug#890680: reportbug: python3-reportbug submodules are not well documented

On 20-02-2018 06:02, Sandro Tosi wrote: > On Sun, Feb 18, 2018 at 5:03 AM, Nis Martensen <nis.marten...@web.de> wrote: >> Extending the test suite is actually the goal here. It's just hard to >> add tests for functions of which you don't know what they're supposed to >

Bug#890680: [Reportbug-maint] Bug#890680: reportbug: python3-reportbug submodules are not well documented

Hey Sandro! On 18-02-2018 05:49, Sandro Tosi wrote: > Hey Nis! > >> The reportbug source code has some issues that make it hard to review: > > > thanks for working on this! even if i dont want to mess with your > plans, let me tell you that if you really want to work on this "qa" > kind-of

Bug#890680: reportbug: python3-reportbug submodules are not well documented

Package: reportbug Version: 7.1.8 Severity: wishlist The reportbug source code has some issues that make it hard to review: - Most functions in reportbug/*.py do not have a docstring, or only a very brief one. Some functions still have many parameters, and some return quite complex

Bug#853915: Bugreports and base64

control: clone 853915 -1 control: reassign 853915 python-debianbts control: retitle -1 reportbug: base64 encoded reports rejected by bts Reading and sending base64 message are two different bugs, so let's split this report. I believe that python-debianbts is supposed to decode a base64 message

Bug#878088: [Reportbug-maint] Bug#878088: reportbug: please inform security and lts teams about security update regressions

On 29-01-2018 00:11, Markus Koschany wrote: > > I noticed that you had to import apt but reportbug does not depend on > python3-apt. After I had installed this package it worked. I also > believe you don't need to check for the upstream changelog.gz file, the > Debian changelog should be

Bug#878088: [Reportbug-maint] Bug#878088: reportbug: please inform security and lts teams about security update regressions

in novice mode? Should reportbug incorporate a default version of the json file to fall back to if the lookup fails? Reportbug is probably going to be updated more often than the online version of the json file. An internal version could also be updated regularly. >From 56d6dbffd3075bb9f06aa1b31fd8f6

Bug#878088: reportbug: please inform security and lts teams about security update regressions

On 24-01-2018 19:37, Markus Koschany wrote: > Thanks. How do you catch the case when security updates are part of a > stable point release? This requires more effort. Does the package tracker offer a way to query such information? The only other idea I have right now involves inspecting the

Bug#878088: reportbug: please inform security and lts teams about security update regressions

How about this? import apt def is_security_update(pkgname, version): try: p = apt.Cache()[pkgname] except: return False if version not in p.versions: return False if 'Debian-Security' in [o.label for o in p.versions[version].origins]:

Bug#878088: reportbug: please inform security and lts teams about security update regressions

Let me describe my suggestion in more detail: - Instead of having the "is this a security version" check implemented directly in bin/reportbug as a version number check, there could be a new function "is_security_update(package, version)" in reportbug/utils.py. You can move the version number

Bug#878088: reportbug: please inform security and lts teams about security update regressions

2018-01-23 15:58 GMT+01:00 Sandro Tosi : > point releases usually include all the security updates from the > previous point release, so they would come from the "main" repo and > not the security one That would only be a problem if they are then no longer available via the

Bug#878088: reportbug: please inform security and lts teams about security update regressions

It might be possible to determine whether an installed package is a security update by inspecting the output of apt-cache policy pkgname. Not sure if this information can also be obtained used python3-apt.

Bug#539737: reportbug: RFC-1522-encoded headers for mutt

On 3 Aug 2009 Jakub Wilk wrote: > Package: reportbug > Version: 4.5 > Severity: normal > > reportbug encodes non-ASCII headers as per RFC 1522. However, `mutt -H` > does not expect headers to be encoded in such a way. This seems to have been fixed on the mutt side. At least I am unable to

Bug#577278: reportbug: Attach options (-A) is not safe for UTF-8 content

On 11 Apr 2010 Jari Aalto wrote: > Package: reportbug > Version: 4.11 > Severity: normal > > > Using the -A optiontion to attach and UTF-8 patch seems to have problems. This seems to have been fixed in the meantime, probably when reportbug was ported to python3.

Bug#507600: bug script not ready for scripts

On Wed, 03 Dec 2008 05:03:58 +0800 jida...@jidanni.org wrote: > Package: apt > Version: 0.7.19+b1 > File: /usr/share/bug/apt/script > > Your script never expected stdin to be closed. > I.e., one cannot use reportbug --template in a script then. E.g., > $ echo reportbug --template -f

Bug#857810: reportbug: crashes if $HOME does not exist, bugreport is lost

On 15 Mar 2017 Thorsten Glaser wrote: > Package: reportbug > Version: 6.6.3 > Severity: important > > I just reported a bug in a cowbuilder chroot, so $HOME pointed to > a nonexistent directory. What I got was this: > > File /tmp/reportbug-node-uglify-20170315-25826-NfKllD saved. > Report will

Bug#701484: reportbug: "/usr/share/bug/nis/script: 7: yesno: not found"

control: tags -1 patch The yesno command is provided as a bash function by reportbug itself, and only available to bug scripts written as bash scripts. This is documented in /usr/share/doc/reportbug/README.developers.gz. This small change fixes this bug, and #772282 as well: diff --git

Bug#885959: reportbug: marks mime type of attachments as inode/symlink

control: tags -1 patch Thanks for the report! >From 77087cf7a1b16d0be199c301ece62f04f06d5b6f Mon Sep 17 00:00:00 2001 From: Nis Martensen <nis.marten...@web.de> Date: Mon, 1 Jan 2018 11:28:25 +0100 Subject: [PATCH] submit.py: dereference symbolic links when detecting file type ---

Bug#883577: [Reportbug-maint] Bug#883577: locales not installed

On 29-12-2017 01:27, Sandro Tosi wrote: > On Wed, Dec 6, 2017 at 12:48 PM, Nis Martensen <nis.marten...@web.de> wrote: >>> Does reportbug depend on locales being installed or something related? >> >> No, strictly speaking not. In practice, however, often yes. > &

Bug#868155: reportbug: no input line after pager

> Run “reportbug --offline reportbug” on a terminal with 33 lines. > Exit the pager with “q” then wonder. > > Pressing ^L shows the input line, with no introduction. > > This only happens for packages that cause a pager to show > something before the input fields. Cannot reproduce here. Can you

Bug#877650: reportbug: crashes when maintainer's name contains incompatible character

s a patch. It applies on top of the patch that I sent to #695887. Besides #877650, it should also fix #868022 and #883577. >From c238cf242a8713ccd8bd9a36319e1bd1d8c72bb6 Mon Sep 17 00:00:00 2001 From: Nis Martensen <nis.marten...@web.de> Date: Tue, 5 Dec 2017 21:40:03 +0100 Subject: [PATCH 2/2] Pre

Bug#883577: locales not installed

> Does reportbug depend on locales being installed or something related? No, strictly speaking not. In practice, however, often yes. One can set the default system locale to "C.UTF-8" (variable LANG in /etc/default/locale) if having locales installed is not desired. Thanks for the very

Bug#877650: reportbug: crashes when maintainer's name contains incompatible character

Thanks for your report! On 03 Oct 2017 Eckhard Neber wrote: > Detected character set: UTF-8 Your system is set up to use UTF-8 (good). > File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 728, in > get_changed_config_files > for line in fp: > File

Bug#695887: reportbug locks terminal, refuses echo, requires "reset" after viewing followup

control: forcemerge 695887 849763 882983 control: tags -1 patch These bugs are caused by file descriptors not being closed properly. The attached patch should help. >From 1dbc071c3b966f4fb351948412ffe438de11e62f Mon Sep 17 00:00:00 2001 From: Nis Martensen <nis.marten...@web.de> Date: M

Bug#564112: use python-apt to look up package short descriptions

control: tags -1 patch This also fixes #876373 Other related bugs: #502860, #599290, #882130 >From 4612729648fd17955e80a250baca120ce9747251 Mon Sep 17 00:00:00 2001 From: Nis Martensen <nis.marten...@web.de> Date: Mon, 4 Dec 2017 13:39:38 +0100 Subject: [PATCH] Look up short package des

Bug#878439: network-manager-openvpn-gnome: Unable to edit or add VPN connections

Package: network-manager-openvpn-gnome Version: 1.2.8-2 Severity: important Dear Maintainer, After the upgrade from jessie to stretch, I have been unable to connect to my VPN. The GUI was not able to provide a proper description of the reason. However, the system log revealed that the

Bug#851502: Still see this bug

control: tags 851502 unreproducible moreinfo > I would like to request severity raised to serious. Michael, it seems not many people can actually reproduce the bug. I've tried on stretch and current sid, and reportbug works just fine for me. Sandro has already pointed out that reportbug

Bug#868154: reportbug: displays MIME type of attachment

>From bf3724a200d9db947c77c1d9ce0eb61536a0bade Mon Sep 17 00:00:00 2001 From: Nis Martensen <nis.marten...@web.de> Date: Sat, 9 Sep 2017 23:41:48 +0200 Subject: [PATCH 3/3] Drop leftover debug print() --- reportbug/submit.py | 1 - 1 file changed, 1 deletion(-) diff --git a/reportbug/submit

Bug#849765: [Reportbug-maint] Bug#849765: reportbug: produces invalid mails when there are long lines

90 bytes. Here is a patch that fixes the problem in reportbug. >From d32fb670bcdf622b9e2b3d45e88abd8cf0e2d711 Mon Sep 17 00:00:00 2001 From: Nis Martensen <nis.marten...@web.de> Date: Thu, 7 Sep 2017 18:17:00 +0200 Subject: [PATCH 2/2] Use quoted-printable encoding for too long lines ---

Bug#872780: reportbug: When filing ITP report and realname has UTF-8 character, the name will be encoded in RFC2047, which it shouldn't

g> Yes. Here's a patch. >From ae8bb0186e4469ec02f1bfb5c25fa33b78744cc2 Mon Sep 17 00:00:00 2001 From: Nis Martensen <nis.marten...@web.de> Date: Tue, 5 Sep 2017 22:13:14 +0200 Subject: [PATCH] Do not RFC2047-encode Owner pseudo header --- reportbug/debbugs.py | 3 ++- 1 file changed,

Bug#866596: querybts: launch_mbox_reader() strips NL characters

ached. >From 7b0f010797dc8ad52838604bb9eb3de9e3f5d9a3 Mon Sep 17 00:00:00 2001 From: Nis Martensen <nis.marten...@web.de> Date: Fri, 30 Jun 2017 23:19:32 +0200 Subject: [PATCH] Add line endings when processing strings line by line Bug introduced in d7e9eb8cc5d2efa4543bd35a806cbc36d7419e5e --- rep

Bug#862152: crash when $DISPLAY is defined

On 29-05-2017 21:58, Erwan David wrote: > X display is remote (on a mac in my case, but remote). Direct access to > driver is thus not possible. If you do X remote display (which ssh is capable of doing), then something must communicate with some driver. Is any of your local machine or the remote

Bug#862152: crash when $DISPLAY is defined

On Tue, 09 May 2017 07:55:20 +0200 Erwan David wrote: > Package: reportbug > Version: 7.1.6 > Severity: important > > When launching reportbug with $DISPLAY defined I get errors : > @erdavid-dt:~ 8m34s % reportbug emacs > libGL error: No matching fbConfigs or visuals found >

Bug#863513: [Reportbug-maint] Bug#863513: Bug#863513: reportbug: No GUI; only '--ui=text'

the required libraries. Attaching a first draft patch. Not something for stretch, though. >From 14fc7be72a49b704fa3f2cbff275a546fbcd0878 Mon Sep 17 00:00:00 2001 From: Nis Martensen <nis.marten...@web.de> Date: Sun, 14 May 2017 21:32:43 +0200 Subject: [PATCH 7/9] split off the GTK ui in

Bug#863322: reportbug: Wrong subject and package description while filling a WNPP RFA

One more patch on top, with some improvements. >From 1e965eb715d80dd07f4b930db0e22a8011c03bae Mon Sep 17 00:00:00 2001 From: Nis Martensen <nis.marten...@web.de> Date: Sun, 28 May 2017 13:07:25 +0200 Subject: [PATCH 3/3] utils.py: Do not use localized package description .. and unify th

Bug#861153: [Reportbug-maint] Bug#861153: reportbug: Architecture field split into two lines

Hey Sandro! > should we revert to the previous behavior of get_command_output before > introducing other regressions? Having re-read the code again, I can't see any risk of introducing other regressions. Only lsb_release_info() and get_arch() directly return the result of get_command_output(),

Bug#863322: reportbug: Wrong subject and package description while filling a WNPP RFA

's using > "Description-md5" instead the short description) and the description > itself is using text from tags. Thank you for the report. Attaching two patches. Both together should fix this. >From 924f153462f456840211ee6ba852a041156ffe02 Mon Sep 17 00:00:00 2001 From: Nis Martensen <

Bug#861153: reportbug: Architecture field split into two lines

ian.org/823456 > Architecture: amd64 (x86_64) Thanks for reporting this. It is only one symptom of the actual bug. Let's fix this before we find out exactly what else was broken by my patch in reportbug 7.1.6. Follow-up patch attached. >From 892d6fb67fbe2e9198884e020e8f1926c7a1188b Mon Sep 17 00:

Bug#859274: /usr/bin/querybts: double-faults when using -m option

control: tags 859274 patch Thanks for reporting this. Here's a patch. >From cbe84151785b180188d5df9c26f42714e82e9451 Mon Sep 17 00:00:00 2001 From: Nis Martensen <nis.marten...@web.de> Date: Sat, 22 Apr 2017 11:27:37 +0200 Subject: [PATCH 1/2] Finish open_url return type conversion T

<    1   2   3   >