<html>
<head>
<meta content="text/html; charset=iso-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hello All,</p>
<p>My Ubuntu ppa (<a
href="https://launchpad.net/%7Erolfbensch/+archive/ubuntu/sane-git"><span
class="ppa-reference">ppa:rolfbensch/sane-git</span></a>) is
working again. It distributes pre-built packages for all supported
Ubuntu distributions (amd64, i386 and armhf architectures).</p>
<p>I changed the package names to fit the packages version
convention a little bit more. I hope that this helps to change the
package names provided from Ubuntu.<br>
</p>
<p>If you are already using my ppa, you must use the "Force Version"
function of your package manager once to get the updates.</p>
<p>Please report if you may have any problems.</p>
<p>Hope this helps.</p>
<p>Cheers,<br>
Rolf<br>
</p>
<br>
<div class="moz-cite-prefix">Am 07.05.2017 um 13:15 schrieb Rolf
Bensch:<br>
</div>
<blockquote
cite="mid:a8ce65c7-27a9-83f7-38de-2393eb8c9c8b@bensch-online.de"
type="cite">
<pre wrap="">Hi,
@Olaf: Thanks for your patch. It's working with the ppa.
Please have a look at the attached patches. Maybe there are additional
fixes for SANE (fix_avahi_error_paths.patch) or there are needful
additional options for configure possible or just keep them inside the ppa?
Many thanks for your help.
Cheers,
Rolf
Am 06.05.2017 um 14:00 schrieb Olaf Meeuwissen:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Rolf,
Rolf Bensch writes:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Olaf,
I tried to build a recent version for zesty some weeks ago with my test
ppa: <a class="moz-txt-link-freetext" href="https://launchpad.net/%7Erolfbensch/+archive/ubuntu/sane-test/+packages">https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-test/+packages</a> .
</pre>
</blockquote>
<pre wrap="">Thanks for the link! Now I can see the build failures.
BTW, it looks like the build does not apply the debian/patches/. Don't
know if that's intentional or not.
</pre>
<blockquote type="cite">
<pre wrap="">I'll try to investigate this issue next week. If you can provide a patch
before, I can merge it into the build system very quickly.
</pre>
</blockquote>
<pre wrap="">See the attached.
- debian/rules: modified a few configure flags and added one for the
API spec (BTW, 6ffeb909 fixed a brain fart for that option)
- debian/control: add transfig as a build dependency for the spec (BTW,
we do PDF now too but that requires pdflatex and gs as well)
- debian/patches/multiarch_dll_searc_path.patch: adjust to upstream
changes
Note that this only aims to fix the xenial build but the other builds
should be mostly identical if not exactly.
I've checked
debian/rules binary
dpkg-buildpackage -b
and both complete without a hitch, on xenial (in a Docker container).
Hope this helps,
--
Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27
GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9
Support Free Software <a class="moz-txt-link-freetext" href="https://my.fsf.org/donate">https://my.fsf.org/donate</a>
Join the Free Software Foundation <a class="moz-txt-link-freetext" href="https://my.fsf.org/join">https://my.fsf.org/join</a>
</pre>
</blockquote>
</blockquote>
<br>
</body>
</html>