[email protected] wrote: > >Zitat von Scott Kitterman <[email protected]>: > >> On Thursday, June 13, 2013 11:09:19 AM [email protected] wrote: >>> Hello Masters, >>> >>> we use some packages from "universe" repository for which we like to >>> push updates/bugfixes. Until now we have re-build some of these for >>> our own use to get long standing bugs fixed, but IMHO it would be >>> better to fix the package in the repo so others get the fixes also? >>> Can someone explain what is the preferred way to for example get >bugs >>> fixed in the cyrus package? >>> >>> Can we help to prepare a merge of the actual source in the >>> ubuntu/debian build? >>> Who should be contacted to get something included? >>> >>> Thanks for any comments >> >> If you can prepare a debdiff (see the debdiff program in the >devscripts >> package), file a bug against the package in Launchpad that explains >the >> problem, then attach the debdiff to the bug and subscribe the >ubuntu-sponsors >> team to the bug, someone from that team will review it for upload to >the >> Ubuntu archive. >> >> Scott K > >Thanks, > >is it also possible to get "in-sync" with official sources somehow >because there are at least 5 bugs we are concerned that are fixed on >the way from cyrus 2.4.12 in Ubuntu 12.04 LTS to the latest 2.4.17 >source distribution. As far as i understand debdiff this is per-bug >and therefore will miss the ~30 other bugs for example if we only fix >our 5 top priorities? Or is it possible/recommended to use debdiff to >go from 2.4.12 -> 2.4.17 ? >I'm aware that this is not possible for the "main" repository, but i >don't know if this also apply to "universe".
The rules are the same. If you can find the upstream commits and cherrypick them, we can take a debdiff for those. Scott K -- Ubuntu-motu mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
