Re: debian package of libzeep
Hi Maarten,
I've uploaded the current state to experimental (due to freeze policy
I did not want to upload a new upstream version to unstable right now).
It would be nice if you could add a DEP3 header description to the
jamfile-patch patch.
Thanks for your work on this
Andreas.
On Sat, May 11, 2019 at 11:13:31PM +0200, Maarten L. Hekkelman wrote:
> Hi Andreas,
>
> I think I should better thank you for your patience with me.
>
> I'm not a big fan of git, to put it mildly...
>
> Anyway, I recreated the patch file. Should work now. Sorry.
>
> best regards,
>
> -maarten
>
> Op 11-05-19 om 22:14 schreef Andreas Tille:
> > Hi Maarten,
> >
> > thanks for your continuous work on this package.
> > Please commit jamfile-patch to the Git repository. I get
> >
> > dpkg-source: error: cannot read libzeep-3.0.5/debian/patches/jamfile-patch: No such file or directory
> >
> > Kind regards
> >
> > Andreas.
> >
> > On Sat, May 11, 2019 at 07:18:12PM +0200, Maarten L. Hekkelman wrote:
> > > Hi Andreas,
> > >
> > > I've checked in a new set of debian files. The remaining problem is a
> > > lintian message:
> > >
> > > file-references-package-build-path
> > >
> > > Now I checked the documentation files, and indeed the build path is there,
> > > but not in actual links. So I think this should not be a show stopper.
> > >
> > > I have to dive into the documentation tools to find out how to prevent this,
> > > or I could add a sed script to fix it afterwards. But I'm not sure if that
> > > is really worth the trouble at this moment?
> > >
> > > Best regards,
> > >
> > > -maarten
> > >
> > >
> > > Op 11-05-19 om 15:14 schreef Andreas Tille:
> > > > file-references-package-build-pathHi Maarten,
> > > >
> > > > On Sat, May 11, 2019 at 03:07:10PM +0200, Maarten L. Hekkelman wrote:
> > > > > 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.
> > > > If you ask me its a very good idea to stick to the Github generated
> > > > tarball. That's pretty common style / best practice and IMHO you are
> > > > asking for trouble when deriving from this feature which is expected by
> > > > several users.
> > > > > 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...
> > > > I admit I have no idea about this documentation generation.
> > > > Thanks for your work on this
> > > >
> > > > Andreas.
> > > >
> > >
> > > --
> > > Maarten L. Hekkelman
> > > Cataloniëstraat 3
> > > 6663NJ Lent
> > >
> > > http://www.hekkelman.com/
> > > +31 (0)24 3480192
> > >
> > >
> >
>
> --
> Maarten L. Hekkelman
> Cataloniëstraat 3
> 6663NJ Lent
>
> http://www.hekkelman.com/
> +31 (0)24 3480192
>
>
--
http://fam-tille.de
Reply to: