[Pkg-xen-devel] Xen bug reports for Xen 4.1 and 4.4 (or even Xen 3.2)

Hans van Kranenburg hans at knorrie.org
Wed Oct 24 19:20:01 BST 2018


Hi list,

I'm planning to start responding to all bts bugs that we have that are
related to Xen versions before Stretch. There's quite a few of those.

If they're clearly a question about the packaging, like #862408, then I
will skip those for now. But stuff like problems with upstream code or
"I cannot boot my Windows ISO with qemu on lenny" (I just made that up
as example) should go away.

What I would propose is:
* Make up some proper standard text which asks the bug submitter if
she/he's still using this version and is still experiencing this problem.
* Announce that we will close the bug after X time if there's no response.

What about:

"""
Hi <Name of Reporter>,

This is about the bug report that you filed before about <title> in the
Debian bug tracker against the Xen packages.

Your bug report was targeted at a Xen package in a Debian distribution
older than the current stable (Stretch).

When starting to deal again with bug reports that are already open for a
longer time, we'd like to have the reporter of the bug confirm that she
or he is still experiencing this problem, so we can spend the effort on
the bugs in a directed way.

Can you please help us by confirming that any of the following scenarios
does apply to your situation?

* I had this problem a long time ago. It was never solved, but I found a
workaround, which is ...
* I had this problem a long time ago, and I solved it by not using Xen
any more, but by doing ...
* I still experience this problem, and I'm still using Xen
3.2/4.1/4.4/etc. I cannot upgrade to Stretch because ...
* I had this problem, and since upgrading to Stretch / Buster / ? it
seems it was solved, and I forgot to report it again. Please close it,
thanks.
* <... what other options here? ...>
* Other: ...

Note that even if you found a solution, it's still very useful to report
it back to our bug tracker. There might be someone else running into the
same problem, who can be helped with your information.

Please note that unless there's a response within a month from now, we
will close it. If you discover this message later, and this case is
important to you, then you can try unarchiving the bug and replying to
it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.

Thanks,
<My name Here>
"""



More information about the Pkg-xen-devel mailing list