Bug#715426: Bug # 715426: Interested in getting this done
On 30 November 2015 at 19:38, Roderick W. Smith <rod.smith@canonical.com> wrote:
> I think I figured out why this failed: I think you were using an
> unmodified 0.10.0 tarball. At the moment, my revisions since that
> release, including the ARM64 support, are in the rEFInd git repository
> on Sourceforge. An attempt to build on ARM64 from 0.10.0 will of
> course fail.
Yeah, that's definitely the issue. :)
> I use a script called mkdistrib (which is in the git repository) to
> create my tarballs, binary files, etc. You should be able to run it
> yourself like this:
>
> ./mkdistrib {version} --nosign
>
> It'll create a directory tree called ../snapshots/{version} and put
> files there. It will almost certainly error out on you sooner or
> later, but not before it's built a source tarball. Alternatively,
> here's my latest snapshot:
>
> http://www.rodsbooks.com/refind-src-0.10.0.7.tar.gz
>
> I've made some changes this evening that should clean up many of the
> lintian issues. That said, when I ran lintian, I got a much shorter
> list than you did. (I tried both from Ubuntu 14.04 and Debian 8.2.)
> What options were you passing to it?
Ah, I'll do a re-sync of debian/, try building a newer upstream
snapshot, and see where that lands us! :D
I use lintian from sid, not from a release, since that's the only way
I know of to make sure I've got the latest updates. In this case, I
run ran "lintian refind_*.changes", not even the usual
"-EvIL+pedantic" I usually like perusing (but which normally has quite
a few more false positives).
> Concerning the errata.js file error, that's part of the Creative
> Commons license files. I just tossed the whole contents of the
> relevant CC Web page into a directory, but I suppose I can replace
> that with plain text or something. I think I saw something about a
> Debian page with a bunch of archived licenses, so maybe I'll look for
> that....
Yeah, if you're willing to remove that file from upstream's source
tarballs entirely, that's definitely our best solution! I think
https://creativecommons.org/licenses/by-sa/3.0/legalcode.txt is a
plain-text version of the HTML currently contained in the source. :)
♥,
- Tianon
4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
Reply to: