Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I know of bugs where there is a fix available, which has been posted upstream. However, the upstream maintainer hasn't responded to the patch, or applied it to the project's source code.

Would it be suitable to submit the fix for inclusion in Ubuntu, and if so, would I go about doing this?

share|improve this question
add comment

3 Answers 3

up vote 2 down vote accepted

The patch can be submitted in from of a bug report, or if a report of the issue already exists , as an comment at launchpad. Please make sure to mark the uploaded file as a patch (there is a checkbox for that), because this will make it easier for us to find patches.

share|improve this answer
    
I've already done that - I assume the bug folks are pretty busy, and this is a fairly low-priority package. Is it possible to help out by proposing some kind of patch to the package metadata myself? –  Jeremy Kerr Jul 29 '10 at 4:21
    
Which package? Have you also tried forwarding the bug to Debian? –  lfaraone Jul 29 '10 at 4:23
    
libmeanwhile1. How do I forward the bug to Debian? –  Jeremy Kerr Jul 29 '10 at 4:26
1  
Search for the bug on bugs.debian.org and if the bug already exists, then post your patch over there. Else, look to see whether the bug is Ubuntu only (look at patches.ubuntu.com and see if your patch has anything to do with ubuntu changes to that packages, ask someone on debian to test that package for you, use a VM, etc). If the bug affects debian also, report it using any of the tools available (reportbug package, email, etc) and add your patch there. –  Umang Jul 29 '10 at 6:16
    
@Umang: awesome, thanks –  Jeremy Kerr Jul 29 '10 at 8:02
add comment

Here's a pretty decent rundown for historical linkage: https://wiki.ubuntu.com/Bugs/HowToFix

share|improve this answer
add comment

The proper way to do this is to first make sure that the package uses a patch system, and if it doesn't set it up to use Quilt. There should be answers on this site for how to do that.

Then, create a new version of the package using dch -i. Add your changes (such as use of a patch system) to the changelog, add your patch into the patch system, and then test the package (locally or in a PPA).

From there, you can attach a debdiff to the bug report, tag it "patch", and start hunting for a sponsor. A debdiff makes it very easy for a developer to just see your latest version of the package (patch included) and upload it themselves.

You could skip some of these steps and just attach the patch to the upstream source code to the bug report, but then your sponsor would need to do them all for you, and that means it'll probably take longer and it'll be harder to find a sponsor (since your package seems like an uncommon one, it's likely no developers are even familiar with it and thus might be reluctant to apply a patch).

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.