[Utnubu-discuss] How to package an utnubu listed package "the right way"?

[Joachim Breitner]

Hi Marcos,

first note that the utnubu team is currently non functional, but I can
try to answer your questions anyways.

Am Donnerstag, den 15.05.2008, 21:49 +0100 schrieb Marcos Torres Marado:
> As you can see in http://bugs.debian.org/481078 , I recently
> submitted an ITP for the "konq-kim" package, one of those
> packages that exist in Ubuntu but not in Debian. I searched
> in the wiki, but I found nowhere any sort of guidelines on how
>  to deal with doing a new Debian package that already exists
> in Ubuntu.
> 
> This particular package have some good changes made by
> Ubuntu that would be nice to have in Debian but that aren't in
> upstream (I don't know if they were submited, I think I
> could/should do that), also I think we would benefict in using
> the Ubuntu package as a base, and that Ubuntu would benefict
> with the process of making this package into Debian since, for
> instance, at the moment it pops some lintian warnings that
> would be fixed.
> 
> So, what are your suggestions? Should I contact the Ubuntu
> maintainer? What should I purpose?

Contacting the ubuntu maintainer is never a bad idea. 

I think what you should do is take their source package, increase the
version number to the next "debian style", so in this case 
0.9.4-1 instead of 0.9.4-0ubuntu1, by adding a changelog entry, but
leaving their changelog entries in tact. Then proceed with the upload as
usual (using mentors.debian.org or your personal sponsor).

I hope that helps,
Joachim
-- 
Joachim "nomeata" Breitner
Debian Developer
  nomeata at debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nomeata at joachim-breitner.de | http://people.debian.org/~nomeata
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.alioth.debian.org/pipermail/utnubu-discuss/attachments/20080516/43d5b4d5/attachment.pgp