[sane-devel] config conflict on Ubuntu update

[Ulf Zibis]

Hi Ingo,

it's not an issue for professionals, but for "normal" users.

If the version string is not evaluated by libsane, then it should be removed to avoid this conflict, which prevents from seamless update.

-Ulf

Am 24.05.20 um 02:17 schrieb Jörn-Ingo Weigert:
> This is not an issue as the line is a comment anyway and nothing which is used by sane at all.
>
> Kind regards,
>
> Ingo Weigert
>
> Ulf Zibis <Ulf.Zibis at gmx.de <mailto:Ulf.Zibis at gmx.de>> schrieb am So., 24. Mai 2020, 01:40:
>
>     This would result in the same as clicking "Keep".
>     Then version "1.0.29" would remain in the config file, even I have installed 1.0.30 of libsane.
>
>     -Ulf
>
>     Am 23.05.20 um 22:00 schrieb Jörn-Ingo Weigert:
>>     You can use pinning for your config files via apt..
>>
>>     https://wiki.debian.org/AptConfiguration
>>
>>     Ulf Zibis <Ulf.Zibis at gmx.de <mailto:Ulf.Zibis at gmx.de>> schrieb am Sa., 23. Mai 2020, 12:47:
>>
>>         Hi,
>>
>>         I was prompted for a conflict while Ubuntu did the regular automatic update, see attachment.
>>
>>         When I would accept the new config file version, then my Mustek scanner would no more work.
>>
>>         It's not a problem, to adjust this manually, but maybe you have an idea how to prevent from this conflict.
>>
>>         Thanks for your work,
>>         -Ulf
>>
>>         --
>>         Von meinem Seibert gesendet
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20200524/e7e5152a/attachment.html>