Hi Iain, On Mon, Jul 20, 2020 at 5:02 AM Iain Parris <ipv2....@parris.org> wrote: > Wow! That was extremely fast. Thank you so much Utkarsh - very much > appreciated. :-)
Hehe, you're welcome! \o/ > Excerpts from Utkarsh Gupta's message of 2020-07-20 04:28:33 +0530: > Thank you (x5)! That's wonderful to hear. There are two new upstream > maintainers (I am one), and we've both previously been using Sup for > many years before we volunteered to pick up the maintenance, so we're > planning to maintain upstream for the long term. That's awesome! > I would be very happy to help in anyway that I can with the maintenance > of sup-mail in Debian too, following your lead. For example, would you > like me to fork in Salsa, and take a look at the failing pipeline, to > see if we can get to a green build in Debian? Most certainly! I have granted you push access to the git repository, which means you can essentially push commits to ruby-team/sup-mail repository. (I believe that even if someone messes up somewhere, things can always be reverted! So just push directly and I'll keep reviewing those changes! \o/) So the Debian maintenance is a bit different from upstream development. Here, we have 3 branches: master, upstream, and pristine-tar. Described in https://wiki.debian.org/Teams/Ruby/Packaging/#Git_workflow. I can help you quickly understand the basic workflow of packaging. The best place would be #debian-ruby at OFTC (on IRC). Please free to join there and ping me, my nick is utkarsh2102. > And one small initial request: thank you for adding the new build > dependencies on ruby-optimist and ruby-unicode-display-width. Please > could you also remove the old build dependency on ruby-trollop? > (ruby-optimist replaced ruby-trollop.) Eeks, I should've done that in the first place. Anyway, since you want to contribute to Debian, would you like to do that yourself? :) (now that you have commit access to sup-mail, just clone the repository, do the changes, commit and push! \o/) Let me know if you face any problems!? > > Also, the most important part where you can really help is when I forward > > some patches/issues upstream, maybe you can take a look at them and > > provide a fix so it's more easier to maintain the package on the Debian > > side! :) > > Yes definitely, I'm of course very happy to do this. I've subscribed > myself to this mailing list, so you can reach me here. Or the upstream > mailing list is <sup...@googlegroups.com>. That's lovely, great! > Or upstream pull requests and/or issues on GitHub are always very > welcome: https://github.com/sup-heliotrope/sup/>. Nice! I'll forward dropping-the-git patch. So hopefully you'll see a PR soon! :) > Huge thank you again Utkarsh - I wasn't expecting such a friendly > response. But I can see for myself, you are friendly here, just like you > said. :-) You're very welcome! Everyone is ;) Best, Utkarsh
