Debian contemplates patch management [LWN.net]

Debian contemplates patch management

Posted May 20, 2008 18:00 UTC (Tue) by samroberts (subscriber, #46749)
Parent article: Debian contemplates patch management

Debian developers are a diverse set of people, I don't want to tar them 
all with the same brush, but often they make no effort to collaborate 
with upstream, or even to tell them that their code has been packaged.

I have had some of my code debianized. The package hasn't been updated 
since August 2005! What can I do? As the upstream developer, I've no 
particular rights as regards the packaging of my software. I don't think 
I can request mantainership be passed to me.

It has one large patch .diff.gz, not the debian/patches/ style. Almost 
all of the patch file exists to create the debian-specific files, but 
buried deep in there is also a README.Debian, that includes useful 
information on how to use my code with Evolution. Its not debian 
specific, and I would be happy to accept documentation patches, but it 
was never offerred to me (I know now just because I went searching to see 
if any of my code had been debianized).

I like the suggestion to use the BTS. Whatever is done, every patch 
should have attached to it proof that it was at least offerred upstream 
(copy of email to author, bug# from upstream, something). All developers 
are busy, not just Debian developers, and Debian itself is glacially slow 
in accepting patches. Maybe its frustrating at times, but packagers 
should make at least a token effort!

(Log in to post comments)

Debian contemplates patch management

Posted May 20, 2008 18:44 UTC (Tue) by tzafrir (subscriber, #11501) [Link]

You don't have to argue about who has whatever right. You can ask the original packager to
update the package. The formal way of doing it is to file a wishlist bug on the package. See
http://bugs.debian.org/ (this takes sending an email. No need to create an account or
anything).

If the old package is broken in interesting ways, mention it. If the old package is buggy it
may need to get more love and care, or maybe just get thrown away.

It also sounds like there are no debian/patches/ because the package does not patch anything
in the tarball itself. debian/patches/ are just some of the files created by applying the
.diff.gz .

Debian contemplates patch management

Posted May 20, 2008 23:47 UTC (Tue) by pdewacht (subscriber, #47633) [Link]

I'm guessing you're talking about vpim :)
It looks like the vpim package was removed last year because it went unmaintained. You'll
still see references to it as it was part of a stable release, but it won't be included in
future releases. Unless somebody repackages it of course -- if you're interested in doing that
yourself, check out mentors.debian.net and the debian-mentors mailing list.

Debian contemplates patch management

Posted May 21, 2008 5:42 UTC (Wed) by ajk (subscriber, #6607) [Link]

There are many examples of upstream developers who maintain the Debian packages of their work
within Debian.  What it does require, though, is that they take the time and effort to become
familiar with Debian's policies and procedures, and thus become a part of the Debian
development community.

Being upstream does not confer you any formal rights beyond what you would have otherwise, but
it does lend you some social capital that you can spend to getting the packages under your own
maintainment - assuming you are willing to consider Debian developers your peers and act
accordingly.

As a Debian developer of nearly ten years, I find it shameful that some Debian maintainers do
not cultivate good working relationship with their upstreams.  However, there isn't much I can
do about it, considering that I don't have the time or energy to devote to pushing this
matter.

Debian contemplates patch management

Posted May 21, 2008 7:59 UTC (Wed) by tpo (subscriber, #25713) [Link]

> I have had some of my code debianized. The package hasn't been updated 
> since August 2005! What can I do? As the upstream developer, I've no 
> particular rights as regards the packaging of my software. I don't think 
> I can request mantainership be passed to me.

Maintainership is to some degree a formal affair. As a maintainer you get to decide, OTOH,
nothing prevents you as upstream to do the maintainer's work.

What you can do is apply the Debian diff.gz, include it upstream and improve it. That way, if
Debian's packaged version is in some respect lacking compared to upstream's, users can allways
download your version and build it directly with dpkg-buildpackage. And you can also offer
pre-built Debian packages.

That puts some competition/pressure into the game to offer the "best" package to the user and
can have a healthy effect on "stale" Debian packages. But beware: it can bruise egos, harm the
communication process etc.
*t

Debian contemplates patch management

Posted May 21, 2008 10:30 UTC (Wed) by angdraug (subscriber, #7487) [Link]

What you can do is apply the Debian diff.gz, include it upstream and improve it.

Making your own deb packages is certainly an option, but including debian/ directory in your source will cause pain to Debian maintainers, as well as maintainers of other Debian-based distros. It's one thing to apply a diff.gz that adds debian/ directory where it doesn't exist, and quite another to re-merge your patch to upstream's debian/ directory for every upstream release. If you want to go down that route, keep your debian/ directory somewhere separate.

Also, as stated above, the ideal solution if you're not happy with the way your software is packaged for Debian is to propose to take it over. As long as you are willing and able to comply with Debian policies, most DDs will be happy to hand it over: we don't want to own the package, we only want the software to be part of Debian and play nice with other packages.

Upstream == Debian maintainer

Posted May 22, 2008 6:31 UTC (Thu) by rhertzog (subscriber, #4671) [Link]

> What can I do? As the upstream developer, I've no particular rights as regards the packaging
of my software. I don't think I can request mantainership be passed to me.

Yes you can! Just contact the maintainer and ask to become maintainer or co-maintainer. You
will also need to get an official status in the Debian community. If the lengthy process of
becoming a Debian Developer bothers you (see http://www.debian.org/devel/join/newmaint), just
try to become Debian Maintainer. See http://wiki.debian.org/Maintainers, it's never been as
easy to contribute to Debian by maintaining your own package.

-- Raphael Hertzog