Package: lists.debian.org
Severity: wishlist
X-Debbugs-Cc: nis.marten...@web.de
Dear listmaster,
The web archives like
https://lists.debian.org/debian-devel/
would be nicer to use if the latest months were listed first, because
right now it is always necessary to scroll down to reach the latest
Package: lists.debian.org
Severity: normal
X-Debbugs-Cc: nis.marten...@web.de
Dear listmaster,
Trying to access
https://lists.debian.org/debian-devel/recent
no longer works, but gives an error:
cmp_idx_pages() missing 1 required positional argument: 'b'
This is not specific to the debian-devel
On 18.05.2024 23.52, Nis Martensen wrote:
> Since this is about cc-related options, are you already including the -x
> (or --no-cc) option when invoking reportbug?
Just checked and you don't need it when using --template. Bcc headers
will be stripped off and won't be included in that case.
Hi Xiyue,
> If we have an option to disable loading "~/.reportbugrc" we can avoid
> this situation.
There is no option to disable loading /etc/reportbugrc, but you can
already disable loading ~/.reportbugrc by setting $HOME to a
non-existing directory or the empty string:
$ grep cc
On 18.05.2024 22.58, Xiyue Deng wrote:
> Using the use case in elpa-debian-el as an example, we handle CCing
> oneself in ELisp, so we assume reportbug is invoked without "list-cc-me"
> by not passing that argument. However, if the user has a
> "~/.reportbugrc" with "list-cc-me" in it, it will
On 12.05.2024 23.11, Xiyue Deng wrote:
> Nis Martensen writes:
>
>> On 11.05.2024 08.23, Xiyue Deng wrote:
>>> I'd like to propose adding an option to skip loading configuration files
>>> (/etc/reportbug.conf and ~/.reportbugrc). The use case is for external
&g
On 11.05.2024 08.23, Xiyue Deng wrote:
> I'd like to propose adding an option to skip loading configuration files
> (/etc/reportbug.conf and ~/.reportbugrc). The use case is for external
> programs that runs reportbug (e.g. debian-bug in elpa-debian-el) which
> provides its own command line
Hi Paul,
On 10.02.2024, Paul Wise wrote:
>
> I have been working on an enhancement[1] to reportbug that would allow
> interactive selection of port/arch usertags[2] and automatically set
> them in code paths that currently already ask for an architecture.
>
> I could use some design advice
control: tags -1 pending
On 16.11.2023 12.48, Vincent Lefevre wrote:
> Control: retitle -1 reportbug: obsolete NEWQUEUE_URL, giving a 301 Moved
> Permanently
>
> On 2023-11-16 12:34:17 +0100, Vincent Lefevre wrote:
>> So this URL gives a 301 Moved Permanently with
>>
Hi Vincent,
On 14.11.2023 15.17, Vincent Lefevre wrote:
>> Checking for newer versions at madison and
>> https://ftp-master.debian.org/new.html
>>
>> Your version (6.1.55-1) of linux-image-6.1.0-13-amd64 appears to be out of
>> date.
>> The following newer release(s) are available in the Debian
On 03.10.2023, Asher Gordon wrote:
> This code is problematic for several reasons.
>
> 1. The elements of 'package' are integers, not strings (I am not sure
> under what circumstances they would be strings). This is what causes the
> crash.
This function is not only called by querybts, but also
control: tags -1 - moreinfo
> Please go ahead and remove the moreinfo tag once the upload happened.
Thank you Paul. Uploaded, removing moreinfo tag.
Nis
+
+ [ Paul Wise ]
+ * Update Linux kernel taint list and location
+
+ [ Nis Martensen ]
+ * debian/control: update standards-version (no changes needed)
+ * reportbug.utils.get_package_status: force literal package name match when
+calling apt-cache show. Thanks to David Kalnischkies
> To avoid the need to update reportbug in a bookworm point release and
> prevent bug 992332 from happening in this release, can we have a version
> of reportbug that does the right thing in bookworm?
Yes we can.
Is it acceptable for us to include one or two other small fixes in the
new version?
Package: lists.debian.org
Severity: minor
X-Debbugs-Cc: nis.marten...@web.de
I'd be interested to learn how the list pages such as
https://lists.debian.org/debian-devel/ are generated. It would be great
if theses pages could provide a hint about that directly.
The background is that I'm
On 12 Jul 2013 Prekates Alexandros wrote:
> Package: apt
> Version: 0.9.7.9
> Severity: normal
>
> Man page of apt-cache dont mentions regex on operations with pkg argument
> ,except from 'search'
>
> But i tested in wheezy and i see that using regex with operation like show ,
> showpkg works.
Please do not send private email. Keep the bug in CC. Thanks.
On 21.01.2023 Heston Corbeil wrote:
> Closing rebortbug discards even more information than what you're
> suggesting and by your own logic would be an even worse user experience.
If there is information in the first attempt that you
Hi Holger,
> then why did I experience this bug in 7.10.3+deb11u1 when you claim
> it has been fixed in 7.9.0?
There was another bug where reportbug often did not find the information
on package section and priority. Due to this, reportbug then detected a
priority change when that was not
On Fri, 02 Dec 2022 Philip Hands wrote> Debian Live images built in the
last day seem not to be able to start X.
>
> It segfaults at start-up, thus:
>
> [20.784] (EE) Backtrace:
> [20.785] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x564d21cafc59]
> [20.787] (EE) 1:
On Sat, 23 Jul 2022 Richard Hector wrote:
> I assume the link above was the old version of
>
> https://www.debian.org/releases/bullseye/amd64/release-notes/ch-moreinfo.en.html#bugs?
No. This is the correct one:
https://www.debian.org/releases/stable/amd64/ch05s04.en.html#submit-bug
On 13.10.2022 16.01, Kent West wrote:
> Or simply a warning that the report stored in /tmp may disappear, so
> the user should make a copy of it to somewhere safe.
I believe /tmp is a good default. Users who want a more permanent
location can already have that, e.g.:
mkdir ~/reportbug && echo
control: reassign -1 libgtk-3-0
control: affects -1 reportbug
control: affects -1 reportbug-gtk
> After submitting a bug, the final page ("Thank you for your report") gets
> mangled by the text-justification engine. (See attached image)
Thank you for your report. I can reproduce this on
On 19.03.2022 23.37, Simon McVittie wrote:
> On Sat, 19 Mar 2022 at 14:17:08 -0700, Don Armstrong wrote:
>> On Sat, 19 Mar 2022, Nis Martensen wrote:
>>> "This bug affects accessibility to users with disabilities. It
>>> particularly impacts usability by people
On 14.03.2022 22.06, Don Armstrong wrote:
> On Mon, 14 Mar 2022, Simon McVittie wrote:
>> Please could the BTS owners provide or approve a clearer wording for
>> this, if they are the "owners" of the tag definition?
>
> I'd like if it includes "accessibility" in the language (so someone can
>
control: forcemerge 1005998 1006408
Thanks Paul. It is a regression since 11.3.0. Fixed in git since last week.
Will upload a new version this weekend. This is the fix:
https://salsa.debian.org/reportbug-team/reportbug/-/commit/929c7066747e48daab84abb79d3c385b6632d763
control: reassign 1003065 python3-apt
On 03.01.2022 16.10, Adolf Markus Berthold wrote:
> Package: reportbug
> Version: 7.10.3+deb11u1
> Severity: normal
> Tags: l10n
>
> Dear Maintainer,
>
> reportbug (console-version) raises an exception when called with the locale
> de_DE@euro :
>
>
(Moving to #712979 for the REST interface thing, and adding Bastian to
recipients)
On 31.12.2021 Don Armstrong wrote in #1002595:
> [Really, it's past time for us to support a REST interface and
> abandon the SOAP interface.]
Just wondering: Don, how much effort would you estimate is this? Do you
Package: python3-openpyxl
Version: 3.0.9-1
Severity: minor
X-Debbugs-Cc: nis.marten...@web.de
Since version 3.0.7 openpyxl no longer depends on jdcal, so the
dependency of the python3-openpyxl package on python3-jdcal can be dropped.
Not sure if jdcal has any other reverse dependencies in
(I've merged #923090 and #996833 since they are asking the same. Adding
Guillem to CC here.)
On 19 Oct 2021 Michael Biebl wrote:
> given the decisions by the CTTE to go with a merged-/usr file system
> layout, I think it would be useful (at least during the transition
> phase), if reportbug
control: tags 853915 + patch
> > Somehow, when the code is run on the BTS server, the MIME::Parser seems
> > to fail and the `parse` function code is falling back to the legacy
> > pre-MIME code. Why?
>
> The reason is that the perl code on the BTS server is executed in taint
> mode, and
On 25 Dec 2021 Mike Frysinger wrote:
> On Sat, 25 Dec 2021 01:26:00 -0500, Mike Frysinger wrote:
> > I get that that bug report has a lot of spam, but debbugs prob shouldn't
> > ever return a with xsi:type other than xsd:long.
>
> err, obviously I meant should always have xsi:type of
control: reassign -1 reportbug-gtk
control: severity -1 important
control: tags -1 - moreinfo
> Update: The bug was introduced with the upload of python3.9 3.9.8-1 to
> unstable on 7 November. Downgrading python3.9 to version 3.9.7-4 fixes
> the problem.
>
> Next tasks: Identify which change
control: reassign -1 python3.9
control: affects -1 reportbug-gtk
> Michael Hatzold hat am 19.11.2021 geschrieben:
>> When using reportbug-gtk I now cannot close it (the window) anymore, not even
>> after sending the email. I can minimize it, but not close. I have to open a
>> VT
>> and pkill
CC'ing the python3.9 maintainer.
On 22.12.2021 00.39, Nis Martensen wrote:
> Hello GTK/Gnome experts,
>
> Would you be able to help with #1000200? Reportbug's GTK UI does not
> close properly any more. It works fine in bullseye, and there was no
> change in reportbug that co
Hello GTK/Gnome experts,
Would you be able to help with #1000200? Reportbug's GTK UI does not
close properly any more. It works fine in bullseye, and there was no
change in reportbug that could have caused this change in behaviour.
On 20.11.2021 13.07, nis.marten...@web.de wrote:
>
> Michael
control: tags -1 moreinfo
Michael Hatzold hat am 19.11.2021 geschrieben:
> When using reportbug-gtk I now cannot close it (the window) anymore, not even
> after sending the email. I can minimize it, but not close. I have to open a
> VT
> and pkill or ctrl-C it (when opened in a VT)
>
> It
control: tags -1 moreinfo
Michael Hatzold hat am 19.11.2021 geschrieben:
> Due to SMTP overload reportbug saved the report to a tmp file.
>
> Sending the report based on the re-opened tmp file resulted in a message along
> the lines: "bug report written to tmp file etc ...", but nothing about
Source: vte2.91
Version: 0.62.3-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: nis.marten...@web.de
According to
https://lazka.github.io/pgi-docs/Vte-2.91/classes/Terminal.html#Vte.Terminal.spawn_async
and
https://lazka.github.io/pgi-docs/#Vte-2.91/classes/Pty.html#Vte.Pty.spawn_async
the order
Source: vte2.91
Version: 0.62.3-1
Severity: minor
Tags: upstream
X-Debbugs-Cc: nis.marten...@web.de
According to
https://lazka.github.io/pgi-docs/Vte-2.91/classes/Terminal.html#Vte.Terminal.spawn_sync
spawn_sync is deprecated and one should use spawn_async instead.
After trying to switch
On 23 Dec 2015 Julian Andres Klode wrote:
> Package: reportbug
> Version: 6.6.5
> Severity: normal
>
> This is somewhat strange:
>
> The snappy package comes from the source package snappy-player, whereas
> there also is a snappy source package that builds some development
> libraries.
>
>
control: tags -1 moreinfo
On 21 May 2014 Adam Borowski wrote:
> Package: reportbug
> Version: 6.5.0
> Severity: normal
>
>
> In current unstable, when you type "reportbug kernel-common", reportbug
> somehow acts as if you wrote "reportbug src:kernel-common". There is no
> binary package by
On 06 Aug 2021 Patrice Duroux wrote:
>
> $ reportbug src:gtk4
>
> W: Unable to locate package gtk4
Reportbug calls apt-cache to look up packages. The warning you received
about the failed package lookup is in fact produced by apt-cache.
Not sure how reportbug can know about packages if even
On 10 Mar 2021 Paul Wise wrote:
>
> The reportbug behaviour differs between src:samba and --source samba,
Even with the bug fixed there is still a small difference. Just
mentioning it here for completeness:
When you use --source then reportbug expects you to give the name of a
binary package and
> Until recently lintian emitted a warning that python3-reportbug uses the dpkg
> database directly. The corresponding code in the reportbug source package has
> not changed, but the warning is gone. Does this mean that the warning was a
> false positive in the first place? Or is the lack of
> Somehow, when the code is run on the BTS server, the MIME::Parser seems
> to fail and the `parse` function code is falling back to the legacy
> pre-MIME code. Why?
The reason is that the perl code on the BTS server is executed in taint
mode, and MIME::Parser fails on multipart messages when run
Hi,
On 18.02.2021 18.04, Holger Wansing wrote:
> Now merged.
Thanks!
> Will upload at the weekend, I think.
A new reportbug upload will follow within 24 hours after you upload.
Nis
(cc'ing the apt maintainers for advice)
> Samuel Thibault hat am 08.02.2021 09:31 geschrieben:
>
>
> Uh, reportbug does it completely wrongly indeed:
>
> $ reportbug libbsd0-udeb
> [...]
>
> Which of the following packages is the bug in?
>
> 1 libbsd-devutility functions from BSD
On 07.02.2021 19.46, Mikael Petersson wrote:
> Nope. No non-ascii characters for my user account entry in /etc/passwd.
> No non-ascii characters whatsoever as far as I can see. No e-mail
> address is specified in my user account entry.
>
> Neither /etc/email-adresses nor /etc/email-addresses
(Please keep the bug in cc.)
On 07.02.2021 19.01, Mikael Petersson wrote:
> Den sön 7 feb. 2021 kl 18:49 skrev Nis Martensen
> Even if you did not type such a non-ascii address into reportbug, it may
> have picked it up from any of the REPORTBUGEMAIL, DEBEMAIL, or EMAIL
>
control: forcemerge 969209 982245
On 07.02.2021 17.14, Mikael Petersson wrote:
>
> Reportbug fails during the initial configuration when I use the default
> Y answer (I press Enter) for direct Internet access. Console output
> during execution:
> [...]
> UnicodeEncodeError: 'ascii' codec can't
Package: installation-report
Severity: normal
Tags: patch
X-Debbugs-Cc: debian-report...@lists.debian.org
What do you think about including the installation-report message
template directly in reportbug?
In reportbug's GTK interface, the output of bugscripts is not handed to
the user for
control: tags -1 moreinfo
On 10.01.2021 09.58, 2704...@gmx.de wrote:
> Package: reportbug
> Version: 7.9.0
>
> Debian testing bullseye
>
>
> When i start reportbug, its crashing, due to python error.
> SystemError: returned a result with an error set
>
> The above exception was the direct
Package: debbugs
Severity: wishlist
X-Debbugs-Cc: nis.marten...@web.de
Let's take bug #711404 as an example:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711404
Here the bug log currently shows four messages. However, when running
`reportbug -u text -N 711404`, you'll be shown 12 messages.
Version: 4.16.0-1
On Mon, 6 Jan 2014 "Alexandra N. Kossovsky" wrote:
I use mutt as e-mail client. mutt itself perfectly handles mailto:
URLs, including the mail body. When using it via xfce, the mail body is gone.
This bug was fixed in Xfce 4.16.
Version: 4.16.0-1
On Mon, 6 Jan 2014 "Alexandra N. Kossovsky" wrote:
I use mutt as e-mail client. mutt itself perfectly handles mailto:
URLs, including the mail body. When using it via xfce, the mail body is gone.
This bug was fixed in Xfce 4.16.
On Mon, 03 Jul 2017 Phil Wyett wrote:
Source: reportbug
Package: reportbug
Version: 7.1.7
Crash while viewing and scrolling through existing bug report.
Crash...
(reportbug:2841): Gdk-ERROR **: The program 'reportbug' received an X
Window System error.
This probably reflects a bug in the
control: reassign -1 python3-reportbug
control: forcemerge 975398 -1
control: forcemerge 975398 -1
On 21.12.2020 22.40, Witold Baryluk wrote:
Package: reportbug
Version: 7.8.0
Severity: normal
X-Debbugs-Cc: witold.bary...@gmail.com
When using gtk interace, and viewing the existing bug, I got this:
Traceback (most recent call last):
File
Package: reportbug
Version: 7.8.1
Severity: normal
X-Debbugs-Cc: nis.marten...@web.de
eins zwei drei
vier fünf sechs
sieben acht neun
-- Package-specific info:
** Environment settings:
EDITOR="vi"
DEBEMAIL="nis.marten...@web.de"
DEBFULLNAME="Nis Martensen"
On 24 Nov 2016 Nancy Anthracite wrote:
* What led up to the situation? I configured report bug to use my email
saying that it required TLS, gave it the email but I was not asked for a port
or a password and when I tried to submit the report, it did not ask me for a
password and it timed out.
control: severity -1 minor
On 14 Feb 2017 James Clarke wrote:
Running reportbug release.debian.org with the GTK UI, when prompted to
choose a suite, the first suite in the list is already selected, and
there is no way to de-select it (at least as far as I can tell). This
means I can't use
control: severity -1 minor
On 05 Feb 2016 Takahide Nojima wrote:
In using gui of reportbug, The page of 'Do any of the following apply to this
report' lacks functionarity that all item set to unselecting. If you would
select a item mistakenly, all item can't set to unselecting.
Yes, just
On 26 Dec 2019 Fabrice BAUZAC-STEHLY wrote:
Version 7.5.3 is really considered newer than 7.5.3~deb10u1 (beware, it
is a tilde, not a dash):
# ge = "greater or equal"
$ dpkg --compare-versions 7.5.3 ge "7.5.3~deb10u1"; echo $?
0 # means "true"
Indeed, according to the Debian Policy [1]:
[1]
Hi Roderich,
AttributeError: 'BugPage' object has no attribute 'isAlive'
Thank you for the report and analysis.
Patch attached.
There is no diff in the attachment - did you send the wrong file?
Hi Adam,
On 24.10.2020 21.01, Adam D. Barratt wrote:
reportbug/debbugs.py: Fix crash with stable-pu update request
[...]
TypeError: not all arguments converted during string formatting
Closes: #964987
Is there an ETA for getting the fix for this issue uploaded? It's been
marked as
Package: python3-debianbts
Version: 3.0.2~bpo10+1
Severity: normal
X-Debbugs-Cc: nis.marten...@web.de
Proxy support in python3-debianbts does not work. The underlying reason
may be a bug in pysimplesoap:
>>> import debianbts
>>> debianbts.set_soap_proxy('http://192.168.12.34:3128')
>>>
Package: lintian
Version: 2.84.0
Severity: minor
X-Debbugs-Cc: nis.marten...@web.de
Dear Maintainers,
Until recently lintian emitted a warning that python3-reportbug uses the dpkg
database directly. The corresponding code in the reportbug source package has
not changed, but the warning is gone.
On 17.07.2020 23.02, Thorsten Glaser wrote:
> Nis Martensen dixit:
>> If this were your developer time, would you want to spend it on that?
>
> Absolutely!
>
> In addition to that, you probably should do that anyway and convert
> between headers and pseudoheaders, s
On 16.07.2020 23.44, Thorsten Glaser wrote:
> Nis Martensen dixit:
>
>> - There is an excellent alternative to setting an x-debbugs-cc header
>> -- you can set it as a pseudoheader. Just add a corresponding line to
>> the pseudoheader section of your repo
On Wed, 15 Jul 2020 Thorsten Glaser wrote:
> Report will be sent to Debian Bug Tracking System
> Submit this report on openssh-server (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|?]?
> s
> Invalid selection.
Thank you Thorsten for your report. The removal of this menu option is
not a bug; this was a
On Mon, 6 Jan 2014 "Alexandra N. Kossovsky" wrote:
>
> I use mutt as e-mail client. mutt itself perfectly handles mailto:
> URLs, including the mail body. When using it via xfce, the mail body is gone.
Please find below a patch that fixes this.
It also moves the "-s subject" option to the
Dear GTK/GNOME list,
I'm looking for help with a problem in the reportbug GTK ui (bug
#964846). The GTK ui has code that uses VTE to run certain commands in a
terminal. These commands include package-specific bug scripts and
user-selected external MUAs used for bug submission. The problem is that
On 12.07.2020 02.44, Paul Wise wrote:
> On Sat, 2020-07-11 at 18:20 +0100, Simon McVittie wrote:
>> It might be safer to build a corresponding mailto:
>> URI (which is desktop-agnostic and can be done in
>> pure Python), and then pass it to whatever is the Python
>> binding for
On Sat, 11 Jul 2020 09:54:48 +0800 Paul Wise wrote:
> Package: python3-reportbug
> Version: 7.7.0
> Severity: normal
> File: /usr/lib/python3/dist-packages/reportbug/mailer.py
>
> The xdg-email MUA maps to the Mailto class, but the Mailto class fully
> encodes the Mailto URL, while xdg-email
e the xdg-email MUA with the reportbug GTK UI, at the
> end there is a brief flash of a black screen but no MUA composer window
> pops up. My default MUA on this GNOME desktop is evolution.
On 11.07.2020 11.34, Paul Wise wrote:
> On Sat, 2020-07-11 at 09:54 +0200, Nis Martensen wrote:
>
On Sat, 11 Jul 2020 09:44:27 +0800 Paul Wise wrote:
> Package: reportbug-gtk
> Version: 7.7.0
> Severity: important
>
> When I try to use the xdg-email MUA with the reportbug GTK UI, at the
> end there is a brief flash of a black screen but no MUA composer window
> pops up. My default MUA on
On Fri, 28 Apr 2006 Paul Wise wrote:
> Package: reportbug
> Version: 3.20
> Severity: wishlist
>
> I would love to be able to select evolution from the MUA menu, making it
> add the message to evolution's Draft folder. At the moment I do this
> through mutt, which I have set to use evolution's
Package: libexo-helpers
Version: 0.12.4-1
Severity: normal
Tags: patch
X-Debbugs-Cc: nis.marten...@web.de
Dear Maintainer,
Thunderbird fails to get launched for certain mailto URIs, while it
works perfectly fine with many others. To reproduce, try
/usr/share/xfce4/exo-1/exo-compose-mail-1
Paul is right, custom mua support outside xdg is not really needed at all.
xdg-email works just fine in a text-only environment, and these users can
simply specify their preferred mailer(s) in the MAILER env var.
> Dave Steele hat am 22.06.2020 20:29 geschrieben:
>
> If I can interpret, it sounds like there are two options on the table -
> something looking like
> https://salsa.debian.org/reportbug-team/reportbug/-/merge_requests/24,
> or a reportbug-ng port. The MR needs, at a minimum, elimination
David Steele wrote:
> chaica wrote:
> > Allowing custom muas outside supported muas exclude the possibility to give
> > feedback to the user about what happened *after* reportbug gave the bug
> > report to the mua. How can reportbug know if your script/custom software is
> > available on your
Package: reportbug
Version: 7.5.3~deb10u1
Followup-For: Bug #412914
I'd prefer if we could avoid introducing a new configuration variable
for this. How about implicitly always using SSL if the user specifies
port 465?
(NB: This message serves as a test for a patch I am preparing.)
On 17 Mar 2020 Josh Triplett wrote:
>
> https://salsa.debian.org/reportbug-team/reportbug/-/merge_requests/55
>
> querybts supports a -m/--mbox option to dump an mbox directly to stdout,
> and an --mbox-reader-cmd option to specify a MUA to read an mbox when
> using the option from the query UI
On 25 May 2020 Patrick ZAJDA wrote:
> When launching the Reportbug GTK, it is not possible to use keyboard
> navigation.
> Nothing happens when I press Tab or Shift+Tab.
Thank you for the report. After receiving your report I have tried to
navigate the GTK UI using only the keyboard, and can
control: merge 712066 939177
> 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.
> >
> >
control: retitle -1 reportbug: newer versions check does not use timeout
control: tags -1 patch
Hi Russell, thanks for the report.
On 01 Jun 2020 Russell Coker wrote:
> I have reportbug hang for HOURS at the above line when trying to talk to
> madison via IPv6. It has an IPv6 https connection
control: tags -1 patch
Michael sent me his draft patch. Slightly modified version with added
commit message attached. Diff is against latest upstream git version.
Thanks Michael!
>From 89399122692823bc215cf1097b05da4ee2201e0e Mon Sep 17 00:00:00 2001
From: Nis Martensen
Date: Sun, 24 May 2
Thanks a lot Noah and Michael for working on this!
Michael Biebl wrote:
> The patch to add sd_notify is rather trivial. Problem is, that dovecot
> unhelpfully clears the full environment. In src/master/main.c,
> sd_notify() should be called around/after main_init().
> Unfortunately, at this point
control: merge 709862 930085
control: tags 709862 patch
> > 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
control: reassign 961092 reportbug
control: merge 919102 961092
control: tags 919102 patch
On 19 May 2020 Real Carbonneau wrote:
> reportbug-gtk crashes after package selection when there is no internet
> connection. It works correctly as soon as an internet connection is present.
Thank you for
control: reassign 853915 bugs.debian.org
control: affects 853915 reportbug
Bug summary:
- Browsing bug logs in reportbug is broken for some messages
- Bug log messages retrieved from the BTS via the SOAP interface
are supposed to be decoded, but in these cases aren't.
- All MIME multipart
> So either something does not work as expected there, or I'm simply
> looking at the wrong code and should be looking somewhere else.
If this is the correct code, then why is it behaving differently when
its is run to serve a soap request, as compared to running it directly,
for the same email
When running e.g. `reportbug -N 853037`, a bunch of base64 is
displayed instead of the actual content of the messages.
> Could the BTS SOAP interface be changed to return the decoded message
> body of signed messages? Being able to deal with all other kinds of
> complex MIME messages
control: tags 936061 patch
> So as a solution reportbug could consider respecting a Submit-As already
> when retrieving the list of existing bugs. It could do this either
> instead of using the actual package name given on the command line, or
> in addition (presenting the union of both lists to
On 31 Aug 2019 Nis Martensen wrote:
> I'm not familiar with reportbug-ng so I cannot tell how you managed to
> find the bug there.
You might have found the bug there simply by searching for bugs in
src:linux, and not in linux-image-5.2.0-2-amd64.
I think the actual problem here is that the
On 14 Feb 2019:
> 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
On Wed, 13 May 2015 13:26:49 -0400 Sandro Tosi wrote:
> On Wed, May 13, 2015 at 1:15 PM, Henriquew wrote:
> > Package: reportbug
> > Version: 6.6.3
> > Severity: normal
>
> empty bug reports are not very useful... would you mind reporting the
> exact, unaltered, traceback you get on the
control: affects -1 - apt-transport-tor
> > Reportbug can't handle onion addresses. Thus when sources.list only
> > contains onion addresses reportbug thinks it is empty.
> >
> > $ reportbug
> > E: You must put some 'source' URIs in your sources.list
>
> The error message comes from "apt-cache
control: tags -1 patch
On 3 Sep 2009 James Vega wrote:
>
> In doing a little more poking around, I see this is only an issue when
> using querybts on a source package. This may simply be an artifact of
> screen-scraping the BTS, but I'd have to do some tests with the BTS'
> SOAP interface to
control: tags -1 unreproducible moreinfo
On Mon, 14 Jan 2019 traumschulerie...@riseup.net wrote:
>
> Reportbug can't handle onion addresses. Thus when sources.list only
> contains onion addresses reportbug thinks it is empty.
>
> $ reportbug
> E: You must put some 'source' URIs in your
1 - 100 of 290 matches
Mail list logo
