Re: debian package of libzeep

["Maarten L. Hekkelman" <maarten@hekkelman.com>]

Hi Andreas,

OK, I know what happened....

Github creates a libzeep-x.x.x.tar.gz file as a convenience for each 
release. But I created my own dist file called libzeep-x.x.x.tgz and put 
it on github as a downloadable release file. And guess what, they 
contain different things. The one I created contains preformatted html 
pages where as the github generated file contains only the raw sources 
and makefiles. Oh, and I edited the makefile a bit, which caused to 
quilt complain.

So I will need to fix the debian package to create documentation on the 
fly. This is taking way more time than I had hoped for...

best regards,

-maarten


Op 11-05-19 om 13:16 schreef Andreas Tille:
> Hi Marten,
>
> On Sat, May 11, 2019 at 11:18:31AM +0200, Maarten L. Hekkelman wrote:
> > Hi Andreas,
> >
> > That is strange.
> >
> > I just retried:
> >
> > - checkout a fresh libzeep copy from salsa
> > - copy the libzeep-3.0.5.tgz file from github and rename it to
> > libzeep_3.0.5.orig.tar.gz
> That's not needed.  I added the metadata to pristine-tar branch
> (see Debian Med team policy[1]).  Than you can do
>
>     gbp buildpackage
>
> (which should recreate a byte identical upstream tarball).
>
> You should also be able to do
>
>     quilt push -a
>
> inside the fresh Git clone.
>
> > - run dpkg-source -b .
> > - run dpkg-buildpackage -us -uc
> >
> > And I end up with a couple of fine .deb files.
> That's strange.
>   
> > Are you sure you have the correct upstream file?
> If I run git buildpackage it creates
>
> $ md5sum libzeep_3.0.5.orig.tar.gz
> f984d5236b9b15a532886411794c05df  libzeep_3.0.5.orig.tar.gz
>
> That's identical to what I get when I run
>
>     uscan --force-download
>
> Kind regards
>
>        Andreas.
>
>
> [1] https://med-team.pages.debian.net/policy/#gbp-buildpackage

--
Maarten L. Hekkelman
Cataloniëstraat 3
6663NJ Lent

http://www.hekkelman.com/
+31 (0)24 3480192