[opensuse-factory] openSUSE 12.1 update stack testing
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? 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
On 26.10.2011 13:21, 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.
The same happens with zypper patch IIRC
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.
It looks like a bug in the update-test packages to me. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 26 October 2011 13:24:26 Stefan Seyfried wrote:
On 26.10.2011 13:21, 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.
The same happens with zypper patch IIRC
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.
It looks like a bug in the update-test packages to me.
Comparing the update-test updateinfo.xml with the live data for eg 11.1 the reboot_suggested and restart_suggested tags are missing from the relevant packages in 12.1's metadata. Therefore I assume any update stack testing done for 12.1 is invalid. Anyone with a clue want to confirm this for me? Will -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 26 October 2011, Will Stephenson wrote:
Comparing the update-test updateinfo.xml with the live data for eg 11.1 the reboot_suggested and restart_suggested tags are missing from the relevant packages in 12.1's metadata. Therefore I assume any update stack testing done for 12.1 is invalid. Anyone with a clue want to confirm this for me?
Yes, the current ones are broken. We're working on the opensuse buildservice based system, but that one is also currently not finished, so it'll take a bit more. Thanks, Dirk -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Oct 26, 2011 at 01:58:14PM +0200, Dirk Müller wrote:
On Wednesday 26 October 2011, Will Stephenson wrote:
Comparing the update-test updateinfo.xml with the live data for eg 11.1 the reboot_suggested and restart_suggested tags are missing from the relevant packages in 12.1's metadata. Therefore I assume any update stack testing done for 12.1 is invalid. Anyone with a clue want to confirm this for me?
Yes, the current ones are broken. We're working on the opensuse buildservice based system, but that one is also currently not finished, so it'll take a bit more.
WIll, you could juse use the 11.4 updates for testing, probably needs a 11.4 base? Otherwise Dirk needs to fix it first. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 26 Oct 2011 14:03:03 Marcus Meissner wrote:
On Wed, Oct 26, 2011 at 01:58:14PM +0200, Dirk Müller wrote:
On Wednesday 26 October 2011, Will Stephenson wrote:
Comparing the update-test updateinfo.xml with the live data for eg 11.1 the reboot_suggested and restart_suggested tags are missing from the relevant packages in 12.1's metadata. Therefore I assume any update stack testing done for 12.1 is invalid. Anyone with a clue want to confirm this for me?> Yes, the current ones are broken. We're working on the opensuse buildservice based system, but that one is also currently not finished, so it'll take a bit more.
WIll, you could juse use the 11.4 updates for testing, probably needs a 11.4 base?
Otherwise Dirk needs to fix it first.
It's hardly 'test what you fly, and fly what you test' is it? I can only show that Apper has no regressions vs KPackageKit on 11.4 update stack, when we know that the components are notoriously tightly coupled. I'll do this in a VM now, but would it be possible to generate update-test metadata using the old system for now? We have 2 days to RC2 and irrespective of KDE only issues, the rest of the stack needs testing or we risk shipping a release that can't be fixed later.</statingtheobvious> Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Mittwoch, 26. Oktober 2011 schrieb Will Stephenson:
On Wednesday 26 Oct 2011 14:03:03 Marcus Meissner wrote:
On Wed, Oct 26, 2011 at 01:58:14PM +0200, Dirk Müller wrote:
On Wednesday 26 October 2011, Will Stephenson wrote:
Comparing the update-test updateinfo.xml with the live data for eg 11.1 the reboot_suggested and restart_suggested tags are missing from the relevant packages in 12.1's metadata. Therefore I assume any update stack testing done for 12.1 is invalid. Anyone with a clue want to confirm this for me?>
Yes, the current ones are broken. We're working on the opensuse buildservice based system, but that one is also currently not finished, so it'll take a bit more.
WIll, you could juse use the 11.4 updates for testing, probably needs a 11.4 base?
Otherwise Dirk needs to fix it first.
It's hardly 'test what you fly, and fly what you test' is it? I can only show that Apper has no regressions vs KPackageKit on 11.4 update stack, when we know that the components are notoriously tightly coupled. I'll do this in a VM now, but would it be possible to generate update-test metadata using the old system for now? We have 2 days to RC2 and irrespective of KDE only issues, the rest of the stack needs testing or we risk shipping a release that can't be fixed later.</statingtheobvious>
Rudi fixed /update/12.1 Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Stephan Kulow wrote:
Am Mittwoch, 26. Oktober 2011 schrieb Will Stephenson: [...]
It's hardly 'test what you fly, and fly what you test' is it? I can only show that Apper has no regressions vs KPackageKit on 11.4 update stack, when we know that the components are notoriously tightly coupled. I'll do this in a VM now, but would it be possible to generate update-test metadata using the old system for now? We have 2 days to RC2 and irrespective of KDE only issues, the rest of the stack needs testing or we risk shipping a release that can't be fixed later.</statingtheobvious>
Rudi fixed /update/12.1
Would it be possible to release all checkins since RC1 as patches for testing purposes? What would be required to make that happen? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Mittwoch, 26. Oktober 2011 schrieb Ludwig Nussel:
Stephan Kulow wrote:
Am Mittwoch, 26. Oktober 2011 schrieb Will Stephenson: [...]
It's hardly 'test what you fly, and fly what you test' is it? I can only show that Apper has no regressions vs KPackageKit on 11.4 update stack, when we know that the components are notoriously tightly coupled. I'll do this in a VM now, but would it be possible to generate update-test metadata using the old system for now? We have 2 days to RC2 and irrespective of KDE only issues, the rest of the stack needs testing or we risk shipping a release that can't be fixed later.</statingtheobvious>
Rudi fixed /update/12.1
Would it be possible to release all checkins since RC1 as patches for testing purposes? What would be required to make that happen?
Talk to Dirk and Benjamin - they are working on setting up the new maintenance project. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 26 Oct 2011 15:27:17 Stephan Kulow wrote:
Am Mittwoch, 26. Oktober 2011 schrieb Will Stephenson:
On Wednesday 26 Oct 2011 14:03:03 Marcus Meissner wrote:
On Wed, Oct 26, 2011 at 01:58:14PM +0200, Dirk Müller wrote:
On Wednesday 26 October 2011, Will Stephenson wrote:
Comparing the update-test updateinfo.xml with the live data for eg 11.1 the reboot_suggested and restart_suggested tags are missing from the relevant packages in 12.1's metadata. Therefore I assume any update stack testing done for 12.1 is invalid. Anyone with a clue want to confirm this for me?>
Yes, the current ones are broken. We're working on the opensuse buildservice based system, but that one is also currently not finished, so it'll take a bit more.
WIll, you could juse use the 11.4 updates for testing, probably needs a 11.4 base?
Otherwise Dirk needs to fix it first.
It's hardly 'test what you fly, and fly what you test' is it? I can only show that Apper has no regressions vs KPackageKit on 11.4 update stack, when we know that the components are notoriously tightly coupled. I'll do this in a VM now, but would it be possible to generate update-test metadata using the old system for now? We have 2 days to RC2 and irrespective of KDE only issues, the rest of the stack needs testing or we risk shipping a release that can't be fixed later.</statingtheobvious> Rudi fixed /update/12.1
Good work, Rudi. But the update-test-interactive package is still missing from /update/12.1, could you add it please? Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Mittwoch, 26. Oktober 2011, 16:26:42 schrieb Will Stephenson: [....]
It's hardly 'test what you fly, and fly what you test' is it? I can only show that Apper has no regressions vs KPackageKit on 11.4 update stack, when we know that the components are notoriously tightly coupled. I'll do this in a VM now, but would it be possible to generate update-test metadata using the old system for now? We have 2 days to RC2 and irrespective of KDE only issues, the rest of the stack needs testing or we risk shipping a release that can't be fixed later.</statingtheobvious>
Rudi fixed /update/12.1
Good work, Rudi. But the update-test-interactive package is still missing from /update/12.1, could you add it please?
sorry, can't find any valid example for this yet. The interactive stuff was IMHO never implemented for 11.x (libzypp/satsolver variant). The only ones I can find are reboot_needed and so on, and we already have these.
Will
-- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@suse.com,ro@suse.de,bugfinder@t-online.de) GPG Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 26 October 2011, Dirk Müller wrote:
Yes, the current ones are broken. We're working on the opensuse buildservice based system, but that one is also currently not finished, so it'll take a bit more.
they will be found here: http://download.opensuse.org/repositories/openSUSE:/12.1:/Update/standard/ so please use that as an update channel (it is currently empty). Thanks, Dirk -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
participants (7)
-
Dirk Müller -
Ludwig Nussel -
Marcus Meissner -
Ruediger Oertel -
Stefan Seyfried -
Stephan Kulow -
Will Stephenson