> More important is that some dfsg files are still in the git tree.
> MATLAB/{spypart.m,time.m} and DOC/*ug.pdf.
Aha yes. (Is the user guide really nonfree?)
Unfortunately, I have no experience with automatically creating dfsg
tarballs, and there's a fair chance I'll do it incorrectly. I'd appreciate
if someone could take over from here.
Cheers,
Nico
On Fri, May 20, 2016 at 12:48 PM Drew Parsons <dpars...@debian.org> wrote:
> On Fri, 2016-05-20 at 09:49 +0000, Nico Schlömer wrote:
> > I've pushed some more changes to [1] (including a patch) and it's now
> > compiling and installing alright. I guess a review would be in order.
> >
> > Cheers,
> > Nico
> >
> > [1] alioth:/git/debian-science/packages/superlu.git
>
>
> Thanks Nico.
>
> I suggest some dfsg changes. At the moment the upstream version
> is 5.2.0+dfsg. I like to enumerate the dsfg, 5.2.0+dfsg1, in case
> someone later spots another dfsg issue that needs to be dealt with.
> It's only a minor thing, a question of taste really.
>
> More important is that some dfsg files are still in the git tree.
> MATLAB/{spypart.m,time.m} and DOC/*ug.pdf. (SRC/mc64ad.* has been
> removed)
>
> The dfsg tarball is generated from debian/rules get-orig-source, where
> the files to be removed have been hard-coded. The informal list in
> debian/copyright omits the pdf files. There is the machine-readable
> copyright format,
> https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> Documented not there, but in uscan documentation is the
> Files-Excluded field. If it is present then uscan will use it to
> automatically determine which files to remove. That will simplify the
> get-orig-source rule.
>
> What I do is generate a dfsg tarball and load it into the upstream
> branch. Then it's easy to merge into master, removing the dfsg files
> automatically. gbp (need to argue, with or without the pristine-tar
> flag?) can help with that.
>
> Drew
>
>
