Your message dated Sat, 8 Jul 2017 19:20:03 -0700
with message-id <[email protected]>
and subject line Re: Bug#817191: bugs.debian.org: Version pseudoheader ignored
has caused the Debian Bug report #817191,
regarding psuedoheader parsing does not properly deal with multi-part messages
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 [email protected]
immediately.)
--
817191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817191
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bugs.debian.org
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817128#23 is a
message sent to -done with Version pseudoheader. The bug was closed,
but fixed version wasn't recorded. (Maybe it's because the message is
multi-part?)
--
Jakub Wilk
--- End Message ---
--- Begin Message ---
On Wed, 09 Mar 2016, Don Armstrong wrote:
> Control: retitle -1 psuedoheader parsing does not properly deal with
> multi-part messages
>
> On Wed, 09 Mar 2016, Jakub Wilk wrote:
> > * Colin Watson <[email protected]>, 2016-03-08, 22:46:
> > >On Tue, Mar 08, 2016 at 10:17:12PM +0100, Jakub Wilk wrote:
> > >>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817128#23 is a message
> > >>sent to -done with Version pseudoheader. The bug was closed, but fixed
> > >>version wasn't recorded. (Maybe it's because the message is multi-part?)
> > >
> > >IIRC Version is only honoured if there's also a Package or Source
> > >pseudo-header.
> >
> > Hmm, I've never seen lone Version fail to work before.
> > Latest example were I saw it did the job is #772705.
>
> Yeah, I think this is the multi-part causing an issue.
>
> I bet if you resend the message without that it will work.
>
> I should write a test case for this bug and fix it properly.
I found two things; one the bug used a non-breaking space instead of a
normal space, and it was also a multipart mime.
However, I've now created a test which mimics that exactly, and I can no
longer reproduce the issue. Let me know if you find another case of this
happening, and I'll try to produce a better test message. [It's likely
that I fixed the mail->utf8 conversion at some point which incidentally
fixed this issue.]
--
Don Armstrong https://www.donarmstrong.com
I would like to be the air
that inhabits you for a moment
only. I would like to be that unnoticed
& that necessary.
-- Margaret Atwood "Poetry in Motion" p140
--- End Message ---
