Am 01.09.2006 um 08:20 schrieb Chuan-kai Lin:
On Fri, Aug 25, 2006 at 08:47:22PM +0200, Sven Joachim wrote:
Probably even better would be to just create the missing symlink
yourself, with
[ -e /usr/bin/yacc ] || ln -s /etc/alternatives/yacc /usr/bin
instead of
[ -e /usr/bin/yacc ] || update-alternatives --auto yacc
manual alternatives don't get destroyed on upgrade from 2.3.dfsg-1.
I think we still need to switch the yacc alternative to auto because of
the nature of the breakage in 2.3.dfsg-1.
If the system contains a working, auto yacc alternative when you install
2.3.dfsg-1, the alternatives system will notice that the /usr/bin/yacc
symlink is stomped on and switch the yacc alternative to manual.
Aaah, I overlooked that. So we cannot tell whether the user has set
the alternative to manual on purpose or whether it was an accident.
Manually creating the missing symlink fixes the problem for now, but
unless someone switches the yacc alternative back to auto, the
alternatives system will leave the yacc alternative alone and result in
further breakage (for example, a dangling /usr/bin/yacc symlink after
all yacc alternatives had been removed).
Yes, update-alternatives does not play nice in this case. Switching
to auto is the least of the evils, it seems.
Regards,
Sven
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
