Tobias Frost <[EMAIL PROTECTED]> wrote:

Hi,

> "However as far as I see, the actual issue in #459424 is very different:
> package bar (in this context: libsane-extras) is buggy whether it is in 
> installed state or removed state.
> Package foo (in this context: libsane) is not required to work around bar 
> breakage as long as bar
> is not part of a stable release.  If foo insists to do it, then I think
> the best option is to do it in the preinst script."

I'm not willing to touch a conffile from another package in the
preinst, this would be an option but it's another option that's very
prone to breakage.

I have two ways to avoid the current breakage for people in your
situation:
 - have libsane Depend on libsane-extras (>= 1.0.18.15)
 - change the name of the label in the udev rules in libsane, so as to
   make it unique again

At that time, if I was to do something about it, I'd just add the
dependency to libsane. That's going to pull in libsane-extras for
everybody, which is no big deal. libsane-extras is only a separate
package because it's handy when it needs to be updated, not because
of its size or dependencies.

Option 2 is a partial fix, in that the udev rules in libsane-extras
really have 2 bugs, and option 2 only works around one of them. I'd
rather have them BOTH fixed.

I think I'm going for option 1 later today.

> I'm not reopening, to let you decide how to handle the bug.

As far as libsane-extras is concerned, the bug is fixed. The bug did
not make it to a stable release, as it only appeared after Linux
2.6.22, and that's waaaayyyy after Etch's release :)

JB.

-- 
 Julien BLACHE <[EMAIL PROTECTED]>  |  Debian, because code matters more 
 Debian & GNU/Linux Developer        |       <http://www.debian.org>
 Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to