[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#763819: hdf4 not ready for sponsering



On Fri, Oct 03, 2014 at 11:53:21PM +0200, Johan Van de Wauw wrote:
> > I'd like to sponsor this package as requested on SoB Wiki page but there
> > are several lintian issues (including errors) which would cause an
> > auto-reject:
> 
> Thanks for taking time to review and sorry for your time. I'll try to
> find out what went wrong because I'm pretty sure that at least the
> lintian errors should not be present (they were present before and
> thought I fixed them in this upload).

OK, just touch the Wiki page if this is fixed or send an e-mail.

> Just two more questions/comments:
> 
> >
> > W: libhdf4-alt-dev: copyright-refers-to-versionless-license-file usr/share/common-licenses/GPL
> > W: libhdf4g-dev: copyright-refers-to-versionless-license-file usr/share/common-licenses/GPL
> > W: libhdf4-doc: copyright-refers-to-versionless-license-file usr/share/common-licenses/GPL
> >
> > seems to be easy to fix
> 
> Not really, since this license refers to the debian packaging work.
> The only reference points to this directory. I will ask the copyright
> holders to choose a version. Strictly speaking they might even have
> referred to different versions of the GPL.

This warning would not really stop me from sponsering if I just know
that it is somehow reflecting the history.
 
> > W: libhdf4 source: debian-watch-file-in-native-package
> > W: libhdf4 source: native-package-with-dash-version
> >
> > looks suspicious.  There are other not that important things but I'd
> > call the package in a bad state.
> Indeed suspicious and strange, I didn't get these. Wonder what went
> wrong. Probably something while rebasing.
> 
> Just a final remark: I am planning to make more changes (build only
> one library version without netcdf) after the freeze (it will require
> a transition). This can make the d/rules files and patches much
> easier. I'm now focusing on fixing bugs and ignoring some lintian
> errors, since it seems more useful to fix them when a "proper" package
> is built. Anyway, it had 134 lintian warnings before I started working
> on it, so it is definitely improving :-)

:-)
I'm pretty sure that you improved the package.

Thanks for your work on this

       Andreas. 

-- 
http://fam-tille.de


Reply to: