Custom Query (344 matches)

This is not a failure of getbootdrive.exe (as I originally thought). After reading ticket #339 and updating os2-rpm to 1-9, I can still reproduce the failure of the os2-base package to edit the correct CONFIG.SYS.

Example:

C:\CONFIG.SYS exists, but does not have any SHELL= statements in it.

U: is the current boot volume.

Reinstall, downgrade, or update os2-base on U:, and C:\CONFIG.SYS is edited to insert:

SET SHELL=U:/usr/bin/sh.exe SET EMXSHELL=U:/usr/bin/sh.exe SET CONFIG_SHELL=U:/usr/bin/sh.exe SET MAKESHELL=U:/usr/bin/sh.exe SET EXECSHELL=U:/usr/bin/sh.exe

U:\CONFIG.SYS is untouched (if entries are manually removed before reinstall/update, they are not added).

As getbootdrive.exe does return the correct drive, I'm not sure where else the os2_boot_drive or os2_config_sys macros could be failing. While this ticket is opened against os2-base, clearly the problem lies in an rpm macro which can potentially impact a number of other packages.

os2_langdir, os2_bookdir, and os2_helpdir (and possibly more) macros rely on _datadir to provide the first portion of their paths. Unfortunately, _datadir points to:

%{_prefix}/share (i.e., /@unixroot/usr/share)

which is not very useful when attempting to install something in, say, %BOOKSHELF% (X:\OS2\BOOK) using the os2_bookdir macro.

I would suggest that once ticket #340 has been fully vetted, these macros be reviewed for accuracy, so that os2_helpdir, etc. start with os2_boot_drive, instead.

python-dateutil-2.6.0-1.oc00.noarch python-2.7.6-24.oc00.i686

paython-dateutil makes use of six, as per parser.py:

from six import text_type, binary_type, integer_types

Unfortunately, as this cannot be automatically detected during RPM build, this dependency must be listed explicitly, or we end up with a non-working dateutil, and thus, anything which depends upon dateutil (yum-plugin-changelog, for example) fails.