ASpell 0.60.6.1-4 behaves like term is NULL (but it is OS2)

[Alfredo Fernández Díaz]

This a direct follow up to #178, in more ways than one.

After we seemingly got ASpell running in that one, I finally came round to start testing in a work machine. As per Murphy's law, it just fails again.

So, this is an old Spanish MCP2 system, with a fresh yum/rpm install, and of course SET TERM=OS2 is in place, but ASpell still behaves here as it did in #178 in the virtual toy system with no SET TERM.

Sure enough, my first suspicion is again ANPM didn't do something it must have, but I didn't even have a look at the ASpell sources or ANPM internals yet so I don't know what to check/test next and see if I need to (re)install something with yum. Any ideas?

Thank you in advance,

(Yes, I am still alive -- just came out of deep freeze ;)

[Alfredo Fernández Díaz]

Exported list of installed packages

[Silvan Scherrer]

you need to compare your running system to this one. and also make sure /@unixroot/usr/lib is one of the first entries in LIBPATH. Beside that I don't have an idea right now.

[Alfredo Fernández Díaz]

Of course I need to compare systems, and there are a number of differences -- I just don't see anything obvious (or even vaguely seemingly related to the issue). /usr/lib is atop of LIBPATH.

However, I tried to reinstall aspell ("yum reinstall aspell" from D:\Temp) and I got this message that apparently means yum is happy with the installation even if something happened along the way. Does this give you any ideas (the transaction file that could not be deleted only contains the text line "install 0:aspell-0.60.6.1-4.oc00.pentium4")?:

---

Non-fatal POSTIN scriptlet failure in rpm package aspell-0.60.6.1-4.oc00.pentium
4
error: Couldn't fork %post(aspell-0.60.6.1-4.oc00.pentium4): Interrupted system
call
Failed to remove transaction file /@unixroot/var/lib/yum/transaction-done.2018-0
9-27.23.53.43

LIBC PANIC!!
LIBC fork: Child aborting fork()! rc=0xfffffffc
pid=0x014f ppid=0x014e tid=0x0001 slot=0x00c8 pri=0x0200 mc=0x0000 ps=0x0010
D:\USR\BIN\PYTHON2.7.EXE
LIBC066 0:00001e78
cs:eip=005b:1d201e78 ss:esp=0053:0012cf2c ebp=0012cf34

ds=0053 es=0053 fs=150b gs=0000 efl=00012212

eax=00000040 ebx=1394a9c0 ecx=178a0000 edx=00000018 edi=00000000 esi=178a0000
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

Installed:

aspell.pentium4 0:0.60.6.1-4.oc00

Complete!

---

[Silvan Scherrer]

I have no idea whats wrong on your system. But it must be your system, as I can't reproduce it here and your other installation also works right?

[Alfredo Fernández Díaz]

Yes, my other installation (a virtual machine within this one) still seems to work after upgrading from .60.6.1-2 (current level back when I did the initial testing) to 1-4 (current as of now).

I didn't do anything 'special' that I can think of, so I would expect you to suggest what to check/test for next -- reproducing it yourself w/o any solid information yet would be clairvoyance ;)

Is there a way to retrieve a package and not install it so I can compare both systems are actually getting the same file (that would rule out problems downloading the rpm itself)? Or check the integrity of installed packages (VLC seems to work on this machine, and it uses other stuff installed via yum as well, so not everything can be badly broken)?

[Silvan Scherrer]

Sorry but this is a bit out of scope of free service. As it's clearly your home grown old system. I can work on that in my spare time, but it will take weeks. Sorry again but the day only has 24 hours and my spare time/will is limited.

[Alfredo Fernández Díaz]

The virtual systems here are meant to replace the real one eventually, so I guess that's OK -- my time is limited as well, and if I *really* need aspell I will use it on virtual or some other system meanwhile. I still thought if the problem was known or could be readily identified this could contribute to make the whole thing more manageable, though.

[Silvan Scherrer]

as said I heavily believe it's your env. Some old term stuff from emx or whatever. When you can proof it happens on a fresh installed ArcaOS as well I will look at it of course. But on older home grown systems it's hard and I can't do that for free. So until you have more infos or better proofs I close the ticket.

[Alfredo Fernández Díaz]

Sorry if I am misreading you or I haven't been clear myself, but are you angry with me?:

precisely because we are talking about my 'home' system, which is not very modern, I never implied that your aspell port is broken, or that you need to fix it, let alone invest work hours to make it work on a system that may or may not be too different from your intended target -- all I was asking for is some things I could check myself to find out whatever may be wrong in my system, i.e. what aspell expects to find and may be missing from my system, or what may choke it beyond rpm dependencies.

I understand that you may not be able to tell me 'check if you have this, or if that is enabled' unless you go through hoops and loops to find out yourself in the first place, in which case simply stating so and leaving it at that sounds perfectly reasonable to me.

If you think I misused the ticket system, please tell me what I did wrong and I'll refrain from doing that in the future -- re: the 'blocker' thing, I didn't think it would be so important given that aspell is not even listed as a component, and I meant this issue is a blocker for me on this system anyway, not in general or anything.

Of course, if it's all in my mind and you were not mad at me at all, sorry -- your last post just gave me that overall vibe.