Mailinglist Archive: opensuse-testing (32 mails)

< Previous Next >
Re: [opensuse-testing] creating a better Factory
  • From: "Terje J. Hanssen" <nteknikk@xxxxxxxx>
  • Date: Thu, 18 Nov 2010 22:24:36 +0100
  • Message-id: <4CE59994.6050702@xxxxxxxx>
Den 16. nov. 2010 12:03, skrev Bernhard M. Wiedemann:
Hi

there is this problem, that Factory is sometimes broken
but it would be nice if people had a safer way to test new software even between milestone-releases (which are manual factory-snaphots).

...snip

It is about creating a snapshot of Factory whenever it passes all basic automated tests (aka critical path) - preferably with minimal human intervention (aka hard work) needed.
I have much of the automated testing done, so what is missing is a way to trigger+do the snapshotting.


Do I understand you right that Factory iso sometimes are broken and should undergo a better QA testing on each build before being published?

I.e comparing the current builds for Milestone-3 with Factory, we have

openSUSE-NET-Build0845-x86_64.iso
08-Nov-2010 21:42 161M
http://download.opensuse.org/distribution/11.4-Milestone3/iso/

openSUSE-NET-x86_64-Build0876-Media.iso
18-Nov-2010 17:57 161M
http://download.opensuse.org/factory/iso/


By the way, I've found myself soon on the latest Factory iso, or rather using online update to Factory with 'zypper', even if I started out with the latest Milestone distribution. This to find out if issues are solved before reporting new bugs or to test fixes after reporting bugs.

A question aside, after using 'zypper up' first: Why can thereafter 'zypper dup' suggest to downgrade some packages with the same repositories available? I thought that 'zypper dup' should upgrade at least to the same or newer versions than 'zypper up'.


Terje J. Hanssen



--
To unsubscribe, e-mail: opensuse-testing+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-testing+help@xxxxxxxxxxxx

< Previous Next >