Re: major versions greater than 1 are not allowed for packages without an <extends> tag or an identical postfix (foo2 v2.0.)

Markus Tacker wrote: > Hoi, > > I just got this error while pushing a package from 1.1.0 to 2.0.0b: > >> major versions greater than 1 are not allowed for packages without an <extends> tag >> or an identical postfix (foo2 v2.0.0) > > I could not find any documentation related to this error. > > Any hints? Hi Markus, When you move from a stable version to a new one that has an API change, this breaks BC. This is not allowed in PEAR. Instead, you should release as File_BitTorrent2 version 2.0.0b1 Pending review, I have removed the release 2.0.0b1 of File_BitTorrent. It may turn out that you may re-release this version if indeed there are no changes in API. However, if you're using PEAR_Exception instead of PEAR_Error, this is by definition a BC break, as scripts written to use File_BitTorrent 1.x would cease to work properly with File_BitTorrent 2.x. If I am right about this BC break, simply create a new package File_BitTorrent2 and the PEAR Group will (most likely) approve it and then you can create a new CVS module (File_BitTorrent2) and copy over the stuff you've done for File_BitTorrent. It's a bit of work, unfortunately, but you'll also want to revert the PHP5-only changes to File_BitTorrent by reverting to the state at version 1.1.0. I'm CCing pear-qa, please reply to that list. Thanks, Greg