Custom Query (325 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (46 - 48 of 325)

Ticket Resolution Summary Owner Reporter
#31 fixed yum reports WarpIn database locked/in-use when it is not Yuri Dario Lewis Rosenthal
Description

Case:

Odin 0.6.21632.0 (20110512-release) was installed under WarpIn?. Uninstalled, breaking Flash dependency. Restarted. Ran "yum install libodin" from prompt, and received:

ERROR:

Failed to access the WarpIn? database file:

C:\ECS\INSTALL\WARPIN\DATBAS_C.INI

Please close the WarpIn? application or, if it is not running, make sure that this file is not locked by another process, and try again.

This is not the only package to exhibit this behavior, thus, I do not think this is a packaging issue. I confirmed that the database was not in use, and was able to open it under UniMaint? (and closed it before re-trying yum).

I have had success with several other packages, though I am not sure what triggers the perceived lock on the database.

As "yum version" currently yields:

Error: Error accessing file for config file:///etc/yum/version-groups.conf

I can't get version info from there, however, dir reports:

8-28-11 10:58 1,330 124 yum.exe

#32 invalid LIBC PANIC!! when installing clamav Yuri Dario Andib
Description

Maybe someone have a clue about the problem I encountered while installing clamav.i386 (yum install clamav.i386)

....
Führe Verarbeitungstest durch
Verarbeitungstest erfolgreich
Führe Verarbeitung durch
  Aktualisieren  : libc-0.6.4-11.oc00.i386                                  1/7
  Aktualisieren  : libc-devel-0.6.4-11.oc00.i386                            2/7
  Installieren   : clamav-data-0.97.2-5.oc00.i386                           3/7
warning: user %username does not exist - using root
warning: group %username does not exist - using root
warning: user %username does not exist - using root
warning: group %username does not exist - using root
  Installieren   : clamav-lib-0.97.2-5.oc00.i386                            4/7
P:\var\cache\rpm\wps\objects.90606.tmp -> P:\var\cache\rpm\wps\objects
     1 file renamed
P:\var\cache\rpm\wps\packages\clamav-lib.48706.tmp -> P:\var\cache\rpm\wps\packag
es\clamav-lib
     1 file renamed
  Installieren   : clamav-0.97.2-5.oc00.i386                                5/7
P:\var\cache\rpm\wps\objects.00656.tmp -> P:\var\cache\rpm\wps\objects
     1 file renamed
P:\var\cache\rpm\wps\packages\clamav.65181.tmp -> P:\var\cache\rpm\wps\packages\c
lamav
     1 file renamed
  Aufräumen      : libc-0.6.3-7.oc00.i386                                   6/7
  Aufräumen      : libc-devel-0.6.3-7.oc00.i386                             7/7
clamav-data-0.97.2-5.oc00.i386 was supposed to be installed but is not!
libc-devel-0.6.4-11.oc00.i386 was supposed to be installed but is not!
libc-0.6.4-11.oc00.i386 was supposed to be installed but is not!
clamav-lib-0.97.2-5.oc00.i386 was supposed to be installed but is not!
clamav-0.97.2-5.oc00.i386 was supposed to be installed but is not!

LIBC PANIC!!
_um_free_maybe_lock: Tried to free block twice - block=013ac688 lock=0x1
pid=0x007b ppid=0x007a tid=0x0001 slot=0x00b8 pri=0x0200 mc=0x0000
P:\USR\BIN\PYTHON.EXE
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

ClamAV 0.97.2 object was created at desktop which holds a RedMe?.txt reference only. Not sure if there should be more. clamscan works

#33 worksforme Installation fails when TMP is on ram disk Yuri Dario cinc
Description

Using bootstrap V1.3 installation fails when temp dir is located on a ram drive provided by RAMFS107.IFS.

The error message is:

[...]
Installieren      52 Paket(e)
Upgrade       0 Paket(e)

Gesamtgrösse: 27 M
Installed size: 72 M
Ist dies in Ordnung? [j/N] :j
Lade Pakete herunter:
Führe rpm_check_debug durch
Führe Verarbeitungstest durch


[Errno 13] Permission denied: 'r:/temp/tmpo9q8rm'

[L:\]

Note that the bootstrap files are on drive L:\tmp\yumbt despite the tempdir settings in config.sys.

Config.sys:

REM ****** TEMP on RAM-Disk *********
IFS=E:\system\ramfs107\ramfs.ifs /Q /S:150M
call=l:\os2\cmd.exe /C md R:\temp
SET TEMP=R:/temp
SET TMP=R:\temp
SET TMPDIR=R:/temp
Note: See TracQuery for help on using queries.