As noted in a previous comment this is caused by an incomplete upgrade. This is normal for a development release where the archive is a state of rapid change. There isn't really anyway of blocking the release until all packages are ready without freezing the repository which is something we only do for alpha/beta milestones.
If you run the development release please wait until you have a complete upgrade before reporting bugs. Unless of course you are getting a bug that prevents you completing the upgrade. If you have a fully upgraded 4.2 and you still find bugs then those are the ones we want to hear about.
As noted in a previous comment this is caused by an incomplete upgrade. This is normal for a development release where the archive is a state of rapid change. There isn't really anyway of blocking the release until all packages are ready without freezing the repository which is something we only do for alpha/beta milestones.
If you run the development release please wait until you have a complete upgrade before reporting bugs. Unless of course you are getting a bug that prevents you completing the upgrade. If you have a fully upgraded 4.2 and you still find bugs then those are the ones we want to hear about.
Thanks