Comment 10 for bug 1047681

1. Passed on my own hardware. I removed my local changes, downgraded to the versions of jockey-common jockey-gtk and nvidia-common currently in precise. Then I enabled -proposed, updated, upgraded the three packages, ran jockey-gtk and verified it works. The experimental driver is displayed correctly in the GUI. I then went ahead and installed it and rebooted, and verified it came up with that driver loaded and unity working normally.

2. Passed on independent verification. I solicited a random nvidia/precise user on #ubuntu-devel (thanks again ion!), had them repeat the above steps (except for the actual driver installation), and verify that the experimental driver was available for them as well.

Thus, verification passed.

The one caveat I should add for completeness is that if the user updates but does not upgrade, then running jockey won't work, because the jockey currently in precise can't cope with there being drivers named "experimental-NNN" in the archive. The fix is of course to do the upgrade, but I am a little worried some users may get caught by this. One way to minimize this might be to roll out the nvidia-common and jockey changes *now*, and hold off a few days on introducing the -experimental-304 packages, but maybe I'm being overcautious?