Opened 7 years ago

Closed 7 years ago

#59 closed defect (wontfix)

Yum install cannot install (8) packages

Reported by: Al Savage Owned by: Yuri Dario
Priority: major Milestone:
Component: yum Version:
Severity: Keywords:
Cc: asavage@…, Dave Yeo


eCS 2.1
rpm-yum-bootstrap-1_3.wpi gave no errors upon its installation.
At Yum Bootstrap Console,
[Q:\]yum install yum

wasn't able to install eight of the 55 packages:


ash.i386 0:0.0.0-10.oc00 ca-certificates.noarch0:2011.80-1.oc00
coreutils.i386 0:8.6-9.oc00 file-libs.i386 0:5.04-6.oc00
ncurses.i386 0:5.7-4.oc00 openssl.i386 0:1.0.0a-5.oc00
rpm.i386 0:4.8.1-14.oc00 tcl.i386 1:8.5.9-2.oc00

Mar 13 20:54:28 ash-0.0.0-10.oc00.i386: 100
Mar 13 20:54:34 file-libs-5.04-6.oc00.i386: 100
Mar 13 20:54:38 1:tcl-8.5.9-2.oc00.i386: 100
Mar 13 20:54:39 ca-certificates-2011.80-1.oc00.noarch: 100
Mar 13 20:54:42 openssl-1.0.0a-5.oc00.i386: 100
Mar 13 20:54:43 ncurses-5.7-4.oc00.i386: 100
Mar 13 20:54:43 coreutils-8.6-9.oc00.i386: 100
Mar 13 20:54:43 rpm-4.8.1-14.oc00.i386: 100

The exact errors scrolled off the VIO window and I couldn't find a log
that contained the same text, but it seemed to be complaining about cpio
and symlinks on every one AFAICT.

I have been unable to find a support channel for this product.

Change History (22)

comment:1 Changed 7 years ago by Al Savage

During creation of this ticket, I received this notification at the top of the screen (after a very long pause):

"Warning: The ticket has been created, but an error occurred while sending notifications: [Errno 8] hostname nor servname provided, or not known "

comment:2 Changed 7 years ago by Al Savage

Cc: asavage@… added

comment:3 Changed 7 years ago by Dave Yeo

Cc: Dave Yeo added

comment:4 Changed 7 years ago by Yuri Dario

is this a HPFS386 partition?

comment:5 Changed 7 years ago by Al Savage

It is an eCS 2.1 JFS partition.

comment:6 Changed 7 years ago by Yuri Dario

Very strange. Could you try newer bootstrap?

requires manual changes to config.sys (path/libpath/set unixroot).

comment:7 Changed 7 years ago by Al Savage

I am unable to unzip one file in that distribution:

13860 0 0 02-02-2012 19:45 usr/bin/[.exe

I d/l'd it twice. What is that file?

comment:8 Changed 7 years ago by Silvan Scherrer

are you sure you have only one cpio.exe around? not that you have a older one in the path.

comment:9 Changed 7 years ago by Al Savage

I have three:

[C:\ecs\bin]cpio --version
cpio (GNU cpio) 2.11

[Q:\tmp\yumbt\usr\bin]cpio --version
cpio (GNU cpio) 2.11

[Q:\usr\bin]cpio --version
cpio (GNU cpio) 2.11


What is "[.exe" and is that a legal filename?

comment:10 Changed 7 years ago by Silvan Scherrer

what file date does the on in ecs\bin have? and how does your 'set path=' look like?

comment:11 Changed 7 years ago by Silvan Scherrer

and yes the [.exe is a legal name for a file. and rpm brings that with it

comment:12 Changed 7 years ago by Al Savage

C:\ecs\bin\cpio.exe 75,664 .a.. 12-03-12 9:31:44
Q:\tmp\yumbt\usr\bin\cpio.exe 76,477 .a.. 11-18-10 22:55:22
Q:\usr\bin\cpio.exe 75,664 .a.. 12-03-12 18:31:44

I've run UNZIP 6.00 from the commandline, and [.exe unzips OK, so it was my filemanager's invoking of UNZIP that was preventing that file from unzipping. I'll look into that further later, but it's not a problem with the pkg.

I am traveling to another state for three days, leaving in an hour. I can VNC to the eCS box from the road, but I may be slow to respond until Monday, 08Apr2013.

Last edited 7 years ago by Al Savage (previous) (diff)

comment:13 in reply to:  12 Changed 7 years ago by Yuri Dario

Now put paths in front of PATH/LIBPATH and set UNIXROOT.
PYTHONPATH and PYTHONHOME are known conflicts.

comment:14 Changed 7 years ago by Al Savage


[Q:\]set unixroot

With no changes to CONFIG.SYS or PATH, merely unzipping the 1.4 pkg from , running "yum install yum", the install did not give any errors:

[Q:\]yum install yum
netlabs-rel 100% |=========================| 1.3 kB 00:00
netlabs-rel/primary 100% |=========================| 298 kB 00:04
netlabs-rel: ##################################################### 1023/1036S
etting up Install Process
Package yum-3.2.27-5.oc00.noarch already installed and latest version
Nothing to do


Is that what I should expect?

I went on to run "yum install rpm" and it gave this error:

Error unpacking rpm package rpm-4.8.1-16.oc00.i386
error: unpacking of archive failed on file /@unixroot/usr/bin/rpmdb;51661023: cp
io: symlink

comment:15 Changed 7 years ago by Yuri Dario

You need to set at least BEGINLIBPATH=q:\usr\lib to be sure to load the correct dlls.

comment:16 Changed 7 years ago by Al Savage

[Q:\]SET BEGINLIBPATH=q:\usr\lib

[Q:\]yum install rpm
netlabs-rel 100% |=========================| 1.3 kB 00:00
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package rpm.i386 0:4.8.1-16.oc00 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved


Package Arch Version Repository Size



rpm i386 4.8.1-16.oc00 netlabs-rel 650 k

Transaction Summary

Install 0 Package(s)
Upgrade 1 Package(s)

Total size: 650 k
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction

Updating : rpm-4.8.1-16.oc00.i386 1/2

Error unpacking rpm package rpm-4.8.1-16.oc00.i386
error: unpacking of archive failed on file /@unixroot/usr/bin/rpmdb;5166ed58: cp
io: symlink
rpm-4.8.1-14.oc00.i386 was supposed to be removed but is not!


rpm.i386 0:4.8.1-16.oc00


comment:17 Changed 7 years ago by Yuri Dario

are you able to manually unpack a rpm file? download a rpm file and unpack it with

requires rpm2cpio and cpio binaries (they are included in 1.4 bootstrap zip).

comment:18 Changed 7 years ago by Al Savage

[C:\temp]unrpm apr-1.4.5-1.oc00.i686.rpm
211 blocks

It *appears* that it's unpacked correctly.

comment:19 Changed 7 years ago by Silvan Scherrer

when you do the "yum install" are there other apps running?
if there are other apps open i would close them all and try again. to be sure no wrong dlls are loaded.
i did the yum/rpm installation some days ago on a fresh ecs 2.1 and it run flawless.

comment:20 Changed 7 years ago by Lewis Rosenthal

Dave, just a couple of thoughts, here, as you pointed to this bug in eCS-Technical...

Is this a JFS volume or HPFS?
Run a chkdsk recently?
Can you indeed create symlinks (see if you have a working ln.exe somewhere)? The syntax would be ln -s <something> <somewhere>, as in:

(existing file \var\temp\abc.exe)

ln -s \var\temp\abc.exe \abc-link.exe

(Of course, you need a shell which can then make use of a symlink, but a dir should at least list it.)

Speaking of shells, under which shell are you running this?

comment:21 Changed 7 years ago by Al Savage

I appreciate all who tried to help.

I no longer have the resources to continue to attempt to resolve this problem. Please close this ticket.

comment:22 Changed 7 years ago by Silvan Scherrer

Resolution: wontfix
Status: newclosed

closed in request of the reporter

Note: See TracTickets for help on using tickets.