(Me is very confused with To and Cc right now I've been getting double
of every email so far and I'm sorry if you are going to get a double
of this email as well)
2009/9/12 Jonathan Marsden <email address hidden>:
> Benjamin Drung wrote:
>
>> I get following report from lintian -iIE --pedantic (version 2.2.14,
>> build on jaunty):
>> P: xiphos: copyright-refers-to-symlink-license usr/share/common-licenses/GFDL
>> W: xiphos: binary-or-shlib-defines-rpath ./usr/bin/xiphos /usr/lib
>> W: xiphos: binary-or-shlib-defines-rpath ./usr/bin/xiphos /lib
>> P: xiphos-data: copyright-refers-to-symlink-license usr/share/common-licenses/GFDL
>> P: gnomesword: copyright-refers-to-symlink-license usr/share/common-licenses/GFDL
>>
>> My changes are not huge. The problem is the 2.3 MiB big auto-generated
>> patch. Attached the diff with this patch trimmed down. Then the changes
>> are only 60 lines long.
>
The debian/copyright can certainly go it =) I'll merge as soon as i'll
be back on my main ubuntu box.
As for autoreconf, not so sure about chrpath either. Because I have
longer term solution
> Then, longer term, we can (hopefully) persuade "upstream" to put newer
> autoconf-generated files in their release tarballs.
>
I am one of the "upstreams" now, well I have commit access anyway. So
far I've update configure.ac, all makefiles.am and so far already
dropped image-magick dependency. And after I will convince the lead
developer not to use Fedora 7 to generate tarballs this issue will be
gone. So next upstream release hopefully will be generated with modern
autotools and this issue will be gone fingers-crossed.
>
> Do you know if it is common to have such large patches just to overcome
> lintian warnings like this?
>
As far as I know if you modify configure.ac, makefile.am and etc you
should run all autofoo and use it as a patch cause then you will have
the same configure + Makefile.in's on all architectures. There is high
chance that each architecture and each release has different autotools
and by applying patch is the only option to make reproducible builds.
(Me is very confused with To and Cc right now I've been getting double
of every email so far and I'm sorry if you are going to get a double
of this email as well)
2009/9/12 Jonathan Marsden <email address hidden>: refers- to-symlink- license usr/share/ common- licenses/ GFDL or-shlib- defines- rpath ./usr/bin/xiphos /usr/lib or-shlib- defines- rpath ./usr/bin/xiphos /lib refers- to-symlink- license usr/share/ common- licenses/ GFDL refers- to-symlink- license usr/share/ common- licenses/ GFDL
> Benjamin Drung wrote:
>
>> I get following report from lintian -iIE --pedantic (version 2.2.14,
>> build on jaunty):
>> P: xiphos: copyright-
>> W: xiphos: binary-
>> W: xiphos: binary-
>> P: xiphos-data: copyright-
>> P: gnomesword: copyright-
>>
>> My changes are not huge. The problem is the 2.3 MiB big auto-generated
>> patch. Attached the diff with this patch trimmed down. Then the changes
>> are only 60 lines long.
>
The debian/copyright can certainly go it =) I'll merge as soon as i'll
be back on my main ubuntu box.
As for autoreconf, not so sure about chrpath either. Because I have
longer term solution
> Then, longer term, we can (hopefully) persuade "upstream" to put newer
> autoconf-generated files in their release tarballs.
>
I am one of the "upstreams" now, well I have commit access anyway. So
far I've update configure.ac, all makefiles.am and so far already
dropped image-magick dependency. And after I will convince the lead
developer not to use Fedora 7 to generate tarballs this issue will be
gone. So next upstream release hopefully will be generated with modern
autotools and this issue will be gone fingers-crossed.
>
> Do you know if it is common to have such large patches just to overcome
> lintian warnings like this?
>
As far as I know if you modify configure.ac, makefile.am and etc you
should run all autofoo and use it as a patch cause then you will have
the same configure + Makefile.in's on all architectures. There is high
chance that each architecture and each release has different autotools
and by applying patch is the only option to make reproducible builds.
> Jonathan /code.launchpad .net/~bdrung/ xiphos/ lintian- clean/+ merge/11535
> --
> https:/
> You are requested to review the proposed merge of lp:~bdrung/xiphos/lintian-clean into lp:~pkgcrosswire/xiphos/main.
>
--
With best regards
Dmitrijs Ledkovs (for short Dima),
Ледков Дмитрий Юрьевич