Streamline pkgsrc issues: DragonFly developer gained NetBSD commit privilege

John Marino dragonflybsd at
Mon Sep 12 03:22:48 PDT 2011

On 9/12/2011 9:22 AM, Francois Tigeot wrote:
> On Sun, Sep 11, 2011 at 09:21:58PM -0400, Justin Sherrill wrote:
>> > From what I've seen in the Problem Report system, there's a
>> > 'dfly-pkg-people' alias that DragonFly issues get placed with; if you
>> > are in that group, you'll probably catch things directly.
> The pkgsrc people are usually very quick to act. The only exception I've
> found is this dfly-pkg-people@ alias
> Once a PR is assigned to it, you can abandon all hope it will be fixed.
> It would be best to remove this alias IMHO.

I don't know if I'd use the word "usually".  Like most things in life,
it likely depends on who is involved.  If you have already dealt with a
specific maintainer who reacts quickly, then it's appropriate to keep
working through him.

However it can take a while for a PR to even get assigned, and then the
maintainer may sit on it indefinitely without any communication.  If
it's just a simple patch, and especially if it's highly-used package, it
might be more efficient to ping me instead.

I think the dfly-pkg-people idea was probably okay in theory, but it
doesn't sound like it's been too successful so far.


More information about the Users mailing list