Hi, No need to Cc me: I am subscribed to d-m mailing list.
> While Alioth is down, there are > http://cgit.osdyson.org/open-axiom.git/ > and > https://github.com/ip1981/open-axiom-debian Great! This helps. Let's see. $ uscan --report Processing watchfile line for package open-axiom... Newest version on remote site is 3058, local version is 1.5.0~svn3056+ds (mangled local version number 056) open-axiom: Newer version (3058) available on remote site: http://sourceforge.net/p/open-axiom/code/3058/ (local version is 1.5.0~svn3056+ds, mangled local version number 056) It looks as a typo in debian/watch file. Just replace string: opts=dversionmangle=s/.*svn.(\d+)(.ds.*)?/$1/ \ by string: opts=dversionmangle=s/.*svn(\d+)(.ds.*)?/$1/ \ And it will work fine. https://github.com/ip1981/open-axiom-debian/commit/ae0ede2 Files: debian/* -Copyright: 2011, Igor Pashev <pashev.i...@gmail.com> +Copyright: 2013, Igor Pashev <pashev.i...@gmail.com> I suppose it should be: +Copyright: 2011-2013, Igor Pashev <pashev.i...@gmail.com> Also why did you choose WTFPL-2 license for the package? Usually it is good idea to use the same license as program uses, especially in cases with permissive licenses like BSD. This is just a question. But if you change it, your d/copyright will be a bit simpler and shorter. These copyright holders are still not listed in your d/copyright: Leslie Lamport Free Software Foundation, Inc X Consortium M.Bronstein and INRIA Some files in the source tree are licensed under GPL-2+ and Expat licenses. But I have checked only [1] output. Please have in mind that it includes not full info and all blocks with "Copyright: *No copyright*" and "License: UNKNOWN" should be checked manually. [1] licensecheck --copyright -c . -r . | /usr/lib/cdbs/licensecheck2dep5 > ../copyright_ Except small notes above your package looks fine for uploading. And how about maintaining this package under umbrella of Debian Science Team? Do not think that I am asking something strange. Debian has a very good tendency of increasing the number of team-maintained packages [2]. If you choose to maintain this package in the team, it will not change your workflow too much. You may just move your VCS repo and update d/control a bit, and ignore other team-related features. As a bonus you will find many DDs interested in sponsoring your package, in helping with patches, etc. [2] http://www.lucas-nussbaum.net/blog/wp-content/uploads/2013/03/comaint.png Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
