Bug 1210890
Summary: | logic error failure & SysFileTree | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joel C Ewing <jcewing> |
Component: | oorexx | Assignee: | GĂ©rard Milmeister <gemi> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 21 | CC: | gemi |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-02 11:00:10 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joel C Ewing
2015-04-10 19:47:58 UTC
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The Fedora version for this bug should be changed to f22.as it persists in f22 with all updates as of 2015-11-04 exactly as described in detail in the 2015-04-10 15:47:58 posting. This bug was in f17, f18, f19, f20, f21, and now it is verified as still in the f22 oorexx packages on the Fedora repository with latest updates installed, so whatever technique being used to carry these packages to the next Fedora release is doing a perfect job of propagating the packaging error. I feel certain from the history of this bug that it will persist in any subsequent version of Fedora unless someone either fixes the apparent packaging error or removes this package from the Fedora repository (which was one suggestion). These oorexx packages were somehow incorrectly built when they were restructured from the way the app is packaged at oorexx.org (whose packages have never shown the missing library issue or the SysFileTree bug that is in the Fedora repository packages). The verification on f22: With f22 at the latest update levels, installing oorexx-4.1.0-9.fc22 from Fedora repository also pulls in oorexx-libs-4.1.0-9 . From a directory containing the previously documented (2015-04-10) cksft.rex program, attempting to execute cksft gets 100% failure with ./cksft.rex Logic error: Failure loading required base library After install oorexx-devel-4.1.0-9.fc22 from Fedora repository, REXX programs will run, but 100% of the time have an error in the results of function SysFileTree as evidenced from the rsults of the supplied cksft test program: ./cksft.rex Result from Call SysFileTree ~/ProgApps/REXX/cksft.rex, "dirout", "F" -rwxrwxr-x /home/jcewing/ProgApps/REXX/cksft.rex !!!oorexx bug present, date time size not returned. I do not have enough knowledge of Fedora packaging or program development conventions or I would attempt to fix this myself. But just from looking at the results it appears that in the Fedora packaging (1) an essential base component of oorexx was erroneously assumed to only be relevant to doing oorexx development and was put in oorexx-devel when it should have been in oorexx; and (2) one or more components of oorexx are at at an inconsistent maintenance level with either the rest of oorexx or with Fedora. Just a wild guess, but since the observed bug occurs in extracting directory info from the system, I suspect one or more oorexx libraries in the Fedora packages are out of sync with Fedora and should have been regenerated at a new Fedora release but weren't. The filesystem for which the SysFileTree bug was verified is in ext4 format on a logical volume, in case that is relevant. I have finished tesing this problem on Fedora 23 as well. It looks like the new release of oorexx in the Fedora 23 repository (oorexx-4.2.0-1.f23, oorexx-libs-4.2.0-1.f23, oorexx-devel-4.2.0-1.f23) has finally fixed the oorexx runtime SysFileTree problem for Fedora23. At that level the test program gets: f23wslive REXX]$ ./cksft.rex Result from Call SysFileTree ~/ProgApps/REXX/cksft.rex, "dirout", "F" 11/09/15 11:35a 1033 -rwxrwxr-x /home/jcewing/ProgApps/REXX/cksft.rex All documented parameters appear to be returned. but the problem with the undocumented dependency on oorexx-devel is still there with Fedora 23 and oorexx-4.2.0-1.f23. I just noticed Fedora 22 repository now has added a unified oorexx-4.2.0-9940.fedora package (not yet in Fedora 23 repository) which seems to be a merging of oorexx, oorexx-libs, oorexx-devel. I haven't yet tested it but if this this new release fixes the SysFileTree problem for f22 as well, merging all to a single rpm would certainly be expected to fix the remaining issue with the undocumented dependency on oorexx-devel. If a similar unified single rpm becomes available for Fedora 23, that should hopefully resolve the remaining issue there as well. OOPS. Disregard the fedora 22 remarks in last two paragraphs of previous comment. Neither issue of #1210890 is resolved on f22 (unless you go with rpms from oorexx.org). I thought I was looking at a package list from my stripped down f22 test system, but in retrospect was obviously looking at a list from my main system. The "oorexx-4.2.0-9940.fedora" unified package is not from the Fedora repository but is of course the fully functional rpm installed from oorexx.org that was mentioned as a problem circumvention near the end of the original description entry. If the oorexx-4.2.0-1.fc23 and related rpms for for oorexx 4.2.0-1 in Fedora 23 repository were retrofitted to Fedora 22, that should at least make it possible to resolve the SysFileTree bug that is in the oorexx 4.1.0-9 version on Fedora 22. Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |