proper procedure regarding bug reports

[Benjamin Drung]

Am Mittwoch, den 06.01.2010, 07:47 -0800 schrieb Shentino:
> I've sorta had this dance with a problem in mc that, due to improper
> perms on cons.saver, prevented the usage of C-o to flop the screen in
> and out.
> 
> 
> I uploaded a patch that highlighted the problem and I thought that
> someone would eventually get around to testing it.
> 
> 
> Unfortunately, it recently got the wave-off as now it no longer builds
> under Lucid and I'm being asked to test a new upstream version, when I
> know that the fix needed cannot come from upstream on account of the
> fact that I've run into the same problem on Gentoo, with the same
> version I was being asked to test.

You are talking about bug #367318? It was me, who commented on this bug
report. Let me clarify some points: 

* I never wrote that the bug is invalid or does not exist. I just
unsubscribed ubuntu-universe-sponsors.

* I was processing your bug in behalf of ubuntu-universe-sponsor. This
team is for sponsoring debdiffs [1]. The debdiff contains a changelog
entry explaining the changes. When the current package does not build,
the debdiff needs to be updated (at least the version in the changelog).

There are two ways for getting your patch into Ubuntu:

* Create a debdiff out of your patch (in this case adding a new entry to
debian/changelog should do it) and resubscribe ubuntu-universe-sponsor.

* Find someone or wait until someone creates the debdiff and uploads it
to the archive (either directly or through the sponsorship process)

[1] https://wiki.ubuntu.com/SponsorshipProcess

-- 
Benjamin Drung
Ubuntu Developer (www.ubuntu.com) | Debian Maintainer (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <https://lists.ubuntu.com/archives/ubuntu-devel-discuss/attachments/20100107/9c59a6b3/attachment.sig>