http://bugzilla.suse.com/show_bug.cgi?id=1074242
http://bugzilla.suse.com/show_bug.cgi?id=1074242#c3
--- Comment #3 from Johannes Meixner ---
I did read but it seems you do not understand,
perhaps because I did not explain it (see below).
It seems you do not understand how free software development
versus fee software distribution works and therefore
it seems you have wrong expectations what we (at openSUSE)
can do to fix your particular issue in this particular case.
Explanation:
Because we (at openSUSE) do not develop sane-backends,
we cannot bildly "just revert" a SANE upstream commit
because we do not understand what other consequences
at whatever other places such a change may have.
"Just reverting" a SANE upstream commit can make things
work for your particular case but on the other hand
there is a reason why SANE upstream did that commit
(but I do not understand what the commit message means).
If you want a change of the SANE upstream code
you must get in direct contact with SANE upstream
and work together with the SANE upstream authors
to get your particular case fixed at SANE upstream.
This is the only way how issues can get solved properly.
It cannot work well when each Linux distribution maintains
its own distribution-specific different set of patches.
Only when issues get solved at the upstream projects
things will "just work" for all Linux distributions.
In this case the SANE upstream authors need to get
a better understanding of this issue to find a solution
for their intent behind why they did that commit but
without the bad consequences of the current implementation.
Simply put:
Continue to be helpful and continue to contribute to the
SANE upstream bug report to get this issue solved properly
for you and for all users of those scanner models.
--
You are receiving this mail because:
You are on the CC list for the bug.
