On Mon, 25 May 2015 22:41:05 Russell Sim wrote:
> Dmitry Smirnov writes:
> > Why not add both files to "debian/clean"? That would be the easiest.
>
> Thanks, I was using a rm in the rules file. But the debian/clean method
> is better. I didn't know about the clean files but I find it mentioned
Dmitry Smirnov writes:
> Why not add both files to "debian/clean"? That would be the easiest.
Thanks, I was using a rm in the rules file. But the debian/clean method
is better. I didn't know about the clean files but I find it mentioned
in the dh_auto_clean man page. Doesn't seem to be covere
On Sat, 23 May 2015 22:57:24 Russell Sim wrote:
> Dmitry Smirnov writes:
> > Libgit2 leaves its build directory dirty hence it FTBFS when built again:
> > dpkg-source: info: local changes detected, the modified files are:
> > libgit2-0.22.2/tests/.clarcache
> > libgit2-0.22.2/tests/c
Hi Dmitry,
Dmitry Smirnov writes:
> Libgit2 leaves its build directory dirty hence it FTBFS when built again:
>
> dpkg-source: info: local changes detected, the modified files are:
> libgit2-0.22.2/tests/.clarcache
> libgit2-0.22.2/tests/clar.suite
I've had a look at this and it
Source:libgit2
Version: 0.22.2-1
Severity: normal
Libgit2 leaves its build directory dirty hence it FTBFS when built again:
dpkg-source: info: local changes detected, the modified files are:
libgit2-0.22.2/tests/.clarcache
libgit2-0.22.2/tests/clar.suite
--
Regards,
Dmitry Smi
5 matches
Mail list logo