[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Getting a patch applied with an unresponsive maintainer



On Mon, May 02, 2022 at 11:03:01AM -0400, songbird wrote:
> 
> Adam Dinwoodie wrote:
> 
> i've sent a private reply since i'm not sure gmane sent the
> Cc: i requested.

It didn't :(

> ...
> > Can anyone give any advice about what my next steps might be if I want
> > to get this patch made more widely available?
> 
>   in looking at the following i see there is a request for
> help and that not much else has happened.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006264
> 
> also look at:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964947

Right.  That's ... not very promising.

>   do you have access to the repository on salsa?

With that hint, I've just found the repository[0].  It looks like the
maintainer created a patch to achieve effectively the same result as my
patch back in July 2019[1].  However, while it's in a branch labelled
"debian/sid", it doesn't appear to actually be available in Sid.

[0]: https://salsa.debian.org/smlx-guest/dhcpcd5
[1]: https://salsa.debian.org/smlx-guest/dhcpcd5/-/commit/62162b20e2fb14336f6d884ec6603ebf1d3ac463

So I guess the question now is: what, if anything, can I do to get that
code into a build and out the door and onto the Debian package
repositories?

> > I'm not a Debian developer, and as best I can tell I'd need to have
> > developer privileges already to be able to kick off a non-maintainer
> > upload.  And I don't think I currently have the spare bandwidth to do
> > justice to becoming a developer (I'm already the maintainer of a few
> > Cygwin packages, plus all of the other obligations of life...).  I am,
> > however, very happy to engage with discussions about patches and
> > approaches.
> >
> > Please keep me on the To/Cc list for any replies; I'm not currently
> > subscribed to this list.
> 
>   i've tried to do that via a Cc but i'm not sure gmane honors
> those.  we'll see...  :)

I'll try to remember to keep an eye on the mailing list archives in case
any other replies fall into the same hole...


Reply to: