Just how do I get a patch related to a plan, when the upstream maintainer does not appear energetic?
I recognize of pests where there is a solution readily available, which has actually been uploaded upstream. Nonetheless, the upstream maintainer hasn't replied to the patch, or used it to the task's resource code.
Would certainly it appropriate to send the solution for incorporation in Ubuntu, and also if so, would certainly I deal with doing this?
The correct means to do this is to first see to it that the plan makes use of a patch system, and also if it does not set it approximately make use of Quilt. There need to be solutions on this website for just how to do that.
After that, create a new variation of the plan making use of dch - i. Add your adjustments (such as use a patch system) to the changelog, add your patch right into the patch system, and afterwards examine the plan (in your area or in a PPA).
From there, you can attach a debdiff to the bug record, tag it "patch", and also start searching for an enroller. A debdiff makes it really simple for a programmer to simply see your most recent variation of the plan (patch consisted of) and also post it themselves.
You can miss several of these actions and also simply attach the patch to the upstream resource code to the bug record, yet after that your enroller would certainly require to do them all for you, which suggests it'll possibly take longer and also it'll be tougher to locate an enroller (given that your plan feels like an unusual one, it is most likely no programmers are also accustomed to it and also hence could be unwilling to use a patch).
The patch can be sent in from of a bug record, or if a record of the concern currently exists, as an comment at launchpad. Please see to it to note the uploaded documents as a patch (there is a checkbox for that), due to the fact that this will certainly make it less complicated for us to locate spots.