Updating RPM results in failure

[darcio]

Attempting to upgrade the core RPM itself causes a failure with the following error available in the log file:

START===

[ 21 May 2017 08:33:45 ]
Executing: @python G:\UTIL\ANPM\scripts\yum_update.py rpm

Running Transaction Check Error:
[u'ERROR with transaction check vs depsolve:', 'rpm = 4.13.0-10.oc00 is needed by rpm-python-4.13.0-10.oc00.i686',
'rpm.dll is needed by rpm-python-4.13.0-10.oc00.i686',
'rpmbuild.dll is needed by rpm-python-4.13.0-10.oc00.i686',
'rpmio.dll is needed by rpm-python-4.13.0-10.oc00.i686',
u'Please report this error at ​http://trac.netlabs.org/rpm/']
YumRPMCheckError()
Return code: 0

STOP ===

The DLLs are available, a system check confirms:

[G:\]whichdll rpm
The loaded instance of rpm is:
G:\USR\LIB\RPM.DLL

[G:\]whichdll rpmbuild
The loaded instance of rpmbuild is:
G:\USR\LIB\RPMBUILD.DLL

[G:\]whichdll rpmio
The loaded instance of rpmio is:
G:\USR\LIB\RPMIO.DLL

[Silvan Scherrer]

You can't update rpm alone. I bet you have a lot outdated stuff. Rpm python db4 comes to mind. Please update them all

[darcio]

Hmmm, curious, pls see ticket #250 (​http://trac.netlabs.org/rpm/ticket/250).

I just came out of a failure with python.exe, could not upgrade either, had to force install the EXE & DLL and only then would it work. All this apparently due to a exp release of DB4, even though I only do the installs using ANPM and always install all the pre-requisites that are enforced by ANPM/RPM/YUM.

Soo....right now, the only "outdated" stuff that ANPM shows is:
1) info 5.2-2 (oc00) => 5.2-3.oc00 (netlabs-exp)
2) rpm 4.13.0-9 (oc00) => 4.13.0-15 (netlabs-rel)
3) rpm-libs 4.13.0-9 (oc00) => 4.13.0-15 (netlabs-rel)
4) rpm-python 4.13.0-9 (oc00) => 4.13.0-10.oc00 (netlabs-exp)

I would love to fix this, but you need to be a lot more specific regarding what "outdated stuff" you think I actually have. Clearly all my RPM stuff is at the same 4.13.0-9 release level.

Can you provide some ways for me to check this? CLI is fine...

[Silvan Scherrer]

To help you more I need to know what you exactly try to do. As a yum update should work of course.

[darcio]

Replying to diver:

To help you more I need to know what you exactly try to do. As a yum update should work of course.

???

I'm sorry, but I updated the matching LOG entry and spelled out the failure in the ticket description as well. I am simply trying to update the RPM package...once again, the matching LOG entry is:

[ 21 May 2017 08:33:45 ]
Executing: @python G:\UTIL\ANPM\scripts\yum_update.py rpm

What else do you need? What details? please spell them out...you are currently asking some pretty generic questions and that leads me to believe that you do not understand what is the issue I am reporting in this ticket.

[Silvan Scherrer]

I told you to do a yum update. And if you don't know what that is, then you better hunt to ArcaNoae page and ask for help there. We don't support ANPM, as we need the yum output to figure our the failures.
And why yum update: Because sometimes you can't update just one rpm.

[darcio]

Replying to diver:

I told you to do a yum update. And if you don't know what that is, then you better hunt to ArcaNoae page and ask for help there.

Wow man...have you ever actually supported any customers in the past? I can tell you that based on my 20+yrs of IS industry experience that way of talking would get you FIRED on the spot.

So here is the thing, I have asked for specific stuff you want me to check...as in, "Give me the CLI command to run", can you do that? If your previous ticket update stating "...As a yum update should work of course..." is that instruction, that is pretty sad.

Further on, if you can not, since clearly you have not been able to do so this far into this ticket, I absolutely am happy to CLOSE the issue out and share my experience with our OS/2 community and AN so that as many people as possible are aware of the sorry lack of RPM support.

In other words, "Everyone stay the hell away from RPM, because you're gonna get NO HELP from that team".

[dmik]

darcio, your behavior is clearly arrogant. Please take into account that such attitude is not supported by us. So if you want support, please handle this. As my colleague said, you should execute yum update from the command line and provide its output.

[darcio]

Hi dmik,

Replying to dmik:

darcio, your behavior is clearly arrogant.

I think I know who you are in real life, meaning your first & last name, so if I am right I do have a lot of respect for what you have done for our community and respect your input. But please go back, re-read the ticket and understand the concerns I am raising here.

Replying to dmik:

...As my colleague said, you should execute yum update from the command line and provide its output.

Problem is that your colleage NEVER actually said that, despite my multiple request for precise CLI command. diver's attitude seems to reek of that condesending "I know a lot and you don't, so don't bother me with silly questions", in short precisely the sort of behaviour that has caused the vast majority of OS/2 supporters to move on to another platform where "community" actually means something.

I will go back to my professional experience...we never put people with such bad "customer relations" behaviour in the front line, neither should you guys, it gives you a bad name!

Thanks guys...close the ticket, I hope to never again have to deal with the individual known as 'diver'!

[Silvan Scherrer]

I'm closing it on the request of the reporter. And I'm even sure you deal with me more than you think.

And on comment 3 and comment 5 I told you to do a yum update and send me the messages you got.