Excerpts from Kasper Dupont's message of Sat Apr 28 08:14:44 UTC 2012:
> I'm still a bit new to Ubuntu. I'm more experienced with rpm based
> systems. I haven't figured out the exact steps I need to do in order to
> build a patched version of an ubuntu package, but if you could point me
> at instructions that shows me how to build and install a modified deb
> package, I'll have a patch ready for you in "no time".
In this case, I think we'd want to just *backport* the precise upstream
version completely, since almost all changes should have been to add new
mappings of networks and tlds, or fix major bugs. Please verify that in
the upstream changelog before submitting that as a fix though. If that
is the case, I think we can waive the usual "no new upstream" rule for
stable release updates.
Excerpts from Kasper Dupont's message of Sat Apr 28 08:14:44 UTC 2012:
> I'm still a bit new to Ubuntu. I'm more experienced with rpm based
> systems. I haven't figured out the exact steps I need to do in order to
> build a patched version of an ubuntu package, but if you could point me
> at instructions that shows me how to build and install a modified deb
> package, I'll have a patch ready for you in "no time".
Certainly!
http:// developer. ubuntu. com/packaging/ html/ /wiki.ubuntu. com/StableRelea seUpdates
https:/
In this case, I think we'd want to just *backport* the precise upstream
version completely, since almost all changes should have been to add new
mappings of networks and tlds, or fix major bugs. Please verify that in
the upstream changelog before submitting that as a fix though. If that
is the case, I think we can waive the usual "no new upstream" rule for
stable release updates.
Thanks!