On Thu, Sep 12, 2002 at 08:17:44PM +0200, Wolfgang Pfeiffer wrote: > Dominik, > Thanks for your fast answer: > > On Sep 12, 2002, 19:24 (+0200) Dominik Vogt wrote: > > > On Thu, Sep 12, 2002 at 07:01:50PM +0200, Wolfgang Pfeiffer wrote: > > > Dominik Vogt wrote: > > > > > > > The DeferExecution() function is trashing memory. I ran into the > > > > same problem yesterday and have hopefully fixed it in current CVS. > > > > (But be aware that fvwm will probably crash anyway.) > > > > > > ... I didn't find any explanations on how to use CVS when searching > > > on: > > > ftp://ftp.fvwm.org/pub/fvwm/devel/sources/ > > > > Look on our web site: http://fvwm.org/cvs.html > > I'll have a look at it .. > > > > > > But is the fix for the problem already built into > > > ftp://ftp.fvwm.org/pub/fvwm/devel/snapshots/fvwm-snap-20020912.tar.gz > > > ?? > > I just tried to build an RPM/SRC.RPM from this snapshot (I have, as, > IIRC, previously told in this thread, RedHat 6.2 here): it didn't > work: > > ########################## > error: Bad exit status from /var/tmp/rpm-tmp.79583 (%build) > > > RPM build errors: > Bad exit status from /var/tmp/rpm-tmp.79583 (%build) > ########################### > > > > > I'm not sure, but the fix will be in the next snapshot. > > let's hope it builds RPM's here :) > > > > > > Or are there so many more instabilities (additional to the ones that > > > are already in 2.5.3) that it doesn't make much sense to install a > > > snapshot? > > > > It makes sense to try it out, but not to use it on your system. > > Ummmh, you probably mean: not trying it in a production environment > or so, right? I mean, I have just one machine here, so I'll install it > on this one or nowhere ... :)
Actually I wanted to say: expect trouble and be prepared to downgrade to a more stable release. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
