Custom Query (344 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (91 - 93 of 344)

Ticket Resolution Summary Owner Reporter
#298 no change needed CSTRINGIO.PYD cannot be loaded (dlopen rc=123) Lewis Rosenthal
Description

CSTRINGIO.PYD has an illegal OS/2 DLL name (not 8.3). Hence:

  #define ERROR_INVALID_NAME      123     /* MSG%INVALID_NAME */

This keeps yum from being able to run:

  There was a problem importing one of the Python modules 
  required to run yum. The error leading to the problem was:

     dlopen rc=193 extra=C:\USR\LIB\PYTHON2.7\LIB-DYNLOAD\CSTRINGIO.PYD

  Please install a package which provides this module, or 
  verify that the module is installed correctly.

Oddly, this does not seem to affect yum on all processors or arches, however, we have seen this internally at Arca Noae, and we have a ticket open for ANPM.

#308 fixed os2-rpm should install wpi4rpm.exe in %PATH% and create symlinks elsewhere Lewis Rosenthal
Description

Currently (1-2), os2-rpm installs the real wpi4rpm.exe to /@unixroot/usr/lib/rpm/pc and adds a symlink in /@unixroot/usr/lib/rpm. Neither is in %PATH%, limiting the usefulness of this valuable tool.

Suggest installing wpi4rpm.exe to /@unixroot/usr/sbin, and creating symlinks in both of the above places (assuming one is also needed in /@unixroot/usr/lib/rpm/pc).

#321 no change needed os2-rpm 1-3 symlink change renders some packages unable to install Lewis Rosenthal
Description

I just updated the i686 and pentium4 bootstrap zips, and after a test install of an ArcaOS trunk build, I find that libqt4 will not install, complaining that the PREIN scriptlet cannot find /@unixroot/usr/lib/rpm/warpin-conflicts.exe.

These symlinks were apparently changed in os2-rpm 1-3 to not have extensions. Unfortunately, it seems that some packages are still looking for them.

Copying /@unixroot/usr/lib/rpm/warpin-conflicts to /@unixroot/usr/lib/rpm/warpin-conflicts.exe allows the installation of libqt4 to complete successfully.

While the ultimate fix is in the spec files for the affected packages, it may be wise to maintain two symlinks for each of these or create a separate package to install/remove the additional (missing) symlinks.

Note: See TracQuery for help on using queries.