Custom Query (326 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (16 - 18 of 326)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Ticket Resolution Summary Owner Reporter
#26 fixed GNU info/man build required to read documentation Yuri Dario ak120
Description

The language and locale should be setup in CONFIG.SYS. SET LOCALEDIR=UNIXROOT:\usr\share\locale SET LANGUAGE=[de|...] Currently TERM=os2 - so GNU info is not capable to display anything. Additionally for man pages MANPATH should refer to /usr/share/man and PAGER to "more" as long no other program is installed

And please only install man pages or info pages documentation stuff, if appropriate tool for viewing them is installed before.

#27 fixed warpin-conflicts should use wic -p Yuri Dario dmik
Description

WIC, starting from version 1.0.16, supports the -p parameter that returns the version number for the given package. See the WarpIn? programmer's documentation for more info.

It is much better to use this parameter than parsing the WarpIn? INI database files manually from Rexx when detecting conflicts. The former is known to suffer from strange bugs (e.g. inability to access the INI file with SysIni?).

#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

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Note: See TracQuery for help on using queries.