On Monday 18 September 2006 22:36, Andreas Jaeger wrote:

Keith Goggin writes:

...

1. Would it be practical to develop a dummy update that could be applied with YOU and or 'Software Updater'?

For what do you want it?

For Beta testers to test Yast YOU / Software Updater / RUG when no updates are available.

...

2. Can we have the 'Software Updater' correctly identify itself? When the cursor is placed over the Icon it simply says 'There are nn software updates available'

What do you propose as alternative?

For example my Kmail openSUSE-Factory inbox is labeled 'Local Folders/inbox/openSUSE-Factory - KMail' yet 'Software Updater' is just labeled 'Software Updater' and 'Software Updater' 'Configure...' is just labeled 'Configuration'. How about 'openSUSE Online Update - ZENworks' and 'Configuration - ZENworks' at least this might give the user a better idea of they are about to invoke. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Wednesday 20 September 2006 21:50, Martin Vidner wrote:

On út 19. září 2006 08:40, Keith Goggin wrote:

...

On Monday 18 September 2006 22:36, Andreas Jaeger wrote:

...

Keith Goggin writes:

...

1. Would it be practical to develop a dummy update that could be applied with YOU and or 'Software Updater'?

For what do you want it?

For Beta testers to test Yast YOU / Software Updater / RUG when no updates are available.

Yes please, we in the yast team need this too. Too often we had difficulties in testing a change in YOU because there was no data to operate with.

I understand that from the point of the view of the autobuild or maintenance teams this may seem difficult to provide. I have an idea that may make it easier:

For a package foo.rpm, copy (rebuild?) the latest built version to foo-900-1.rpm, foo-990-1.rpm and foo-999-1.rpm. That way we have a high enough version that will be always applicable, plus two spare ones for the same round of testing.

This triple should come for several packages: - a trivial package something that is always installed, but preferably leaf. suse-release? - a package that triggers reboot like the kernel. - a package that triggers packager restart

To test scenarios with packager restart and without it, it seems useful to put these to a special update source, so that the tester can choose whether to include the packager-restarting patch.

If we have trouble doing this with regular packages, I propose to include in the default distro tiny packages that exist solely as candidates for testing updates.

As there has been no further discussion on this can I assume Martin Vidner's proposal is being evaluated? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org