One other option for dealing with getting fixes back to Debian that I don't
recall seeing mentioned in this thread is to join a packaging team in Debian
relevant to an interest area and then just push relevant fixes into the team
VCS. I did that with Debian Python Modules Team myself just
On 18/06/08 at 13:34 -0500, Nicolas Valcarcel wrote:
On Wed, 2008-06-18 at 18:48 +0200, Lucas Nussbaum wrote:
On 18/06/08 at 10:12 -0500, Nicolas Valcarcel wrote:
Thanks for the examples, now i'm clearer on what you meant.
I also think this will we great, but to have a wiki page for
On Tue, 2008-06-17 at 22:10 -0400, Scott Kitterman wrote:
On Tuesday 17 June 2008 21:11, Nicolas Valcarcel wrote:
Hi,
On Tue, Jun 17, 2008 at 5:52 AM, Lucas Nussbaum [EMAIL PROTECTED]
There's a wiki page on
https://wiki.ubuntu.com/UbuntuDevelopment/PatchTaggingGuidelines about
On 17/06/08 at 22:10 -0400, Scott Kitterman wrote:
On Tuesday 17 June 2008 21:11, Nicolas Valcarcel wrote:
Hi,
On Tue, Jun 17, 2008 at 5:52 AM, Lucas Nussbaum [EMAIL PROTECTED]
There's a wiki page on
https://wiki.ubuntu.com/UbuntuDevelopment/PatchTaggingGuidelines about
basically
On 17/06/08 at 20:11 -0500, Nicolas Valcarcel wrote:
On Tue, Jun 17, 2008 at 5:52 AM, Lucas Nussbaum [EMAIL PROTECTED]
Secondly, you generally could improve a lot at documenting your changes.
If you put more effort on properly documenting what you change in your
packages, it would allow
On Wed, 18 Jun 2008 09:46:46 +0200 Lucas Nussbaum
[EMAIL PROTECTED] wrote:
On 17/06/08 at 22:10 -0400, Scott Kitterman wrote:
On Tuesday 17 June 2008 21:11, Nicolas Valcarcel wrote:
Hi,
On Tue, Jun 17, 2008 at 5:52 AM, Lucas Nussbaum
[EMAIL PROTECTED]
There's a wiki page on
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
Thanks for the examples, now i'm clearer on what you meant.
I also think this will we great, but to have a wiki page for every
package and to edit it with every change it's not the best to do IMHO.
On the other hand we can open a bug for the changes and explain
everything there and just include
On Wed, 2008-06-18 at 09:13 -0700, Jordan Mantha wrote:
This of course assumes the person writing the changelog entry actually
knows the answer to those questions. As you say, it requires a lot of
effort on the part of the DD. I think it probably takes at least the
same if not more effort on
On 18/06/08 at 10:12 -0500, Nicolas Valcarcel wrote:
Thanks for the examples, now i'm clearer on what you meant.
I also think this will we great, but to have a wiki page for every
package and to edit it with every change it's not the best to do IMHO.
On the other hand we can open a bug for
On 18/06/08 at 09:13 -0700, Jordan Mantha wrote:
On Wed, Jun 18, 2008 at 12:44 AM, Lucas Nussbaum
[EMAIL PROTECTED] wrote:
On 17/06/08 at 20:11 -0500, Nicolas Valcarcel wrote:
On Tue, Jun 17, 2008 at 5:52 AM, Lucas Nussbaum [EMAIL PROTECTED]
snip
Linking to bugs is a good thing, but many
On Wed, 2008-06-18 at 18:48 +0200, Lucas Nussbaum wrote:
On 18/06/08 at 10:12 -0500, Nicolas Valcarcel wrote:
Thanks for the examples, now i'm clearer on what you meant.
I also think this will we great, but to have a wiki page for every
package and to edit it with every change it's not
Lucas Nussbaum wrote:
I didn't mean that there should be one wiki page per package. Only that
there should be one wiki page (or one section on the same wiki page) for
each class of change. In the case of libext-dev, there was probably at
least 20 packages affected by that change, where the
On 18/06/08 at 21:22 +0200, Emilio Pozuelo Monfort wrote:
Lucas Nussbaum wrote:
I didn't mean that there should be one wiki page per package. Only that
there should be one wiki page (or one section on the same wiki page) for
each class of change. In the case of libext-dev, there was
Hi,
As you might have read in [1], I worked on exporting more info about
packages in Ubuntu to the Debian infrastructure, specifically the Debian
PTS[2] and the Debian Developer Packages Overview[3].
[1] http://www.lucas-nussbaum.net/blog/?p=295
[2] http://packages.qa.debian.org/d/dpkg.html
[3]
Hi,
On Tue, Jun 17, 2008 at 5:52 AM, Lucas Nussbaum [EMAIL PROTECTED]
wrote:
Hi,
As you might have read in [1], I worked on exporting more info about
packages in Ubuntu to the Debian infrastructure, specifically the Debian
PTS[2] and the Debian Developer Packages Overview[3].
[1]
On Tuesday 17 June 2008 21:11, Nicolas Valcarcel wrote:
Hi,
On Tue, Jun 17, 2008 at 5:52 AM, Lucas Nussbaum [EMAIL PROTECTED]
There's a wiki page on
https://wiki.ubuntu.com/UbuntuDevelopment/PatchTaggingGuidelines about
basically the same thing (it documents the changes in the patches,
17 matches
Mail list logo
