Marking as verification done. I had failed verification erroneously and I have re-verified to make sure this is correct.
I had previously failed this due to an install failure for a 3rd party package from VMWare, thinking that the problem was in the control file for this new package in precise. After a bit of testing and education I have learned that the 3rd party package is requiring open-vm-tools and specifying a particular version range. The virtual package in the backport can't satisfy specific version requirements so the 3rd party package must be updated with knowledge of the new open-vm-tools-lts-trus-needed-trusty package. With that resolved and the packages re-verified I have set the tags and distribution/package status so that these can be promoted from -proposed.
Marking as verification done. I had failed verification erroneously and I have re-verified to make sure this is correct.
I had previously failed this due to an install failure for a 3rd party package from VMWare, thinking that the problem was in the control file for this new package in precise. After a bit of testing and education I have learned that the 3rd party package is requiring open-vm-tools and specifying a particular version range. The virtual package in the backport can't satisfy specific version requirements so the 3rd party package must be updated with knowledge of the new open-vm- tools-lts- trus-needed- trusty package. With that resolved and the packages re-verified I have set the tags and distribution/ package status so that these can be promoted from -proposed.