On Fri, 19 Aug 2005, Wouter Coekaerts wrote: > > On Thu, Aug 18, 2005 at 05:25:38PM -0400, Paul Kuliniewicz wrote: > > > Hmm. I purged the packages, deleted the cached .debs, and > > > re-installed, and now everything looks to be as it should be. I'm not > > > sure what had happened there. I think I had version -2 of the .deb and > > > then upgraded it to -5, but I don't remember for sure. > > > > > > Everything seems to be working now, so I guess you can close this bug. > > > > doing as requested. ;) > > No, this bug isn't fixed at all! There's just a workaround, which is > uninstalling and reinstalling the package. But (as far as I know) everyone > who follows unstable close enough and has this package and didn't apply > this workaround, still has the broken situation. > It would be nice if a next version would repair that situation somehow...
that's why it is called unstable. > I don't know anything about how symlinks are supposed to be handled > in .debs, but as long as nobody can point out what was done wrong in the > packaging of linux-headers-2.6.12-1, this could just as well concidered a > bug in dpkg, as it looks like it handled this upgrade wrong. > > Wouter. whatever, feel free to reopen. sorry i do not care, please drop me of cc. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
