On Wednesday 26 October 2011 13:21:55 Will Stephenson wrote:
I'm trying to test Apper, the renamed latest version of KPackageKit on 12.1 and need to clarify how the update tests *should* work.
If I revert all the update-test- packages to their 12.1 vanilla versions, I see update-test-affects-package-manager as the only update.
However, installing this update also pulls in every other update-test- package, immediately. Expected behaviour would be for update-test-package- manager to install, Apper to restart itself, then for it to present the other update-test-packages.
Since update-test-affects-package-manager does not require or recommend any of these packages, I looked at http://download.opensuse.org/12.1/repodata/updateinfo.xml.gz, and this lists all the other packages as belonging to the update with id update-test-affects- package-manager. Is this correct? If so, what is the mechanism that causes u-t-a-p-m to pull in the other u-t packages?
Lacking documentation on the updateinfo.xml schema, I compared the 12.1 test metadata to the current 11.1 updateinfo.xml. There are no <reboot_suggested> or <restart_suggested> tags in the 12.1 data for the relevant packages, so I guess the 12.1 test data is buggy and any update stack testing performed for 12.1 so far is invalid :(. Will -- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org