proper procedure regarding bug reports

[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.

On Wed, Jan 6, 2010 at 3:34 AM, Patrick Freundt <
patrick.freundt at googlemail.com> wrote:

> On Wed, Jan 6, 2010 at 12:01 PM, Michael Bienia <michael at bienia.de> wrote:
> > You know that your Ubuntu systems also checks for package updates
> > automatically? So it goes online without your consent too.
>
> As I said before, firefox is just one exaple of multiple topics.
>
>
> > And I don't want a dialog popping up asking me if it can look for fresh
> > updates now.
>
> By clean concept, you take a concious decision once that you want
> updates and that you connect to a specific remote host for that and
> then you can let that happen in an automated way in the future.
>
> --
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-devel-discuss/attachments/20100106/8b9897db/attachment.html>