On Wed, Aug 20, 2014 at 05:53:18PM +1200, Hamish wrote:
> Hamish wrote:
> > > grass 6.4.4.packaging is currently (basically) ready in DebianGIS
> > > git.
> Sebastiaan:
> > But not by using git-import-orig. The upstream branch hasn't been
> > updated with the grass_6.4.4.orig.tar.gz contents.
> it was done in the master branch,
> http://git.linuxminded.nl/?p=pkg-grass/grass;a=commit;h=d183a32b883dbad88e0d751d030e177dd90926a0
> tagging is currently incomplete, but known todo and discussed privately.
> ...

Do you mind to discuss NOT privately? 

> > You should run lintian showing all tags after your build to get an
> > idea of what is left to fix before I would consider an upload.
> er, you really think we don't do that and know exactly what they are?
> We've been busy packaging this software for more than a dozen years!
> Not masking false positives and "real but won't-fix in this major
> version" lintian issues is not a bug IMHO.

Bas, the grass package has a long list of lintian issues due mainly to specific
choices of upstream team and historical reasons. It is quite pointless
trying to respect the full policy by patching at every new release,
and it would be also an heavy job (with no hopes of being accepted upstream
for merging). This is well expected for such a scientific program born in 
the 80s and having a very conservative and tiny development team.

> No doubt the main rules file could use a bit of a refresh here and there
> (supporting 'make -j' would be nice), but let's continue this
> conversation on the DebainGIS list, not in a ticket about transitioning
> to wxpython3.0.

I don't understand *why* the d-gis repo is not already up-to-date with an 
branching and tagging for the proper support. It is quite annoying working
with yet-another-git-archive.

Francesco P. Lovergine

Pkg-grass-devel mailing list

Reply via email to