I'm guessing you are hitting a new bug, specifically Bug# 1038018, and I
only believe so because I've been poking at it the past two evenings for
many hours in order to find the best way to fix it.

First, any reason you are not trying 9.0 SP3 rather than SP2? SP2 had a
few not-so-fun bugs necessitating the hotfixes you may have seen out
there, and SP3 is better, though it has the same issue, if you're seeing
what I think you are.

In summary, directories like /opt/novell and /etc/opt/novell may already
be owned by another package, for example novell-zenworks-ruby (ZCM Agent
for Linux). If so, then the novell-NDSbase package chokes and says, "Oh
no, already owned by something else" and stops the install. If you do
have these directories already, you can see what owns them (if not others)
with the following command:

rpm -qf /opt/novell
rpm -qf /etc/opt/novell

If you want to find out which directories are conflicting, you can run the
following BEFORE you do the install shown after that:

rpm -ivh --test --nodeps novell-NDSbase-9.0.2-0.x86_64.rpm

Please share the output as I'm curious what other packages may interfere
with eDirectory's install. If not zenworks something-or-another, please
share the permissions and ownership of the relevant files/directory as
shown below, but with whatever paths are applicable to you:

ls -ld /opt/novell

I know I am asking for a lot, and I hope you can provide the output from
the stuff above as it may help verify this big is squashed once and for all.

The fix is easy: install eDirctory before whatever else. Alternatively,
you can modify nds-install so that it moves past this particular error.
make a backup of nds-install if you want and then modify line 3559 in it
so that the following:

if ! rpm -Uvh --nodeps  $NOSCRIPTS --dbpath $NDSHOME/var/lib/rpm
$rpmforce $1 >> $log_file 2>

I'm guessing you are hitting a new bug, specifically Bug# 1038018, and I
only believe so because I've been poking at it the past two evenings for
many hours in order to find the best way to fix it.

First, any reason you are not trying 9.0 SP3 rather than SP2? SP2 had a
few not-so-fun bugs necessitating the hotfixes you may have seen out
there, and SP3 is better, though it has the same issue, if you're seeing
what I think you are.

In summary, directories like /opt/novell and /etc/opt/novell may already
be owned by another package, for example novell-zenworks-ruby (ZCM Agent
for Linux). If so, then the novell-NDSbase package chokes and says, "Oh
no, already owned by something else" and stops the install. If you do
have these directories already, you can see what owns them (if not others)
with the following command:

rpm -qf /opt/novell
rpm -qf /etc/opt/novell

If you want to find out which directories are conflicting, you can run the
following BEFORE you do the install shown after that:

rpm -ivh --test --nodeps novell-NDSbase-9.0.2-0.x86_64.rpm

Please share the output as I'm curious what other packages may interfere
with eDirectory's install. If not zenworks something-or-another, please
share the permissions and ownership of the relevant files/directory as
shown below, but with whatever paths are applicable to you:

ls -ld /opt/novell

I know I am asking for a lot, and I hope you can provide the output from
the stuff above as it may help verify this big is squashed once and for all.

The fix is easy: install eDirctory before whatever else. Alternatively,
you can modify nds-install so that it moves past this particular error.
make a backup of nds-install if you want and then modify line 3559 in it
so that the following:

if ! rpm -Uvh --nodeps  $NOSCRIPTS --dbpath $NDSHOME/var/lib/rpm
$rpmforce $1 >> $log_file 2>

On 5/10/2017 14:12, ab wrote:
> I'm guessing you are hitting a new bug, specifically Bug# 1038018, and I
> only believe so because I've been poking at it the past two evenings for
> many hours in order to find the best way to fix it.
>
> First, any reason you are not trying 9.0 SP3 rather than SP2? SP2 had a
> few not-so-fun bugs necessitating the hotfixes you may have seen out
> there, and SP3 is better, though it has the same issue, if you're seeing
> what I think you are.
>
I missed seeing that release. I'll switch to 9.03.


> In summary, directories like /opt/novell and /etc/opt/novell may already
> be owned by another package, for example novell-zenworks-ruby (ZCM Agent
> for Linux). If so, then the novell-NDSbase package chokes and says, "Oh
> no, already owned by something else" and stops the install. If you do
> have these directories already, you can see what owns them (if not others)
> with the following command:

> rpm -qf /opt/novell
"file /opt/novell is not owned by any package".

> rpm -qf /etc/opt/novell
"error: file /etc/opt/novell: no such file or directory".

> If you want to find out which directories are conflicting, you can run the
> following BEFORE you do the install shown after that:
>
>

> rpm -ivh --test --nodeps novell-NDSbase-9.0.2-0.x86_64.rpm
> 

>

Bingo!
"file /opt/novell/eDirectory/lib64 from install of
novell-NDSbase-9.0.3-0.x86_64 conflicts with file from package
novell-NOVLjvmlx-4.5.0-0.x86_64
file /opt/novell/eDirectory/lib64 from install of
novell-NDSbase-9.0.3-0.x86_64 conflicts with file from package
novell-DXMLbasex-4.5.0-0.x86_64
file /opt/novell/eDirectory/lib64 from install of
novell-NDSbase-9.0.3-0.x86_64 conflicts with file from package
novell-DXMLengnx-4.5.0-0.x86_64"

Apparently there was an attempt to install IDM 4.5 on this system too.

Instead of the workaround you detailed below, could/should I simply
uninstall the conflicting RPMs (or every RPM that begins with "novell")
and start over?



Thanks









> Please share the output as I'm curious what other packages may interfere
> with eDirectory's install. If not zenworks something-or-another, please
> share the permissions and ownership of the relevant files/directory as
> shown below, but with whatever paths are applicable to you:
>
>

> ls -ld /opt/novell
> 

>
> I know I am asking for a lot, and I hope you can provide the output from
> the stuff above as it may help verify this big is squashed once and for all.
>
> The fix is easy: install eDirctory before whatever else. Alternatively,
> you can modify nds-install so that it moves past this particular error.
> make a backup of nds-install if you want and then modify line 3559 in it
> so that the following:
>
>

>     if ! rpm -Uvh --nodeps  $NOSCRIPTS --dbpath $NDSHOME/var/lib/rpm
> $rpmforce $1 >> $log_file 2>