Am Freitag, 17. März 2006 18:14 schrieb Andreas Jaeger:

Marcel Hilzinger <mhilzinger@linuxnewmedia.de> writes:

...

Can anybody explain me in 2-3 sentences, howto setup the new replacement for Suse watcher? Or point me to the right documentation?

www.opensuse.org/libzypp -> examples

So, with zen-updater (which should be configured out of the box correctly - and that's a bug already), go to configure and add e.g. factory as YUM repository,

I'm waiting for a preconfigured online updater since beta1. It still doesn't work! There is no documentation, howto add a YaST repo nighter. Do you expect everybody, who want's to have security fixes, to download the 70 MB yum-repodata??? What about setting up a small repository with one or two fake online updates, so we can test the zen-* stuff before it's called stable? Still waiting for the _cool_ features, which make zen-* so good for users of Suse Linux. -- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG Süskindstr. 4 D-81929 München Tel: +49 (89) 99 34 11 0 Fax: +49 (89) 99 34 11 99

On Friday 17 March 2006 18:14, Andreas Jaeger wrote:

So, with zen-updater (which should be configured out of the box correctly - and that's a bug already), go to configure and add e.g. factory as YUM repository,

When adding installation sources in the yast module are they supposed to be added automatically with Zen and Rug also? Or do you have to add them to all three frontends seperately? And by the way, let me say that I'm very positive about 10.1 again, after briefly testing beta8 - for the first time I see real progress with the package manager, though I've already encountered a couple of bugs that I'll be reporting if no one beats me to it. Even though things are looking a lot better perhaps it's a bit optimistic that one more development release will be sufficiant - but we'll see, for now I'm thrilled that b8 is near usable ;) cb400f

Tobias Burnus <burnus@net-b.de> writes:

Hello,

...

On Friday 17 March 2006 18:14, Andreas Jaeger wrote:

...

So, with zen-updater (which should be configured out of the box correctly - and that's a bug already), go to configure and add e.g. factory as YUM repository,

Could someone tell me, why ZMD needs >950 MB of memory when one simply adds factory to the service?

Parsing a 70 MB xml file with libxml2 :-(. I created a blocker bug for that already.

I have now 1 GB of memory (before 1/2 GB), which I deem still as plenty, but if ZMD needs frequently ~1GB, I better buy a dual-core laptop with

...

2 GB RAM :-( Does someone know how much memory/CPU time the daemon needs? If it often needs lots of memory/CPU then I better disable it on our calculation cluster - they should do other calculations than those ...

Either disable - or change the defaults so that it runs less often. 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

Tobias Burnus <burnus@net-b.de> writes:

Hello,

Tobias Burnus schrieb:

...

...

On Friday 17 March 2006 18:14, Andreas Jaeger wrote:

...

So, with zen-updater (which should be configured out of the box correctly - and that's a bug already), go to configure and add e.g. factory as YUM repository,

Next question: If one calls rug update, does it make sense that rug first downloads all files and then installs them? /var/cache/zmd/web/ is then > 1 GB and I do not have extensively much space on /.

And what could have cause the following?

Download failed: (http://ftp4.gwdg.de/efont-unicode-0.4.2-12.noarch.rpm) Sharing violation on path /var/cache/zmd/web/files/ftp4.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/suse/noarch/efont-unicode-0.4.2-12.noarch.rpm Download failed: Download failed: Program aborts, restarting (rug update) seems to re-download the already downloaded files in /var/cache/zmd/ again - and it fails at the same file :-(

Ok, found the reason: df -h / shows 12 M of available diskspace :-(

Please file a bugreport that zmd does not handle low file space correctly.

Actually, zmd could also clean up removed service directories ("rug sd"). I had an old ftp.gwdg.de and download.opensuse.org there, which contained O(58MB) of XML.gz files.

* * *

Great. In order to get some space, I did install the kernel packages manually. The result is:

2:kernel-source ########################################### [ 67%] Changing symlink /usr/src/linux from linux-2.6.16-rc5-git9-3 to linux-2.6.16-rc6-git1-2 Changing symlink /usr/src/linux-obj from linux-2.6.16-rc5-git9-3-obj to linux-2.6.16-rc6-git1-2-obj warning: waiting to reestablish exclusive database lock 3:tpctl-kmp-default ########################################### [100%] warning: waiting to reestablish exclusive database lock

I think ZMD should wait a bit longer to give the pre-/post-inst scripts to do their duty first.

Tobias

PS: I think I have to fill some bug reports ...

so do I - thanks, 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

On Mon, 20 Mar 2006, Juan Erbes wrote:

...

...

3:tpctl-kmp-default ########################################### [100%] warning: waiting to reestablish exclusive database lock

I think ZMD should wait a bit longer to give the pre-/post-inst scripts to do their duty first.

When I use smart to upgrade the system, I got the same errors when the zmd daemon are active ( "warning: waiting to reestablish exclusive database lock" and the excesive memory usage, about 1,3 GB of virtual memory). When I kill the zmd daemon, smart works fine.

That's a known feature / bug ;)

You will continue to support smart?

Of course. Regards Christoph

Martin Schlander <suse@linuxin.dk> writes:

On Friday 17 March 2006 18:14, Andreas Jaeger wrote:

...

So, with zen-updater (which should be configured out of the box correctly - and that's a bug already), go to configure and add e.g. factory as YUM repository,

When adding installation sources in the yast module are they supposed to be added automatically with Zen and Rug also? Or do you have to add them to all three frontends seperately?

Zen and rug share everything, both are frontends to zmd, so adding something to zen-*, you see it with rug as well. The yast installation-source module is currently enhanced so that everything added there is seen by rug/zen as well, the other way might not work :-(

And by the way, let me say that I'm very positive about 10.1 again, after briefly testing beta8 - for the first time I see real progress with the package manager, though I've already encountered a couple of bugs that I'll be reporting if no one beats me to it.

Thanks .

Even though things are looking a lot better perhaps it's a bit optimistic that one more development release will be sufficiant - but we'll see, for now I'm thrilled that b8 is near usable ;)

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

On Tue, 28 Mar 2006, Simon Crute wrote:

On Friday 17 March 2006 20:13, Andreas Jaeger wrote:

...

The yast installation-source module is currently enhanced so that everything added there is seen by rug/zen as well, the other way might not work :-(

Hummm.

I don't see that on a default install. When you do a network install, your network installation source isn't there in the rug service list. Are you saying it should be?

I've tried removing and adding back in the network installation source, and that isn't added into rug as a service either.

I have nfs installed machines (beta8) and there is no update source in zen-updater. 1. Is beta 8 supposed to have a update source configured after install? 2. How do I add a update source, esp. which directory dio i have to specify - the /pub/suse as before? Regards, Andreas -- Andreas Vetter

On Tuesday 28 March 2006 12:24, Simon Crute wrote:

On Friday 17 March 2006 20:13, Andreas Jaeger wrote:

...

The yast installation-source module is currently enhanced so that everything added there is seen by rug/zen as well, the other way might not work :-(

I don't see that on a default install. When you do a network install, your network installation source isn't there in the rug service list. Are you saying it should be? I've tried removing and adding back in the network installation source, and that isn't added into rug as a service either.

This doesn't work for me either - adding factory and extra to yast installation sources didn't make them appear as rug services. Using the directory.yast-URLs. I then tried adding the yum-URLs to YaST installation sources module (same URLs + /suse). This way the installation sources didn't work with neither YaST nor rug. YaST never gave an error message - but no packages were available - except the ones al ready installed - and it started *really* fast ;) Should this be bugreported? Sorry for asking - but I'm a bit uncomfortable reporting bugs for things when I don't have the faintest idea how they're supposed to work. This is all on beta8 - haven't updated from factory since beta8 cd install. cb400f

Simon Crute <scrute@novell.com> writes:

On Friday 17 March 2006 20:13, Andreas Jaeger wrote:

...

The yast installation-source module is currently enhanced so that everything added there is seen by rug/zen as well, the other way might not work :-(

Hummm.

I don't see that on a default install. When you do a network install, your network installation source isn't there in the rug service list. Are you saying it should be?

It should be there, I see first progress now. You won't see it in beta8.

I've tried removing and adding back in the network installation source, and that isn't added into rug as a service either.

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

On Mon, Mar 20, 2006 at 11:26:46PM +0100, Hans-Peter Jansen wrote:

Am Freitag, 17. März 2006 18:05 schrieb Marcel Hilzinger:

...

Can anybody explain me in 2-3 sentences, howto setup the new replacement for Suse watcher? Or point me to the right documentation?

See

While at it, could some kind soul explain me, what the mono folks from ximian consume during work while producing all those *.exe and *.dll files?

Is that just a (plain stupid IMHO) convention, or does producing c# programs with mono mean, we already infected by the win* bork virus.

Lean back and just think that it would be exactly like "/usr/sbin/foo.pl" in the process list. .exe is just a file extension. The programs are written with UNIX in mind, especially zmd and zen-updater Ciao, Marcus

On Tue, Mar 21, 2006 at 07:57:18AM +0100, Marcus Meissner wrote:

Lean back and just think that it would be exactly like "/usr/sbin/foo.pl" in the process list.

.exe is just a file extension.

And it is still a bad idea. Look what other people think what you should do with an .exe file: http://groups.google.com/group/alt.os.linux.suse/browse_frm/thread/9ca4f987a... or http://tinyurl.com/pdx3r Wether right or wrong, people associate .exe with Windows (or dos) programs. If it is just an .exe extention, why not remove the extention alltogether or use something that is common practice under Linux? Using exe is willingly going against common practice, no matter how correct it is technically. It is confusing, to say the least and continued use shows no respect for the user. It looks as if it is a case of 'I can do it, so I do it'. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

Hans-Peter Jansen escribió:

Am Freitag, 17. März 2006 18:05 schrieb Marcel Hilzinger:

...

Can anybody explain me in 2-3 sentences, howto setup the new replacement for Suse watcher? Or point me to the right documentation?

While at it, could some kind soul explain me, what the mono folks from ximian consume during work while producing all those *.exe and *.dll files?

Is that just a (plain stupid IMHO) convention, or does producing c# programs with mono mean, we already infected by the win* bork virus.

Pete

.exe processes appearing in ps output will surely scare some people to death (or to another distro)..

Although ,I Agree with your rant, and found this sudden move to MONO (.NET) or whatever very bad,disappointing, and unnecessary (specially in the middle of the distro development, and having previous, well tested,mature software,that works.) I think you are missing the real point, it doesn't matter if the file extension is pl or exe or whatever, the most important thing is **how it works**.

On Tuesday 21 March 2006 20:57, houghi wrote:

On Tue, Mar 21, 2006 at 10:29:19PM -0400, Cristian Rodriguez wrote:

...

Although ,I Agree with your rant, and found this sudden move to MONO (.NET) or whatever very bad,disappointing, and unnecessary (specially in the middle of the distro development, and having previous, well tested,mature software,that works.) I think you are missing the real point, it doesn't matter if the file extension is pl or exe or whatever, the most important thing is **how it works**.

That is naturaly the first important thing. The second is some kind of logic and calling things *.exe points to a Microsoft enviroment, no matter how wrong that is.

Can someone please explain how it makes sense to use a framework intended for writing code that runs on multiple operating systems (Mono) to write tools used specifically on Linux, and on a specific distro at that? I'm a die-hard Java programmer, but I would never consider writing a SUSE package updater in Java... -- ====================================================== Glenn Holmer (Linux registered user #16682) ====================================================== "Greater coherence cannot be achieved. Not even the Netherlanders have managed this." -Anton Webern ======================================================

On Wed, Mar 22, 2006 at 06:15:45AM -0600, Glenn Holmer wrote:

Can someone please explain how it makes sense to use a framework intended for writing code that runs on multiple operating systems (Mono) to write tools used specifically on Linux, and on a specific distro at that? I'm a die-hard Java programmer, but I would never consider writing a SUSE package updater in Java...

Well, the software does _exist_ implemented in that framework. I wouldn't have chosen that framework neither when it had been my decision in the first place. But now it is implemented in that framework and porting it to any other language/framework would require extra work. And btw. just the fact that the framework is available on multiple platforms does not necessarily disqualify it when implementing an application that is intended to run on one platform only. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."