About forwarding bugs and patches to Debian and documenting your changes
nvalcarcel at ubuntu.com
Wed Jun 18 15:25:43 BST 2008
On Wed, 2008-06-18 at 01:25 -0700, Bryce Harrington wrote:
> On Wed, Jun 18, 2008 at 09:44:56AM +0200, Lucas Nussbaum wrote:
> > For example, instead of:
> > + * debian/control: add missing libxext-dev build-dependency (fixes FTBFS).
> > You could write:
> > + * debian/control: add missing libxext-dev b-dep. See
> > + http://wiki.ubuntu.com/Changes/libext-dev
> > + Should be merged in Debian.
> For this last line, something terser would be preferrable and easier to
> synthetically parse (i.e. something that won't be likely to word-wrap).
Yes, but we lucas isn't saying "Do it that way" just giving some
recommendations to get into a "policy" or "good practices" document so
the relations between ubuntu and any upstream will improve.
I'm working on a wiki page about good practices . Feel free to add
whatever you want, but keep in mind that this must be a general upstream
collaboration guide, not just debian.
Key fingerprint = BCE4 27A0 D03E 55DE DA2D BE06 891D 8DEE 6545 97FE
gpg --keyserver keyserver.ubuntu.com --recv-keys 654597FE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/ubuntu-motu/attachments/20080618/1ece734e/attachment-0001.pgp
More information about the Ubuntu-motu