On Tue, 14 Oct 2008, Will Maier wrote: > Hi Damien- > > On Wed, Oct 15, 2008 at 12:01:02PM +1000, Damien Miller wrote: > > Yes, this is one of the screwups in 2.5 that I fix in the diff. > > Try updating 2.5 with the version in the (slightly misnamed) > > py2.6.diff and then installing 2.6. > > I just ran into this, too. Given that users will likely have old > python2.5 packages installed, shouldn't we add a conflict to the > main python package in the 2.6 PLIST-tools?
This is probably my ignorance of what the @conflict keyword does, but what would that add over the implicit conflict over identically-named files? -d
