Ed W wrote: >> For lvm2 this was added without increasing the ebuild revision, but later >> there were some updates of lvm2, so all users of ~arch that are up to >> date should have this. >> > Anyway, yes, installing that newer lvm2 fixed the problems. Probably > worth a note somewhere in the upgrade docs anyway > Definitely IMO, although the blocker would be much simpler.
On a related note, is it ok for a later version of a package to block an earlier incarnation? (You know where I'm going with this, right?) -- [EMAIL PROTECTED] mailing list
