[Pkg-running-devel] forerunner 310xt support for garmin-ant-downlaoder

[Ralf Treinen]

On Fri, Oct 18, 2013 at 03:32:33PM +0200, Kristof Ralovich wrote:

> It is a new upstream release, that I had prepared for debian packaging, located
> here:  http://anonscm.debian.org/gitweb/?p=pkg-running/antpm.git;a=summary The
> code is there with history, the master/pristine-tar/upstream barnches are
> there, tags are there. What I'm asking for is review so we could create an
> antpm package for debian unstable (or experimental), maybe think this is called
> someone "sponsoring an upload" for me?

I cloned your git repo, and when I try to build the package:

% git-buildpackage -uc -us
dh clean
   dh_testdir
   dh_auto_clean
   dh_clean
	rm -f debian/antpm.substvars
	rm -f debian/antpm.*.debhelper
	rm -rf debian/antpm/
	rm -f debian/garmin-ant-downloader.substvars
	rm -f debian/garmin-ant-downloader.*.debhelper
	rm -rf debian/garmin-ant-downloader/
	rm -f debian/*.debhelper.log
	rm -f debian/files
	find .  \( \( -type f -a \
	        \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
		 -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
		 -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
		 -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
		\) -exec rm -f {} + \) -o \
		\( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) \)
	rm -f *-stamp
xdelta: expected from file (/tmp/pristine-tar.Y_cpuDTqOL/recreatetarball) of length 2856960 bytes
xdelta: expected from file (/tmp/pristine-tar.Y_cpuDTqOL/recreatetarball) of length 2856960 bytes
pristine-tar: Failed to reproduce original tarball. Please file a bug report.
pristine-tar: failed to generate tarball
gbp:error: Couldn't checkout "antpm_1.12.orig.tar.xz": /usr/bin/pristine-tar returned 25

How did you produce the pristine-tar ? Did you push the upstream tags
to the git repo ?

I see that you have licensed your work under GPL3. Does this also apply 
for the contents of the directory "3rd_party" ?

Also, you have in src/ some files that still carry a GPL-2 header,
for instance FIT.hpp.

Anyway, if I were you I would first concentrate on creating an *upstream*
release of the software, with instructions on how to compile the stuff,
and publish that on the project web site. Until this is done I wouldn't
worry about debian packaging. If that upstream is in a shape where one
can easily compile it on a UNIX platform then you can do the debian
packaging, which then should be trivial.

https://wiki.debian.org/UpstreamGuide might be useful.

-Ralf.