<div dir="auto"><div>I agree with you, that version string is unnecessary, because it doesn't matter on which version the config file is based on. </div><div dir="auto"><br></div><div dir="auto">It either works with the running libsane version or not.</div><div dir="auto"><br></div><div dir="auto">Second, usually the average user has only one version installed on their system. The ones, who install a separate version, should know what they're doing anyway.</div><div dir="auto"><br></div><div dir="auto">Last, I'm not aware of any incompatibilities between last version, which forces a special version of the config file.</div><div dir="auto"><br></div><div dir="auto">So yes, I vote too on a removing of that version string.</div><div dir="auto"><br></div><div dir="auto">Experienced users can change the standard behaviour of apt on changed config files from "interactive" to smart diff anyway. That way has other drawbacks, because it affects all config files, but again, experienced users should be aware of that.</div><div dir="auto"><br></div><div dir="auto">Kind regards, </div><div dir="auto"><br></div><div dir="auto">Ingo Weigert</div><div dir="auto"><br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">Ulf Zibis <<a href="mailto:Ulf.Zibis@gmx.de">Ulf.Zibis@gmx.de</a>> schrieb am So., 24. Mai 2020, 11:38:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p>Hi Ingo,</p>
<p>it's not an issue for professionals, but for "normal" users.</p>
<p>If the version string is not evaluated by libsane, then it should
be removed to avoid this conflict, which prevents from seamless
update.</p>
<p>-Ulf<br>
</p>
<div>Am 24.05.20 um 02:17 schrieb Jörn-Ingo
Weigert:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div>This is not an issue as the line is a comment anyway and
nothing which is used by sane at all.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Kind regards, </div>
<div dir="auto"><br>
</div>
<div dir="auto">Ingo Weigert<br>
<br>
<div class="gmail_quote" dir="auto">
<div dir="ltr" class="gmail_attr">Ulf Zibis <<a href="mailto:Ulf.Zibis@gmx.de" target="_blank" rel="noreferrer">Ulf.Zibis@gmx.de</a>>
schrieb am So., 24. Mai 2020, 01:40:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p>This would result in the same as clicking "Keep".<br>
Then version "1.0.29" would remain in the config file,
even I have installed 1.0.30 of libsane.</p>
<p>-Ulf<br>
</p>
<div>Am 23.05.20 um 22:00 schrieb Jörn-Ingo Weigert:<br>
</div>
<blockquote type="cite">
<div dir="auto">You can use pinning for your config
files via apt..
<div dir="auto"><br>
</div>
<div dir="auto"><a href="https://wiki.debian.org/AptConfiguration" rel="noreferrer noreferrer" target="_blank">https://wiki.debian.org/AptConfiguration</a><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Ulf Zibis <<a href="mailto:Ulf.Zibis@gmx.de" rel="noreferrer noreferrer" target="_blank">Ulf.Zibis@gmx.de</a>>
schrieb am Sa., 23. Mai 2020, 12:47:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I was prompted for a conflict while Ubuntu did the
regular automatic update, see attachment.<br>
<br>
When I would accept the new config file version,
then my Mustek scanner would no more work.<br>
<br>
It's not a problem, to adjust this manually, but
maybe you have an idea how to prevent from this
conflict.<br>
<br>
Thanks for your work,<br>
-Ulf<br>
<br>
--<br>
Von meinem Seibert gesendet<br>
<br>
<br>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote></div></div></div>