Your message dated Sat, 26 Nov 2022 21:55:45 +0100 with message-id <72d1c788-bba2-be49-7ff3-bd64369827ee@web.de> and subject line Re: Bug#1022707: reportbug: attachments aren't recalled with reportbug -r has caused the Debian Bug report #1022707, regarding reportbug: attachments aren't recalled with reportbug -r to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1022707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022707 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: reportbug: attachments aren't recalled with reportbug -r
- From: наб <nabijaczleweli@nabijaczleweli.xyz>
- Date: Mon, 24 Oct 2022 13:41:56 +0200
- Message-id: <20221024114156.ja2uus7gazd4rgxe@tarta.nabijaczleweli.xyz>
- Mail-followup-to: Debian Bug Tracking System <submit@bugs.debian.org>
Package: reportbug Version: 7.10.3+deb11u1 Version: 11.5.1 Severity: normal Dear Maintainer, I very often use reportbug like this: * write report on machine A (sid) * "send" it to `outfile "~/reportbug.report"` * copy the report to machine B (bullseye) * reportbug -r, as instructed, on B; this opens it in neomutt via the `mutt` config option * review, send Often, as one may expect, I want to attach a log, or a diff, or whatever; these appear to be lost. This doesn't appear to be reportbug-version-dependent; when recalling on both machine A and machine B (7.10.3+deb11u1 and 11.5.1) the attachment is forgotten, here's a session from the latter: -- >8 -- $ reportbug -r machine-b/saved-reportbug.report *** Welcome to reportbug. Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'наб <nabijaczleweli@nabijaczleweli.xyz>' as your from address. Will send report to Debian (per lsb_release). Spawning sensible-editor... Report will be saved as ~/reportbug.report Submit this report on reportbug (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|?]? Bug report written to a temporary file. You can resume the unsent report using: reportbug -r /home/nabijaczleweli/reportbug.report Thank you for using reportbug -- >8 -- The attachment /is/ present in the original saved file ‒ I'm attaching saved-reportbug.report and the new one. Best, наб -- Package-specific info: ** Environment settings: INTERFACE="text" ** /home/nabijaczleweli/.reportbugrc: reportbug_version "7.5.3~deb10u1" mode standard ui text email "nabijaczleweli@nabijaczleweli.xyz" outfile "~/reportbug.report" For machine B, the diff is -outfile ... +mutt -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: x32 (x86_64) Foreign Architectures: amd64, i386 Kernel: Linux 5.19.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages reportbug depends on: ii apt 2.5.3+b1 ii python3 3.10.6-1 ii python3-reportbug 11.5.1 ii sensible-utils 0.0.17 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail <none> ii debconf 1.5.79 pn debsums <none> pn dlocate <none> pn emacs-bin-common <none> ii file 1:5.41-4 iu gnupg 2.2.40-1 ii nullmailer [mail-transport-agent] 1:2.2-3+b1 pn python3-urwid <none> pn reportbug-gtk <none> pn xdg-utils <none> Versions of packages python3-reportbug depends on: ii apt 2.5.3+b1 ii file 1:5.41-4 ii python3 3.10.6-1 ii python3-apt 2.3.0+nmu1 ii python3-debian 0.1.48 ii python3-debianbts 3.2.3 ii python3-requests 2.27.1+dfsg-1 ii sensible-utils 0.0.17 python3-reportbug suggests no packages. -- no debconf informationContent-Type: multipart/mixed; boundary="===============0930356783==" MIME-Version: 1.0 From: =?utf-8?b?0L3QsNCx?= <nabijaczleweli@nabijaczleweli.xyz> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: dnsmasq: Voluminous bogus whitespace errors introduced into UCF /etc/dnsmasq.conf Bcc: =?utf-8?b?0L3QsNCx?= <nabijaczleweli@nabijaczleweli.xyz> Message-ID: <166661075594.3170.7846439592074691634.reportbug@szarotka.nabijaczleweli.xyz> X-Mailer: reportbug 11.5.1 Date: Mon, 24 Oct 2022 13:25:55 +0200 This is a multi-part MIME message sent by reportbug. --===============0930356783== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline UGFja2FnZTogZG5zbWFzcQpWZXJzaW9uOiAyLjg3LTEuMQpTZXZlcml0eTogbWlub3IKCkRlYXIg TWFpbnRhaW5lciwKCkkgdXBkYXRlZCBkbnNtYXNxLCBhbmQgZXhwZWN0ZWRseSB0aGVyZSBhcmUg bmV3CmNvbW1lbnRlZC1vdXQgZGVmYXVsdCBvcHRpb25zIGluIGRuc21hc3EuY29uZi4KVGhpcyBp cyBncmVhdCwgSSdtIGhhcHB5IHRvIG1lcmdlIHRoZXNlIGludG8gbXkgY29uZmlnLgoKV2hhdCdz IG11Y2ggbGVzcyBncmVhdCBpcyB0aGUgd2hpdGVzcGFjZSBlcnJvcnMsIG5ldyBpbiB0aGlzIHJl bGVhc2UuCk5hdHVyYWxseSwgdGhlIGRlZmF1bHQgYXB0L3VjZiAiRCIgdXBkYXRlIGFjdGlvbiBk b2Vzbid0IHNob3cKdGhhdCB0aGV5J3JlIHdoaXRlc3BhY2UgZXJyb3JzLCBzbyB0aGVyZSBhcmUg anVzdCBhIGxvdApvZiBpZGVudGljYWwgbGluZXMgaW4gdGhlIGRpZmYuIE1vc3Qgb2YgdGhlbSBh cmUgaW4gdGhlIGNvbW1lbnRzLApzb21lIGFyZW4ndCwgYW5kIHRoYXQncyBtb3JlIHdvcnJ5aW5n LgoKSSd2ZSBhdHRhY2hlZCBhICJjbGVhbiIgKGkuZS4gcmVtb3ZlZCBhbGwgbXkgY3VzdG9taXNh dGlvbikgZGlmZgpwaXBlZCB0aHJvdWdoIGNhdCAtQSB0aGF0IHNob3dzIHRoZSBkaWZmZXJlbmNl cyB1c2VycyB3aWxsIHNlZQoob3IsIHJhdGhlciwgbm90IHNlZSkgYW5kIGhhdmUgdG8gZGVjaWRl IHVwb24uCgpQbGVhc2UgY29uc2lkZXIgZW5mb3JjaW5nIHNvbWUgc29ydCBvZiB0cmltIHJlZ2lt ZW4gaWYgdGhlIHVwc3RyZWFtCmRuc21hc3EuY29uZnMgYXJlIGFsc28gZGFtYWdlZCBsaWtlIHRo aXMuCgpCZXN0LArQvdCw0LEKCi0tIFN5c3RlbSBJbmZvcm1hdGlvbjoKRGViaWFuIFJlbGVhc2U6 IGJvb2t3b3JtL3NpZAogIEFQVCBwcmVmZXJzIHVuc3RhYmxlCiAgQVBUIHBvbGljeTogKDUwMCwg J3Vuc3RhYmxlJykKQXJjaGl0ZWN0dXJlOiB4MzIgKHg4Nl82NCkKRm9yZWlnbiBBcmNoaXRlY3R1 cmVzOiBhbWQ2NCwgaTM4NgoKS2VybmVsOiBMaW51eCA1LjE5LjAtMS1hbWQ2NCAoU01QIHcvMiBD UFUgdGhyZWFkczsgUFJFRU1QVCkKS2VybmVsIHRhaW50IGZsYWdzOiBUQUlOVF9QUk9QUklFVEFS WV9NT0RVTEUsIFRBSU5UX09PVF9NT0RVTEUsIFRBSU5UX1VOU0lHTkVEX01PRFVMRQpMb2NhbGU6 IExBTkc9ZW5fR0IuVVRGLTgsIExDX0NUWVBFPWVuX0dCLlVURi04IChjaGFybWFwPVVURi04KSwg TEFOR1VBR0Ugbm90IHNldApTaGVsbDogL2Jpbi9zaCBsaW5rZWQgdG8gL3Vzci9iaW4vZGFzaApJ bml0OiBzeXN0ZW1kICh2aWEgL3J1bi9zeXN0ZW1kL3N5c3RlbSkKTFNNOiBBcHBBcm1vcjogZW5h YmxlZAoKVmVyc2lvbnMgb2YgcGFja2FnZXMgZG5zbWFzcSBkZXBlbmRzIG9uOgppaSAgZG5zbWFz cS1iYXNlIFtkbnNtYXNxLWJhc2VdICAyLjg3LTEuMQppaSAgaW5pdC1zeXN0ZW0taGVscGVycyAg ICAgICAgICAxLjY1LjIKaWkgIGxzYi1iYXNlICAgICAgICAgICAgICAgICAgICAgMTEuNAppaSAg bmV0YmFzZSAgICAgICAgICAgICAgICAgICAgICA2LjQKaWkgIHJ1bml0LWhlbHBlciAgICAgICAg ICAgICAgICAgMi4xNS4wCmlpICBzeXN2aW5pdC11dGlscyBbbHNiLWJhc2VdICAgIDMuMDUtNgoK ZG5zbWFzcSByZWNvbW1lbmRzIG5vIHBhY2thZ2VzLgoKVmVyc2lvbnMgb2YgcGFja2FnZXMgZG5z bWFzcSBzdWdnZXN0czoKcG4gIHJlc29sdmNvbmYgIDxub25lPgoKLS0gQ29uZmlndXJhdGlvbiBG aWxlczoKL2V0Yy9kZWZhdWx0L2Ruc21hc3EgY2hhbmdlZCBbbm90IGluY2x1ZGVkXQovZXRjL2Ru c21hc3EuY29uZiBjaGFuZ2VkIFtub3QgaW5jbHVkZWRdCgotLSBubyBkZWJjb25mIGluZm9ybWF0 aW9uCg== --===============0930356783== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dndiff" diff --git a/etc/dnsmasq.conf b/etc/dnsmasq.conf.dpkg-new$ index bb4c8ed..2047630 100644$ --- a/etc/dnsmasq.conf$ +++ b/etc/dnsmasq.conf.dpkg-new$ @@ -27,8 +27,8 @@ bogus-priv$ $ # Replies which are not DNSSEC signed may be legitimate, because the domain$ # is unsigned, or may be forgeries. Setting this option tells dnsmasq to$ -# check that an unsigned reply is OK, by finding a secure proof that a DS$ -# record somewhere between the root and the domain does not exist.$ +# check that an unsigned reply is OK, by finding a secure proof that a DS $ +# record somewhere between the root and the domain does not exist. $ # The cost of setting this is that even queries in unsigned domains will need$ # one or more extra DNS queries to verify.$ #dnssec-check-unsigned$ @@ -86,6 +85,16 @@ server=8.8.8.8$ # subdomains to the vpn and search ipsets:$ #ipset=/yahoo.com/google.com/vpn,search$ $ +# Add the IPs of all queries to yahoo.com, google.com, and their$ +# subdomains to netfilters sets, which is equivalent to$ +# 'nft add element ip test vpn { ... }; nft add element ip test search { ... }'$ +#nftset=/yahoo.com/google.com/ip#test#vpn,ip#test#search$ +$ +# Use netfilters sets for both IPv4 and IPv6:$ +# This adds all addresses in *.yahoo.com to vpn4 and vpn6 for IPv4 and IPv6 addresses.$ +#nftset=/yahoo.com/4#ip#test#vpn4$ +#nftset=/yahoo.com/6#ip#test#vpn6$ +$ # You can control how dnsmasq talks to a server: this forces$ # queries to 10.1.2.3 to be routed via eth1$ # server=10.1.2.3@eth1$ @@ -155,7 +164,7 @@ domain=nabijaczleweli.xyz$ # a lease time. If you have more than one network, you will need to$ # repeat this for each network on which you want to supply DHCP$ # service.$ -#dhcp-range=192.168.1.2,192.168.1.254,24h$ +#dhcp-range=192.168.0.50,192.168.0.150,12h$ $ # This is an example of a DHCP range where the netmask is given. This$ # is needed for networks we reach the dnsmasq DHCP server via a relay$ @@ -184,11 +193,11 @@ domain=nabijaczleweli.xyz$ #dhcp-range=1234::2, 1234::500, 64, 12h$ $ # Do Router Advertisements, BUT NOT DHCP for this subnet.$ -#dhcp-range=1234::, ra-only$ +#dhcp-range=1234::, ra-only $ $ # Do Router Advertisements, BUT NOT DHCP for this subnet, also try and$ -# add names to the DNS for the IPv6 address of SLAAC-configured dual-stack$ -# hosts. Use the DHCPv4 lease to derive the name, network segment and$ +# add names to the DNS for the IPv6 address of SLAAC-configured dual-stack $ +# hosts. Use the DHCPv4 lease to derive the name, network segment and $ # MAC address and assume that the host will also have an$ # IPv6 address calculated using the SLAAC algorithm.$ #dhcp-range=1234::, ra-names$ @@ -211,9 +220,9 @@ domain=nabijaczleweli.xyz$ #dhcp-range=1234::, ra-stateless, ra-names$ $ # Do router advertisements for all subnets where we're doing DHCPv6$ -# Unless overridden by ra-stateless, ra-names, et al, the router$ +# Unless overridden by ra-stateless, ra-names, et al, the router $ # advertisements will have the M and O bits set, so that the clients$ -# get addresses and configuration from DHCPv6, and the A bit reset, so the$ +# get addresses and configuration from DHCPv6, and the A bit reset, so the $ # clients don't use SLAAC addresses.$ #enable-ra$ $ @@ -290,11 +295,11 @@ domain=nabijaczleweli.xyz$ # any machine with Ethernet address starting 11:22:33:$ #dhcp-host=11:22:33:*:*:*,set:red$ $ -# Give a fixed IPv6 address and name to client with$ +# Give a fixed IPv6 address and name to client with $ # DUID 00:01:00:01:16:d2:83:fc:92:d4:19:e2:d8:b2$ # Note the MAC addresses CANNOT be used to identify DHCPv6 clients.$ # Note also that the [] around the IPv6 address are obligatory.$ -#dhcp-host=id:00:01:00:01:16:d2:83:fc:92:d4:19:e2:d8:b2, fred, [1234::5]$ +#dhcp-host=id:00:01:00:01:16:d2:83:fc:92:d4:19:e2:d8:b2, fred, [1234::5] $ $ # Ignore any clients which are not specified in dhcp-host lines$ # or /etc/ethers. Equivalent to ISC "deny unknown-clients".$ @@ -350,7 +355,7 @@ dhcp-option=option:router,192.168.1.1$ # Send DHCPv6 option. Note [] around IPv6 addresses.$ #dhcp-option=option6:dns-server,[1234::77],[1234::88]$ $ -# Send DHCPv6 option for namservers as the machine running$ +# Send DHCPv6 option for namservers as the machine running $ # dnsmasq and another.$ #dhcp-option=option6:dns-server,[::],[1234::88]$ $ @@ -555,7 +560,7 @@ dhcp-option=option:router,192.168.1.1$ # Set the DHCP server to enable DHCPv4 Rapid Commit Option per RFC 4039.$ # In this mode it will respond to a DHCPDISCOVER message including a Rapid Commit$ # option with a DHCPACK including a Rapid Commit option and fully committed address$ -# and configuration information. This must only be enabled if either the server is$ +# and configuration information. This must only be enabled if either the server is $ # the only server for the subnet, or multiple servers are present and they each$ # commit a binding for all clients.$ #dhcp-rapid-commit$ --===============0930356783==--Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 From: =?utf-8?b?0L3QsNCx?= <nabijaczleweli@nabijaczleweli.xyz> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: dnsmasq: Voluminous bogus whitespace errors introduced into UCF /etc/dnsmasq.conf Bcc: =?utf-8?b?0L3QsNCx?= <nabijaczleweli@nabijaczleweli.xyz> Message-ID: <166661148757.2060.14738526665742911708.reportbug@szarotka.nabijaczleweli.xyz> X-Mailer: reportbug 11.5.1 Date: Mon, 24 Oct 2022 13:38:07 +0200 UGFja2FnZTogZG5zbWFzcQpWZXJzaW9uOiAyLjg3LTEuMQpTZXZlcml0eTogbWlub3IKCkRlYXIg TWFpbnRhaW5lciwKCkkgdXBkYXRlZCBkbnNtYXNxLCBhbmQgZXhwZWN0ZWRseSB0aGVyZSBhcmUg bmV3CmNvbW1lbnRlZC1vdXQgZGVmYXVsdCBvcHRpb25zIGluIGRuc21hc3EuY29uZi4KVGhpcyBp cyBncmVhdCwgSSdtIGhhcHB5IHRvIG1lcmdlIHRoZXNlIGludG8gbXkgY29uZmlnLgoKV2hhdCdz IG11Y2ggbGVzcyBncmVhdCBpcyB0aGUgd2hpdGVzcGFjZSBlcnJvcnMsIG5ldyBpbiB0aGlzIHJl bGVhc2UuCk5hdHVyYWxseSwgdGhlIGRlZmF1bHQgYXB0L3VjZiAiRCIgdXBkYXRlIGFjdGlvbiBk b2Vzbid0IHNob3cKdGhhdCB0aGV5J3JlIHdoaXRlc3BhY2UgZXJyb3JzLCBzbyB0aGVyZSBhcmUg anVzdCBhIGxvdApvZiBpZGVudGljYWwgbGluZXMgaW4gdGhlIGRpZmYuIE1vc3Qgb2YgdGhlbSBh cmUgaW4gdGhlIGNvbW1lbnRzLApzb21lIGFyZW4ndCwgYW5kIHRoYXQncyBtb3JlIHdvcnJ5aW5n LgoKSSd2ZSBhdHRhY2hlZCBhICJjbGVhbiIgKGkuZS4gcmVtb3ZlZCBhbGwgbXkgY3VzdG9taXNh dGlvbikgZGlmZgpwaXBlZCB0aHJvdWdoIGNhdCAtQSB0aGF0IHNob3dzIHRoZSBkaWZmZXJlbmNl cyB1c2VycyB3aWxsIHNlZQoob3IsIHJhdGhlciwgbm90IHNlZSkgYW5kIGhhdmUgdG8gZGVjaWRl IHVwb24uCgpQbGVhc2UgY29uc2lkZXIgZW5mb3JjaW5nIHNvbWUgc29ydCBvZiB0cmltIHJlZ2lt ZW4gaWYgdGhlIHVwc3RyZWFtCmRuc21hc3EuY29uZnMgYXJlIGFsc28gZGFtYWdlZCBsaWtlIHRo aXMuCgp0ZXN0CgpCZXN0LArQvdCw0LEKCi0tIFN5c3RlbSBJbmZvcm1hdGlvbjoKRGViaWFuIFJl bGVhc2U6IGJvb2t3b3JtL3NpZAogIEFQVCBwcmVmZXJzIHVuc3RhYmxlCiAgQVBUIHBvbGljeTog KDUwMCwgJ3Vuc3RhYmxlJykKQXJjaGl0ZWN0dXJlOiB4MzIgKHg4Nl82NCkKRm9yZWlnbiBBcmNo aXRlY3R1cmVzOiBhbWQ2NCwgaTM4NgoKS2VybmVsOiBMaW51eCA1LjE5LjAtMS1hbWQ2NCAoU01Q IHcvMiBDUFUgdGhyZWFkczsgUFJFRU1QVCkKS2VybmVsIHRhaW50IGZsYWdzOiBUQUlOVF9QUk9Q UklFVEFSWV9NT0RVTEUsIFRBSU5UX09PVF9NT0RVTEUsIFRBSU5UX1VOU0lHTkVEX01PRFVMRQpM b2NhbGU6IExBTkc9ZW5fR0IuVVRGLTgsIExDX0NUWVBFPWVuX0dCLlVURi04IChjaGFybWFwPVVU Ri04KSwgTEFOR1VBR0Ugbm90IHNldApTaGVsbDogL2Jpbi9zaCBsaW5rZWQgdG8gL3Vzci9iaW4v ZGFzaApJbml0OiBzeXN0ZW1kICh2aWEgL3J1bi9zeXN0ZW1kL3N5c3RlbSkKTFNNOiBBcHBBcm1v cjogZW5hYmxlZAoKVmVyc2lvbnMgb2YgcGFja2FnZXMgZG5zbWFzcSBkZXBlbmRzIG9uOgppaSAg ZG5zbWFzcS1iYXNlIFtkbnNtYXNxLWJhc2VdICAyLjg3LTEuMQppaSAgaW5pdC1zeXN0ZW0taGVs cGVycyAgICAgICAgICAxLjY1LjIKaWkgIGxzYi1iYXNlICAgICAgICAgICAgICAgICAgICAgMTEu NAppaSAgbmV0YmFzZSAgICAgICAgICAgICAgICAgICAgICA2LjQKaWkgIHJ1bml0LWhlbHBlciAg ICAgICAgICAgICAgICAgMi4xNS4wCmlpICBzeXN2aW5pdC11dGlscyBbbHNiLWJhc2VdICAgIDMu MDUtNgoKZG5zbWFzcSByZWNvbW1lbmRzIG5vIHBhY2thZ2VzLgoKVmVyc2lvbnMgb2YgcGFja2Fn ZXMgZG5zbWFzcSBzdWdnZXN0czoKcG4gIHJlc29sdmNvbmYgIDxub25lPgoKLS0gQ29uZmlndXJh dGlvbiBGaWxlczoKL2V0Yy9kZWZhdWx0L2Ruc21hc3EgY2hhbmdlZCBbbm90IGluY2x1ZGVkXQov ZXRjL2Ruc21hc3EuY29uZiBjaGFuZ2VkIFtub3QgaW5jbHVkZWRdCgotLSBubyBkZWJjb25mIGlu Zm9ybWF0aW9uCg==Attachment: signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: наб <nabijaczleweli@nabijaczleweli.xyz>, 1022707-done@bugs.debian.org
- Subject: Re: Bug#1022707: reportbug: attachments aren't recalled with reportbug -r
- From: Nis Martensen <nis.martensen@web.de>
- Date: Sat, 26 Nov 2022 21:55:45 +0100
- Message-id: <72d1c788-bba2-be49-7ff3-bd64369827ee@web.de>
- In-reply-to: <20221024114156.ja2uus7gazd4rgxe@tarta.nabijaczleweli.xyz>
- References: <20221024114156.ja2uus7gazd4rgxe@tarta.nabijaczleweli.xyz>
> I very often use reportbug like this: > * write report on machine A (sid) > * "send" it to `outfile "~/reportbug.report"` > * copy the report to machine B (bullseye) > * reportbug -r, as instructed, on B; > this opens it in neomutt via the `mutt` config option > * review, send > > Often, as one may expect, I want to attach a log, or a diff, or whatever; > these appear to be lost. Yes, the purpose of the -r option is to store the text content of the message, not the attachments. This behaviour is documented in the man page: ---- -r TEMPFILE, --resume-saved=TEMPFILE Use this to resume an unsent report previously saved by reportbug. Note that attachments stored in TEMPFILE are ignored; if you want to attach any files you need to do that again. ---- This is deliberate behaviour to avoid any confusion about which versions of attached files are included in the report. Closing accordingly.
--- End Message ---