Looks like you are using packages frm a different clam distribution.
You may want to resolve that before attempting to apply our patches.
Erik
On 10/18/06, Lucian Cristian <[EMAIL PROTECTED]> wrote:
Eric "Shubes" wrote:
> Lucian Cristian wrote:
>
>> Eric "Shubes" wrote:
>>
>>> Lucian Cristian wrote:
>>>
>>>
>>>> Eric "Shubes" wrote:
>>>>
>>>>
>>>>> Lucian Cristian wrote:
>>>>>
>>>>>
>>>>>
>>>>>> I tried to do a linked sandbox and I got the following output:
>>>>>>
>>>>>> ..
>>>>>> ..
>>>>>> Starting to build the binary rpms ...(pizza anyone?)
>>>>>>
>>>>>> If you want to view compile messages, you can open another terminal
>>>>>> and:
>>>>>> # tail -f /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>>>>>
>>>>>> qtp-build-rpms v0.1.3
>>>>>> Building spamassassin-toaster-3.1.5-1.3.3 ...
>>>>>> qtp-build-rpms - rpmbuild failed for spamassassin-toaster-3.1.5-1.3.3
>>>>>> qtp-build-rpms - see
>>>>>> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>>>>> Build failed, Exiting.
>>>>>> [EMAIL PROTECTED] qmailtoaster-plus]#
>>>>>> [EMAIL PROTECTED] qmailtoaster-plus]# tail -f
>>>>>> /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
>>>>>> Building spamassassin-toaster-3.1.5-1.3.3 ...
>>>>>> error: Unable to open temp file.
>>>>>> Installing
>>>>>> /usr/src/qtp-upgrade/SRPMS/spamassassin-toaster-3.1.5-1.3.3.src.rpm
>>>>>> Building target platforms: i686
>>>>>> Building for target i686
>>>>>>
>>>>>>
>>>>>> RPM build errors:
>>>>>> Unable to open temp file.
>>>>>>
>>>>>>
>>>>>>
>>>>> I can't recreate this error. In build-recent.log I get:
>>>>> Building spamassassin-toaster-3.1.5-1.3.3 ...
>>>>> Installing
>>>>> /usr/src/qtp-upgrade/SRPMS/spamassassin-toaster-3.1.5-1.3.3.src.rpm
>>>>> Building target platforms: i686
>>>>> Building for target i686
>>>>> Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.13427
>>>>>
>>>>> I'm not sure what temp file you're bombing on. What does
>>>>> # ls -ld /var/tmp
>>>>> # ls -ld /opt/qtp-sandbox/var/tmp
>>>>> show you? I have
>>>>> drwxrwxrwt 2 root root 4096 Oct 15 11:12 /var/tmp
>>>>> and
>>>>> drwxr-xr-x 2 root root 4096 Oct 18 12:33 /opt/qtp-sandbox/var/tmp
>>>>> respectively.
>>>>>
>>>>> Please verify that you are running the current scripts:
>>>>> qtp-build-rpms:myver=v0.1.3
>>>>> qtp-build-sandbox:myver=v0.1.2
>>>>> qtp-newmodel:myver=v0.1.10
>>>>> qtp-whatami:myver=v0.1.1
>>>>>
>>>>> If that all checks out, I'd try running again and letting it
>>>>> recreate the
>>>>> sandbox.
>>>>>
>>>>> Please let me know how you make out.
>>>>>
>>>>>
>>>> I have this output:
>>>> [EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /var/tmp
>>>> lrwxrwxrwx 1 root root 8 Aug 5 23:32 /var/tmp -> /usr/tmp
>>>> [EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /opt/qtp-sandbox/var/tmp
>>>> lrwxrwxrwx 1 root root 8 Oct 18 19:49 /opt/qtp-sandbox/var/tmp ->
>>>> /usr/tmp
>>>>
>>>> the files are
>>>>
>>>> qtp-build-rpms:myver=v0.1.3
>>>> qtp-build-sandbox:myver=v0.1.2
>>>> qtp-newmodel:myver=v0.1.10
>>>> qtp-whatami:myver=v0.1.1
>>>>
>>>>
>>>> I tried 3-4 times using only linked because currently I don't have
>>>> enough space on this machine to make a copy.
>>>>
>>>>
>>>>
>>> That's why I made a linked option. ;)
>>> None the less, the sandbox could use some trimming to get rid of some
>>> of the
>>> bloat.
>>>
>>> Anywise, I notice that your /var/tmp is a symlink to /usr/tmp:
>>> lrwxrwxrwx 1 root root 8 Aug 5 23:32 /var/tmp -> /usr/tmp
>>> and likewise in the sandbox, as the sandbox should be the same.
>>>
>>> What does
>>> # ls -ld /usr/tmp
>>> show you?
>>>
>>> What distro/version are you running? On CentOS4, I have /var/tmp being
>>> the
>>> real directory with a /usr/tmp symlink pointing to it, FWIW.
>>>
>>> I'm just searching here. Something's gotta be somehow different. Show me
>>> # df -h
>>> while we're at it.
>>>
>>>
>>>
>> here they are:
>>
>> [EMAIL PROTECTED] qmailtoaster-plus]# ls -ld /usr/tmp
>> drwxr-xr-x 3 root root 4096 Oct 17 21:52 /usr/tmp
>>
>>
>> [EMAIL PROTECTED] qmailtoaster-plus]# df -h
>> Filesystem Size Used Avail Use% Mounted on
>> /dev/sda2 7.8G 5.0G 2.6G 66% /
>> none 252M 0 252M 0% /dev/shm
>>
>> I have another 2 partitions, but are not mounted because I don't need
>> them for sandbox
>>
>> Indeed I have /var/tmp is a symlink to /usr/tmp.. I'll switch the link
>> (I don't remember how and why I changed them)
>>
>> Distro will be always the latest CentOS.
>>
>> Regards!
>>
>>
> Please let me know your result.
>
>
It seems that is working, but I have to manually remove freshclam file
from logrotate.d
..
qtp-build-rpms v0.1.3
REMOVED spamassassin-toaster from sandbox (not for real)
Building spamassassin-toaster-3.1.5-1.3.3 ...
Installing spamassassin-toaster-3.1.5-1.3.3 in the sandbox ...
Building clamav-toaster-0.88.4-1.3.3 ...
Installing clamav-toaster-0.88.4-1.3.3 in the sandbox ...
qtp-build-rpms - rpm -Uvh failed for clamav-toaster-0.88.4-1.3.3
qtp-build-rpms - see
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
Build failed, Exiting.
[EMAIL PROTECTED] qmailtoaster-plus]#
[EMAIL PROTECTED] qmailtoaster-plus]# tail -f
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
+ exit 0
Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.57783
+ umask 022
+ cd /usr/src/redhat/BUILD
+ rm -rf clamav-0.88.4
+ exit 0
Installing clamav-toaster-0.88.4-1.3.3 in the sandbox ...
Preparing...
##################################################
file /etc/cron.daily/freshclam from install of
clamav-toaster-0.88.4-1.3.3 conflicts with file from package
clamav-db-0.88.1-1.el4.rf
file /etc/logrotate.d/freshclam from install of
clamav-toaster-0.88.4-1.3.3 conflicts with file from package
clamav-db-0.88.1-1.el4.rf
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
