> On Sat, Jul 19, 2008 at 2:25 PM, Nagy Gabor <[EMAIL PROTECTED]> > wrote: > > Hi! > > > > I've tried -Su again... > > I've just run into a very "hard to fix" error. > > > > [EMAIL PROTECTED] ~]$ LANG=C sudo pacman -Su --ignore mplayer > > ... > > xulrunner: /usr/include/xulrunner-1.9 exists in filesystem > > xulrunner: /usr/lib/xulrunner-1.9 exists in filesystem > > xulrunner: /usr/lib/xulrunner-devel-1.9 exists in filesystem > > xulrunner: /usr/share/idl/xulrunner-1.9 exists in filesystem > > ... > > > > These are directories... But in the package we have symlinks. > > > > I thought this was a regression caused by this fix : > http://bugs.archlinux.org/task/8156 > > But apparently this fix made it into pacman 3.1, and 3.1 didn't have > the above problem. > So now I am confused... >
I think this is not a regression, but a behaviour change. What did the "old" pacman do when we have a real symlink<->dir conflict? I mean a conflict which won't disappear after the upgrade_remove part: fileconflict003 should pass. Bye P.S.: I will create a pactest for this case. _______________________________________________ pacman-dev mailing list [email protected] http://archlinux.org/mailman/listinfo/pacman-dev
