Hi Oliver, On Wed, Apr 02, 2014 at 04:17:23PM +0200, Oliver Lindemann wrote: > I decided to keep it in science. This is actually also how the > NeuroDebian package it build and how Yaroslav (from NeuroDebian) > proposed it originally . I included an override of the Lintian warning. > (Easy, since Raphael did it already).
That's fine (since it sounds like an educated decision ;-)). > Due to all this changes, I think it is also required to "debchange -i", > right? Well, that's a different pair of shoes. IMHO you right now have way to frequently called debchange. The reason for this statement is that usually your very first == "Initial release" should look like: python-expyriment (<versionstring>-1) unstable; urgency=low * Initial release (Closes: #742639) -- Oliver Lindemann <oliver.lindem...@uni-potsdam.de> <timestamp> and nothing else. The debian/changelog file describes changes *inside* Debian (at least usually) and before a package had its initial upload there are no changes. Does this sound logical? Moreover, before the package is uploaded the first time the target distribution (here "unstable") should be UNRELEASED to set a flag for all team member that no upload has happened yet. So starting a new changelog paragraph like you did is simply wrong. Since you are actually using a version control system all those changes you did document are available via `git log` for your fellow team mates so there is really no point in bloating the initial upload with this information. The situation will change once the first package was really accepted to Debian. Than changes like these become interesting. Thanks for your work on this Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140402203514.gf...@an3as.eu