On Sat, Jul 27, 2024 at 3:10 PM Faulk Johnny <johnny.faul...@yahoo.com> wrote: > Yes, I am more than willing to do whatever needs to be done to get this > rolling. If it means I have to roll up my sleeves and learn this in order to > prevent bitrot, so be it. "Be the change you want to see", as the saying goes. > > I have my own private fork of the package that has 4.15 already, so I do have > a some familiarity with how packaging works.
Have you ever used git-buildpackage? The general workflow here is to 1. fork the Salsa repo 2. use gbp import-orig --uscan to import the new version 3. use dch -i to insert a new Debian changelog entry. Update the version number to match the version number you imported. 4. do a test build 5. if the test build works, push your debian/master, pristine-tar, and upstream/latest branches to your Salsa fork as well as the new upstream/4.15 tag (or whatever the version you imported is) 6. Then you could either do 3 merge requests for each of the three branches or try to contact the maintainer directly 7. if you don't hear from the maintainer after a while, you do try to find a mentor or sponsor. See https://mentors.debian.net/ For dch to work for me, I have these lines in my ~/.bashrc DEBEMAIL=jbi...@ubuntu.com DEBFULLNAME="Jeremy Bícha" Thank you, Jeremy Bícha
