Update Problem

Gunnar Wrobel wrobel at kolabsys.com
Mon Aug 16 09:27:53 CEST 2010


Zitat von Alexander Schröter <webmaster at computational-chemistry.org>:

> Am Mittwoch, 28. Juli 2010, um 14:13:39 schrieb Alexander Schröter:
>> Hi I think I have a wrong Path somewhere or a Problem with the creation of
>> the TMP directory.
>>
>> /kolab/RPM/TMP/rpm-tmp.75943: line 315: ./configure: No such file or
>> directory + /kolab/bin/make
>> make: *** No targets specified and no makefile found.  Stop.
>> + exit 2
>> + exit 2
>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.75943 (%prep)
>>
>>
>> RPM build errors:
>>     Bad exit status from /kolab/RPM/TMP/rpm-tmp.75943 (%prep)
>> /kolab/RPM/PKG now contains the installed packages.
>> Previous contents were moved to /kolab/RPM/PKG....10764
>>
>> Can somebody help me ... I am kind of lost ... I just downloaded the source
>> files and started the kolab-install.sh to update from 2.2.3 to 2.2.4.
>>
>> Where did I go wrong ?
>
> I just got an email form myself (logcheck) with these lines:
>
> Jul 28 15:26:38 sheldon kernel: [ 5849.651002] gzip[5899]: segfault at 60e440
> ip 000000000060e440 sp 00007fffa89d0ec8 error 15 in gzip[60d000+2000]
> Jul 28 15:26:38 sheldon kernel: [ 5849.762409] gzip[5919]: segfault at 60e440
> ip 000000000060e440 sp 00007fff00047568 error 15 in gzip[60d000+2000]
> Jul 28 15:44:49 sheldon kernel: [ 6925.878556] gzip[10899]: segfault  
> at 60e440
> ip 000000000060e440 sp 00007fffe6d341c8 error 15 in gzip[60d000+2000]
> Jul 28 15:44:49 sheldon kernel: [ 6925.931361] gzip[10919]: segfault  
> at 60e440
> ip 000000000060e440 sp 00007fff8b299758 error 15 in gzip[60d000+2000]
> Jul 28 15:46:52 sheldon kernel: [ 7047.626251] gzip[15757]: segfault  
> at 60e440
> ip 000000000060e440 sp 00007ffffee60358 error 15 in gzip[60d000+2000]
> Jul 28 15:46:52 sheldon kernel: [ 7047.717161] gzip[15777]: segfault  
> at 60e440
> ip 000000000060e440 sp 00007fff803106d8 error 15 in gzip[60d000+2000]
>

Did this mean there was some kind of general problem with the server?  
Did you manage to respolve the build problem in the mean time (I was  
on vacation so this response is coming somewhat late)? Is the problem  
reproducible?

Cheers,

Gunnar

> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.




More information about the users mailing list