On Sat, Mar 26, 2005 at 11:25:42AM +0100, Michael Schmitz wrote:
> It's not about a dangling alternatives link - that you could detect, and
> rightly refuse to overwrite it ('the system administrator sure knows what
> he's doing'). I don't understand why, in the absence of any link, the
> alternati
> Correct me if I am wrong: the problem is caused by a dangling link in
> the alternatives system that refers to an uninstalled package. dpkg
Nope - even after removing that dangling link, bison does not properly
install a new link.
> knows that byacc is not installed, so in principle update-alt
On Thu, Mar 24, 2005 at 09:14:11AM +0100, Michael Schmitz wrote:
> > > 2. If you think that bison should work even under this specific
> > > breakage (after all the byacc link is obviously stale), you need
> > > to fix dpkg instead of bison.
> I strongly doubt it's dpkg's fault. After all, hand
> > 2. If you think that bison should work even under this specific
> > breakage (after all the byacc link is obviously stale), you need to
> > fix dpkg instead of bison.
I strongly doubt it's dpkg's fault. After all, handling compatibility
problems of that sort is supposed to happen in p
severity 301075 normal
thanks
On Wed, Mar 23, 2005 at 10:53:03AM -0800, Chuan-kai Lin wrote:
> On Wed, Mar 23, 2005 at 06:41:09PM +0100, Michael Schmitz wrote:
> > > I think I ran into this a few months back. It had to do with
> > > alternatives -- very odd.
> > Odd indeed. I found a stale yacc al
On Wed, Mar 23, 2005 at 06:41:09PM +0100, Michael Schmitz wrote:
> > I think I ran into this a few months back. It had to do with
> > alternatives -- very odd.
> Odd indeed. I found a stale yacc alternatives file for bison (byacc) on
> kullervo, that might have prevented proper alternatives install
6 matches
Mail list logo
