[opensuse-factory] second-libzypp-update-test

Hi, at http://ftp.suse.com/pub/people/aj/second-libzypp-update-test/ there are currently some RPMs which look like they might become a YOU soon. I don't remember any announcement, but installed them anyway ;) What I noticed afterwards is that "yast2 inst_suse_register" now more or less *requires* rug and zmd to be installed. The registration still "works" without them, but YaST complains with popup error messages about not being able to synchronize with ZenWorks. It didn't do that before, and actually I think that it's a regression because at least on Non-Enterprise products, YaST was not intended to *depend* on rug and zmd. Before reporting this as a bug, I'd like to know if it's intentional. Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org

On Tue, Jul 04, 2006 at 10:35:12AM +0200, Andreas Hanke wrote:
Hi,
at http://ftp.suse.com/pub/people/aj/second-libzypp-update-test/ there are currently some RPMs which look like they might become a YOU soon. I don't remember any announcement, but installed them anyway ;)
What I noticed afterwards is that "yast2 inst_suse_register" now more or less *requires* rug and zmd to be installed. The registration still "works" without them, but YaST complains with popup error messages about not being able to synchronize with ZenWorks.
It didn't do that before, and actually I think that it's a regression because at least on Non-Enterprise products, YaST was not intended to *depend* on rug and zmd. Before reporting this as a bug, I'd like to know if it's intentional.
It did do it with the first update already. Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org

On Tue, Jul 04, 2006 at 10:36:02AM +0200, Marcus Meissner wrote:
On Tue, Jul 04, 2006 at 10:35:12AM +0200, Andreas Hanke wrote:
Hi,
at http://ftp.suse.com/pub/people/aj/second-libzypp-update-test/ there are currently some RPMs which look like they might become a YOU soon. I don't remember any announcement, but installed them anyway ;)
What I noticed afterwards is that "yast2 inst_suse_register" now more or less *requires* rug and zmd to be installed. The registration still "works" without them, but YaST complains with popup error messages about not being able to synchronize with ZenWorks.
It didn't do that before, and actually I think that it's a regression because at least on Non-Enterprise products, YaST was not intended to *depend* on rug and zmd. Before reporting this as a bug, I'd like to know if it's intentional.
It did do it with the first update already.
Oh and it requires mono-core, but not rug or zmd directly. rpm -qRp suseRegister.rpm curl perl-XML-Parser perl-XML-Writer perl-URI mono-core coreutils sysconfig hwinfo libzypp-zmd-backend rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 /usr/bin/perl rpmlib(PayloadIsBzip2) <= 3.0.5-1 The requirement is due to a "GUID" generation snippet, a microscopic C# program only. :( Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org

Hi, Marcus Meissner schrieb:
Oh and it requires mono-core, but not rug or zmd directly.
The term "requires" was not meant as in RPM "Requires:" tags, but as in "not working or misbehaving without rug and zmd". Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org

On Tue, Jul 04, 2006 at 10:48:04AM +0200, Andreas Hanke wrote:
Hi,
Marcus Meissner schrieb:
Oh and it requires mono-core, but not rug or zmd directly.
The term "requires" was not meant as in RPM "Requires:" tags, but as in "not working or misbehaving without rug and zmd".
Hmm. It should not misbehave. Please open a bugreport. :) Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org

Hi, Marcus Meissner schrieb:
Hmm. It should not misbehave. Please open a bugreport. :)
OK, I've made a #191135 and found #191133 while doing that. The problem is: I don't know if it's actually a misbehaviour. The new suseRegister from the second update stack now has: Recommends: rug Recommends: zmd so one could argue that this is by design. But on the other hand it's not really a soft requirement if YaST shows ugly popups without rug and zmd: If it's intended to be a soft dependency, it should just fail silently IMHO instead of presenting error messages. Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org

Hi, Marcus Meissner schrieb:
Oh and it requires mono-core, but not rug or zmd directly.
[...]
The requirement is due to a "GUID" generation snippet, a microscopic C# program only. :(
This (known as #183842 and #183656) seems to be already resolved in Factory: http://lists.opensuse.org/archive/opensuse-commit/2006-Jul/0115.html Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org

Hi, Marcus Meissner schrieb:
It did do it with the first update already.
Really? This is very strange because it doesn't seem to be the case for me on a system with just the first libzypp update installed (yast2-installation = 2.13.119-1.2). Are you sure? Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org

Andreas Hanke <andreas.hanke@gmx-topmail.de> writes:
Hi,
at http://ftp.suse.com/pub/people/aj/second-libzypp-update-test/ there are currently some RPMs which look like they might become a YOU soon. I don't remember any announcement, but installed them anyway ;)
I will move them to the old place once I'm happy with them - those are the packages from last week. We found already that you cannot install them with zen-updater - and therefore currently investigate this, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

Tirsdag 04 juli 2006 10:45 skrev Andreas Jaeger:
I will move them to the old place once I'm happy with them - those are the packages from last week.
I'm testing the packages dated July 7th. Seems to work nicely. I believe performance would be the focal point of these patches, correct? Only tested on my 900 mhz/512 mb ram laptop thus far - but it still seems rather slow - at resolving, installing, running suseconfig etc. - slower than 10.0-yast and a lot slower than Smart. Though there seems to pe significant improvement in the parse-metadata department - only tested it briefly thus far. I'm wondering how much more potential is there for improvement? Is this considered satisfactory? How much work will be put into it after this round of updates is put out? Is this the level of performance we can expect, say, when 10.2 rolls around? One of the reasons I'm asking is that it was communicated earlier that the packagemanagement issues would be fixed in two rounds of patching. Martin / cb400f --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org

Hi, Martin Schlander schrieb:
Only tested on my 900 mhz/512 mb ram laptop thus far - but it still seems rather slow - at resolving, installing, running suseconfig etc. - slower than 10.0-yast and a lot slower than Smart.
smart doesn't run SuSEconfig at all.
One of the reasons I'm asking is that it was communicated earlier that the packagemanagement issues would be fixed in two rounds of patching.
I guess that there might be even more than two rounds. Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org

On Tue, Jul 11, 2006 at 01:10:41PM +0200, Martin Schlander wrote:
Tirsdag 04 juli 2006 10:45 skrev Andreas Jaeger:
I will move them to the old place once I'm happy with them - those are the packages from last week.
I'm testing the packages dated July 7th. Seems to work nicely.
I believe performance would be the focal point of these patches, correct?
No, we fixed mostly stability issues.
Only tested on my 900 mhz/512 mb ram laptop thus far - but it still seems rather slow - at resolving, installing, running suseconfig etc. - slower than 10.0-yast and a lot slower than Smart. Though there seems to pe significant improvement in the parse-metadata department - only tested it briefly thus far.
I'm wondering how much more potential is there for improvement? Is this considered satisfactory? How much work will be put into it after this round of updates is put out? Is this the level of performance we can expect, say, when 10.2 rolls around?
I hope more performance than we have now.
One of the reasons I'm asking is that it was communicated earlier that the packagemanagement issues would be fixed in two rounds of patching.
In several rounds, not just two. ;) The next (third) round hopefully will reintroduce handling of patch and delta RPMs. ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org

Martin Schlander <suse@linuxin.dk> writes:
Tirsdag 04 juli 2006 10:45 skrev Andreas Jaeger:
I will move them to the old place once I'm happy with them - those are the packages from last week.
I'm testing the packages dated July 7th. Seems to work nicely.
I believe performance would be the focal point of these patches, correct?
No - correctness. We're still fixing bugs :-(
Only tested on my 900 mhz/512 mb ram laptop thus far - but it still seems rather slow - at resolving, installing, running suseconfig etc. - slower than 10.0-yast and a lot slower than Smart. Though there seems to pe significant improvement in the parse-metadata department - only tested it briefly thus far.
I'm wondering how much more potential is there for improvement? Is this considered satisfactory? How much work will be put into it after this round of updates is put out? Is this the level of performance we can expect, say, when 10.2 rolls around?
We continue working on performance and that needs some major refactoring, so it will need extensive testing.
One of the reasons I'm asking is that it was communicated earlier that the packagemanagement issues would be fixed in two rounds of patching.
It will be more I fear :-( Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

Tirsdag 11 juli 2006 13:40 skrev Andreas Jaeger:
No - correctness. We're still fixing bugs :-(
We continue working on performance and that needs some major refactoring, so it will need extensive testing.
It will be more I fear :-(
Well, what's with the sad smileys? That was just what I wanted to hear! But of course it means a lot of work still left for you guys. :) It gets a better each time - I'm actually starting to believe it'll end up being really good and nice. Must admit I've had doubts before... Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org

Martin Schlander <suse@linuxin.dk> writes:
Tirsdag 11 juli 2006 13:40 skrev Andreas Jaeger:
No - correctness. We're still fixing bugs :-(
We continue working on performance and that needs some major refactoring, so it will need extensive testing.
It will be more I fear :-(
Well, what's with the sad smileys? That was just what I wanted to hear!
It means that we are not confident that we fixed all bugs in the code ;)
But of course it means a lot of work still left for you guys. :)
Exactly.
It gets a better each time - I'm actually starting to believe it'll end up being really good and nice. Must admit I've had doubts before...
Thanks for believing in us, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

* Martin Schlander <suse@linuxin.dk> [Jul 11. 2006 13:11]:
Tirsdag 04 juli 2006 10:45 skrev Andreas Jaeger:
I will move them to the old place once I'm happy with them - those are the packages from last week.
I'm testing the packages dated July 7th. Seems to work nicely.
Good to hear, thanks for testing !
I believe performance would be the focal point of these patches, correct?
Its certainly one of the goals.
I'm wondering how much more potential is there for improvement?
Lots.
Is this considered satisfactory? No, not at all. However, its currently not clear how much we can change on the architecture side of zmd/zypp. We might end up with a 'pure' zypp frontend (aka y2pmsh-zypp) for testing/timing purposes.
How much work will be put into it after this round of updates is put out? Is this the level of performance we can expect, say, when 10.2 rolls around?
Zypp developers are working on further improvements which you will see on the factory (resp. 10.2) releases in the coming weeks. But I can't say how much of it can/will be released for 10.1
One of the reasons I'm asking is that it was communicated earlier that the packagemanagement issues would be fixed in two rounds of patching.
If the time between the two rounds is sufficiently large ... Klaus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org
participants (5)
-
Andreas Hanke
-
Andreas Jaeger
-
Klaus Kaempf
-
Marcus Meissner
-
Martin Schlander