[Pkg-kde-talk] Packaging of KDevelop

[Jeremy Laine]

Hi Christopher,

> Sounds very reasonable. If you continue to get no response even after NMUing
> the package, then you might want to just add yourself to the Uploaders of
> KDevelop, even if Norman Jordan still doesn't respond.

I have been doing quite a bit of cleanup in KDevelop's bugs (a number of bugs
were reported against KDevelop2 and no longer apply) and my second NMU of
KDevelop3 should be going into unstable today, bringing the total of "fixed in
NMU" bugs to 17:

http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=src&data=kdevelop3&archive=no&pend-inc=pending-fixed&pend-inc=fixed

I still haven't had any sort of reply from Norman Jordan so I think I'll take up
your suggestion of adding myself to the Uploaders field. However, I'd like to do
this "the right way", I do not wish to be accused of hijacking KDevelop! How
should I announce my intentions, an email to Norman Cc'd to debian-devel at l.d.o?
Also, in the first upload where I am in the "Uploaders" field, should I
acknowledge my own NMUs?

In the long run I'd like to bring the packaging in KDevelop in line with the
best practices that the Debian Qt/KDE Maintainers have developed, as the
current packaging of KDevelop is full of cruft inherited from old versions. One
of my problems is that the upstream tarballs include a very much outdated
version of debian/*. Do you have the same problem in any of the KDE packages,
and if so how do you handle it?

Thanks in advance for your advice!

Kind regards,
Jeremy

--
http://www.jerryweb.org/             : JerryWeb.org
http://sailcut.sourceforge.net/      : Sailcut CAD
http://opensource.polytechnique.org/ : Polytechnique.org Free Software