Custom Query (344 matches)

Having just installed hplip to support my new printer - HP Envy Photo 6234 - I notice that it has some of the files required for scanner support but there seem to be some missing. The obvious missing file is hpaio.dll but I suspect there are others missing.

Will hplip be delivering scanner support in the, hopefully, near future?

Having used ANPM to update some files I had error messages about not being able to identify the correct DATBAS_?.INI to use and a new file, DATBAS_D.INI, was created as a result.

I have 3 ArcaOS installations on the same disk, H: L: M:

Warpin can handle this without problems as it uses DATBAS_H.INI when booted from H:, DATBAS_L.INI when booted from L: and DATBAS_M.INI when booted from M:

Here is an ANPM log snippet showing the problem:-

Executing: @python J:\PROGRAMS\UTILS\ANPM\scripts\yum_update_dep.py bc coreutils coreutils-common cube dash fontconfig glib2 gmp klusrmgr less libglib-2_0-0 libgmodule-2_0-0 libgobject-2_0-0 libgthread-2_0-0 libusbcalls rxcrypt sed sqlite tcl unzip zip Return code: 0

Executing: @python J:\PROGRAMS\UTILS\ANPM\scripts\yum_update.py bc coreutils coreutils-common cube dash fontconfig glib2 gmp klusrmgr less libglib-2_0-0 libgmodule-2_0-0 libgobject-2_0-0 libgthread-2_0-0 libusbcalls rxcrypt sed sqlite tcl unzip zip Running Transaction Check Warning: RPMDB altered outside of yum. Found 1 pre-existing rpmdb problem(s), 'yum check' output follows: os2-base-0.0.1-2.oc00.i686 is a duplicate with os2-base-0.0.0-19.oc00.i686 Non-fatal POSTIN scriptlet failure in rpm package klusrmgr-1.4.0-1.oc00.i686 ERROR: wpi4rpm: Warning: 4 WarpIN databases found. Using J:\PROGRAMS\UTILS\WARPIN\DATBAS_D.INI

ERROR: wpi4rpm: Warning: 4 WarpIN databases found. Using J:\PROGRAMS\UTILS\WARPIN\DATBAS_D.INI

ERROR: wpi4rpm: Warning: 4 WarpIN databases found. Using J:\PROGRAMS\UTILS\WARPIN\DATBAS_D.INI

ERROR: wpi4rpm: Warning: 4 WarpIN databases found. Using J:\PROGRAMS\UTILS\WARPIN\DATBAS_D.INI

Surely wpi4rpm should check what boot drive letter is in use and select the DATBAS_?.INI file based on the boot drive letter to avoid the above problem.

Related is that the entries in DATBAS_D.INI cannot be read by Warpin, some sort of header problem, so the DATBAS_D.INI file is of no use to anyone - especially Warpin.

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