Devuan bug report logs -
#92
bugs.devuan.org: cannot file bugs against source packages
Reported by: Paul Wise <pabs@debian.org>
Date: Mon, 29 May 2017 05:48:01 UTC
Severity: normal
Tags: ascii
Merged with 135
Done: Mark Hindley <mark@hindley.org.uk>
Full log
🔗
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Mon, 27 Jan 2020 16:56:17 +0000
with message-id <20200127165617.GB14807@hindley.org.uk>
and subject line Re: bugs.devuan.org: cannot file bugs against source packages
has caused the Devuan bug report #92,
regarding reportbug doesn't include a Package header, then complains about no Package header
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.devuan.org
immediately.)
--
92: https://bugs.devuan.org/cgi/bugreport.cgi?bug=92
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems
[Message part 2 (message/rfc822, inline)]
Package: reportbug
Version: 7.1.6+devuan2.1
Severity: important
Dear Maintainer,
When filing a recent bug against network-manager, reportbug found a list
of possible packages, including "network-manager". In the bug report's
pseudo-header, reportbug put "Source: network-manager", not "Package:
network-manager".
After filling out the rest of the bug report, no errors were noted by
reportbug prior to sending the bug report. About 20 minutes later, I
received an email saying:
> Your message didn't have a Package: line at the start (in the
> pseudo-header following the real mail header), or didn't have a
> pseudo-header at all.
>
> This makes it much harder for us to categorise and deal with your
> problem report. Please _resubmit_ your report to submit@bugs.devuan.org
> and tell us which package the report is on. For help, check out
> http://bugs.devuan.org//Reporting.html.
Either reportbug should check for this omission or the Devuan bug
tracker should accept Source: headers as a substitute.
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /home/vmadmin/.reportbugrc:
reportbug_version "7.1.6+devuan2.1"
mode standard
ui text
realname "John Franklin"
email "franklin@tux.org"
-- System Information:
Distributor ID: Devuan
Description: Devuan GNU/Linux 2.0 (ascii)
Release: 2.0
Codename: ascii
Architecture: x86_64
Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages reportbug depends on:
ii apt 1.4.7
ii python3-reportbug 7.1.6+devuan2.1
pn python3:any <none>
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn claws-mail <none>
pn debconf-utils <none>
pn debsums <none>
pn dlocate <none>
pn emacs23-bin-common | emacs24-bin-common <none>
ii file 1:5.30-1
pn gir1.2-gtk-3.0 <none>
pn gir1.2-vte-2.91 <none>
ii gnupg 2.1.18-6
ii postfix [mail-transport-agent] 3.1.4-7
ii python3-gi 3.22.0-2
pn python3-gi-cairo <none>
pn python3-gtkspellcheck <none>
pn python3-urwid <none>
ii xdg-utils 1.1.1-1
Versions of packages python3-reportbug depends on:
ii apt 1.4.7
ii file 1:5.30-1
ii python3-debian 0.1.30
ii python3-debianbts 2.6.1
ii python3-requests 2.12.4-1
pn python3:any <none>
python3-reportbug suggests no packages.
-- no debconf information
[Message part 3 (message/rfc822, inline)]
Paul and John,
I have tested src:package bug sumission today and it is working
normally. So closing as fixed, possibly with the upgrade to debbugs
2.6.0.
Thanks.
Mark
Send a report that this bug log contains spam.