On Monday 12 May 2008, Frank Lichtenheld wrote:
> > The correct solution here IMO is _not_ to add the missing executable to
> > the udeb, but to test whether it exists before calling it and just skip
> > it when it does not.
>
> Didn't this in the past call eject from the target medium instead of
> from the udeb?
Yes, that is correct. It was changed by Joey in July last year (see the BR
for details):
cdrom-detect (1.23) unstable; urgency=low
[ Joey Hess ]
* Stop installing eject into target. This will now be handled by
hw-detect version 1.53.
* Use anna to install eject-udeb, and use that eject in the finish-install
script instead of running /target/usr/bin/eject. Closes: #418593
Thanks for fixing the issue and sorry for the delayed reply to your
question.
Cheers,
FJP
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
