OS/2, eCS & ArcaOS - Technical > Applications
ANPM - libc upgrade error...?
Dariusz Piatkowski:
Hi Alex,
--- Quote from: Alex Taylor on May 06, 2023, 11:58:11 pm ---A bug in the conflict dialog initialization. I'll fix it...
--- End quote ---
Happy to test, just let me know...
--- Quote from: Alex Taylor on May 06, 2023, 11:58:11 pm ---...However, that won't fix your underlying problem, which is that yum is reporting a package dependency conflict. You can try looking examining the end of %LOGFILES%\anpm.log, which records the raw output from yum.
--- End quote ---
Well, that's the weird part, ANPM.LOG is the first place I went, but that only shows:
--- Code: ---...
----------[ 6 May 2023 10:24:03 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_update_dep.py libc
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
No argument pipe.
Return code: 0
--- End code ---
Nothing here looks unusual compared to all the other successful updates before...weird, no?
I haven't tried the CLI update yet, although it does appear to correctly recognize that the matching libc update is out there:
--- Code: ---[G:\]yum list libc
Loaded plugins: changelog, downloadonly, ps, replace, verify
Installed Packages
libc.pentium4 1:0.1.9-1.oc00 installed
Available Packages
libc.i686 1:0.1.9-1.oc00 netlabs-rel
libc.pentium4 1:0.1.10-1.oc00 netlabs-rel
--- End code ---
I figured it would be best to investigate through ANPM first.
Dave Yeo:
I have,
--- Code: ---H:\tmp>yum list libc
Installed Packages
libc.pentium4 1:0.1.10-1.oc00 installed
Available Packages
libc.i686 1:0.1.9-1.oc00 netlabs-rel
--- End code ---
I installed from netlabs-exp, wonder if I also updated Python or such first and so avoided the error.
You might have to open an issue at Bitwise's Github.
Dariusz Piatkowski:
Alright, so for what its worth, I ran a CLI update, here is the output:
--- Code: -----> Running transaction check
---> Package libc.pentium4 1:0.1.9-1.oc00 will be updated
--> Processing Dependency: libc = 1:0.1.9-1.oc00 for package: 1:libc-devel-0.1.9-1.oc00.pentium4
---> Package libc.pentium4 1:0.1.10-1.oc00 will be an update
--> Running transaction check
---> Package libc-devel.pentium4 1:0.1.9-1.oc00 will be updated
---> Package libc-devel.pentium4 1:0.1.10-1.oc00 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Updating:
libc pentium4 1:0.1.10-1.oc00 netlabs-rel 1.0 M
Updating for dependencies:
libc-devel pentium4 1:0.1.10-1.oc00 netlabs-rel 3.1 M
Transaction Summary
================================================================================
Upgrade 2 Packages
Total download size: 4.1 M
Is this ok [y/N]: y
Downloading Packages:
(1/2): libc-0.1.10-1 | 1.0 MB 00:00 ] 462 kB/s | 388 kB 00:01 ETA
(2/2): libc-devel-0. | 3.1 MB 00:01 ===- ] 1.3 MB/s | 2.8 MB 00:00 ETA
--------------------------------------------------------------------------------
Total 1.6 MB/s | 4.1 MB 00:02
Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
pci-ids-2022.07.02-0.oc00.noarch is a duplicate with pci-ids-2019.09.18-0.oc00.noarch
Updating : 1:libc-0.1.10-1.oc00.pentium4 1/4
Updating : 1:libc-devel-0.1.10-1.oc00.pentium4 2/4
Cleanup : 1:libc-devel-0.1.9-1.oc00.pentium4 3/4
Cleanup : 1:libc-0.1.9-1.oc00.pentium4 4/4
Rpmdb checksum is invalid: dCDPT(pkg checksums): libc-devel.pentium4 1:0.1.10-1.
oc00 - u
--- End code ---
The only unusual / concering issue would be this pci-ids remark:
"** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
pci-ids-2022.07.02-0.oc00.noarch is a duplicate with pci-ids-2019.09.18-0.oc00.noarch"
...but I can't imagine how that's impacting ANPM?
Anyways, CLI update was successful.
Navigation
[0] Message Index
[*] Previous page
Go to full version