Author Topic: Attempted update of RPM leads to DLL conflict and failure...any ideas?  (Read 1197 times)

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1465
  • Karma: +35/-0
    • View Profile
Trying to update my RPM stuff:

Quote
@python2.7 G:\UTIL\ANPM\scripts\yum_update_dep.py rpm rpm-build rpm-build-libs rpm-libs rpm-plugin-syslog
...
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_update.py python2-rpm
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
No argument pipe.
Running Transaction Check
YumRPMCheckError(): [u'ERROR with transaction check vs depsolve:', 'rpm7.dll is needed by (installed) deltarpm-3.6-1.oc00.pentium4', 'rpmio7.dll is needed by (installed) deltarpm-3.6-1.oc00.pentium4', u'Please report this error at http://yum.baseurl.org/report']
Error: ERROR with transaction check vs depsolve:rpm7.dll is needed by (installed) deltarpm-3.6-1.oc00.pentium4rpmio7.dll is needed by (installed) deltarpm-3.6-1.oc00.pentium4Please report this error at http://yum.baseurl.org/report
YumRPMCheckError()
Return code: 0
...

So it looks like rpmio7.dll is the conflicting DLL, which in turn is needed by (installed) deltarpm-3.6-1.oc00.pentium4.

Attempting to uninstall deltarpm-3.6-1.oc00.pentium4 just leads to more dependency conflicts as that is used by other packages.

Has anyone ran into this issue?

Thanks!

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1465
  • Karma: +35/-0
    • View Profile
Re: Attempted update of RPM leads to DLL conflict and failure...any ideas?
« Reply #1 on: February 01, 2026, 09:02:11 pm »
Alright...so a bit of an update, but it seems to be looking bleaker and bleaker.

I worked this thing through all the dependencies and uninstalled the following RPMs:

1) createrepo-0.10.4-3.oc00.noarch
2) python2-deltarpm-3.6-1.oc00.pentium4
3) deltarpm-3.6-1.oc00.pentium4

OK, that seemed to work, attempting to upgrade rpm no longer complained, so through ANPM I ran the following:

'Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_update_dep.py rpm rpm-build rpm-build-libs rpm-libs
rpm-plugin-syslog'

ANPM took a while to churn through all this and eventually tossed back a rather cryptic error which was also verbatim captured in the ANPM.LOG file:

Quote
----------[ 1 Feb 2026 14:13:36 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_update.py python2-rpm
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
No argument pipe.
Running Transaction Check
PackageSackError(): Rpmdb checksum is invalid: dCDPT(pkg checksums): rpm.pentium4 0:4.15.1-4.oc00 - u
Error: Rpmdb checksum is invalid: dCDPT(pkg checksums): rpm.pentium4 0:4.15.1-4.oc00 - u
PackageSackError()
Return code: 0
----------[ 1 Feb 2026 14:14:14 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\YUM_UPDATE.PY rpm
error: /@unixroot/etc/rpm/macros.perl: line 34: Macro %global is a built-in (%define)
error: /@unixroot/etc/rpm/macros.perl: line 35: Macro %global is a built-in (%define)
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
No argument pipe.
Running Transaction Check
Warning: RPMDB altered outside of yum.
Return code: 0
...

In particular it is this
Quote
error: /@unixroot/etc/rpm/macros.perl: line 34: Macro %global is a built-in (%define)
error: /@unixroot/etc/rpm/macros.perl: line 35: Macro %global is a built-in (%define)
that's pointing to some sort of a problem as I am now seeing it all the time and ANPM (along with the back-end rpm) has effectively ceased to work (i.e., ANPM churns away but the window never populates).

ANPM.LOG tells the story:

Quote
----------[ 1 Feb 2026 14:26:32 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_list.py
error: /@unixroot/etc/rpm/macros.perl: line 34: Macro %global is a built-in (%define)
error: /@unixroot/etc/rpm/macros.perl: line 35: Macro %global is a built-in (%define)
Setting up yum
No argument pipe.
Adding temporary repositories
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
Initializing cache
Requesting package list
Return code: 0

Running ANPM with a /DEB option doesn't produce any more obvious indicators:

Quote
...
[RetrieveList] Requesting list for category: (default)
[RunYum] Sending information about 4 secure repositories to yum
...
[RunYum] Starting execution thread for command: yum_list.py
[RunYum]   -> Thread 8 started successfully.
[SW_PROGRESS_Fini] Closing progress dialog
[PyDone] Thread for "yum_list.py" completed with status 0.
[PyDone] Processing exit logic for "YUM_LIST.PY".
[PyDone] Processing list result  - 2816 lines.
[PyDone] Initializing INSTALLED package list.
[GetScalingFactor] Using font size 10 (scaling factor 1)
[PyDone] Installed packages: 0
[PyDone] Available packages:
...

I would say either RPM or YUM is failing in all of this, or perhaps it is PERL that's actually a problem given that the errors seems to reference the "/@unixroot/etc/rpm/macros.perl: line 34: Macro %global" script?

Anyone have any ideas where the heck to go with this???

Yeah, I'm pretty much lost at the moment as all the RPMs were in 'REL' status, as were all the installed RPM packages that were actually being upgraded.

BTW, here is my current mix of RPMs:

RPM
Code: [Select]
rpm.pentium4                              4.15.1-4.oc00
rpm-build.pentium4                        4.15.1-4.oc00
rpm-build-libs.pentium4                   4.15.1-4.oc00
rpm-libs.pentium4                         4.15.1-4.oc00
rpm-plugin-syslog.pentium4                4.15.1-4.oc00
rpm-sign-libs.pentium4                    4.15.1-4.oc00

PYTHON2
Code: [Select]
python2-dateutil.noarch                       1:2.8.1-3.oc00
python2-libxml2.pentium4                      2.9.10-3.oc00
python2-pycurl.pentium4                       7.44.1-3.oc00
python2-rpm.pentium4                          4.15.1-4.oc00
python2-six.noarch                            1.10.0-2.oc00
python2.7.pentium4                            2.7.18-3.oc00

PERL - I do NOT have the latest release, that being: 4:5.16.1-11.oc00
Code: [Select]
perl.pentium4                              4:5.16.1-9.oc00
perl-Carp.noarch                           1.26-9.oc00
perl-Error.noarch                          1:0.17024-1
perl-Filter.pentium4                       1.40-9.oc00
perl-Git.noarch                            2.11.0-4.oc00
perl-Module-Pluggable.noarch               1:4.00-9.oc00
perl-PathTools.pentium4                    3.39.2-9.oc00
perl-Pod-Escapes.noarch                    1:1.04-9.oc00
perl-Pod-Parser.noarch                     1.51-9.oc00
perl-Pod-Perldoc.noarch                    3.17.00-9.oc00
perl-Pod-Simple.noarch                     1:3.20-9.oc00
perl-Scalar-List-Utils.pentium4            3:1.49-2.oc00
perl-Socket.pentium4                       2.001-9.oc00
perl-libs.pentium4                         4:5.16.1-9.oc00
perl-macros.pentium4                       4:5.16.1-9.oc00
perl-parent.noarch                         1:0.225-9.oc00
perl-threads.pentium4                      1.86-9.oc00
perl-threads-shared.pentium4               1.40-9.oc00

EDIT - updated the deleted packages to the full package name and listed the current CONFIG I have
« Last Edit: February 01, 2026, 11:27:57 pm by Dariusz Piatkowski »

TeLLie

  • Sr. Member
  • ****
  • Posts: 291
  • Karma: +21/-0
    • View Profile
Re: Attempted update of RPM leads to DLL conflict and failure...any ideas?
« Reply #2 on: February 02, 2026, 08:14:44 am »
Hi

Why not open a ticket?
As I don't think it will be resolved here.
Its allways better to open a ticket.
As then the maintainer reads it, and he can answered you.

Greetz Tellie

Roderick Klein

  • Hero Member
  • *****
  • Posts: 774
  • Karma: +17/-0
    • View Profile
Re: Attempted update of RPM leads to DLL conflict and failure...any ideas?
« Reply #3 on: February 02, 2026, 09:09:13 am »
Hi

Why not open a ticket?
As I don't think it will be resolved here.
Its allways better to open a ticket.
As then the maintainer reads it, and he can answered you.

Greetz Tellie

1000% agreed with Tellie. Developers complain they get no feedback and in genereal users complain about the quality of the sofftware.
So please open a ticket.

Roderick

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 5631
  • Karma: +50/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: Attempted update of RPM leads to DLL conflict and failure...any ideas?
« Reply #4 on: February 02, 2026, 05:44:52 pm »
FYI:

The RPM Tickets should be open here: https://github.com/bitwiseworks/rpm-issues

Just as a note, usually users post their issues on users forum to see if other user share the same issue. Once the issue it is confirmed the procedure it is to open a ticket or contact the developer. 

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1465
  • Karma: +35/-0
    • View Profile
Re: Attempted update of RPM leads to DLL conflict and failure...any ideas?
« Reply #5 on: February 12, 2026, 02:48:03 pm »
Martin!

...Just as a note, usually users post their issues on users forum to see if other user share the same issue. Once the issue it is confirmed the procedure it is to open a ticket or contact the developer...

Thank you for pointing this out, as that was precisely my thinking.

Look, it is not as if we have an army of developers and/or RPM maintainers waiting to pounce on every single issue that is being reported, at least not AFAIK anyways...so posting stuff here first is the least I can do to troubleshoot before I engage the "pros".

Having said that, I think I have pretty much arrived at that point, see https://github.com/bitwiseworks/rpm-issues/issues/45

Will update my post here per the feedback and issue resolution on github.

Thanks everyone!