The following issues with Arca Noae Package Manager (ANPM) are known to exist at this time:
- In certain instances, upon installing the bootstrap package (usually, during the initial ANPM setup), it will be necessary to add some packages to enable existing installed applications to continue to function. A known example of this is the libicu-legacy package which is required for Apache OpenOffice (see related information on path validation, below). Watch for a dedicated wiki page for this.
- Filtering the available package list by repository may fail to display the latest version of a package if a newer version is available from another repository. Example:
Searching for ‘poppler-qt’ (not installed), perhaps version 0.999.0-1.oc00 is available on my-other-great-repo. Even though there are (older) versions available on netlabs-rel, these are not shown in the list of available packages.
If the filter drop-downs are used to show only packages from netlabs-rel, poppler-qt will no longer appear at all. This is because these filters are simply subsets of the already-queried data (and not new queries).
In this case, the only way to view versions of poppler-qt from netlabs-rel is to perform a search, which sends a new query to yum with the show-obsoletes flag set.
This is expected behavior.
- When updating one or more packages, some installed RPMs do not have current versions listed in Download Packages confirmation dialog. This is normal for packages which are actually being replaced by newer versions as opposed to simply being updated. The differences between these two operations are beyond the scope of this document (the end result is the same: the newer files are installed and the older files are removed). This is expected behavior.
- The i386 architecture has been deprecated in favor of i686. As a result, packages which have been updated for the i686 and pentium4 architectures may not reflect the current version numbers in the available package list, although the icon may indicate that they have been updated recently. Selecting the listed package will always install the latest available for the configured architecture, however. As a workaround, start ANPM with the /DUP switch. This will cause all available versions (duplicate package names, but all versions and architectures) to be displayed in the available package list. We are working on improving the package filtering logic to address this.
- Some YUM plugins may cause unpredictable results, as they might when running yum from the command line. These are either limitations of the plugins themselves or how they interact with other applications (namely, Python) on the OS/2 platform.
Management of secure repos excludes editing them. This capability is planned for a later release.(Editing of secure repos added in version 1.0.4.)
- Changing architectures (i386 to i686, i386 to pentium4, pentium4 to i686, etc.) from the RPM Platform Configuration dialog or by editing %UNIXROOT%\etc\rpm\platform directly may lead to unpredictable results. This is a YUM issue, and not a defect of ANPM. We are considering ways to help make these changes easier.
- It is not possible to quickly scroll through lists of files by selecting the first letter of the package name. This is a standard system limitation for these types of windows; the scroll will stop on the first occurrence in any column of the letter pressed, not just the name.
- Once an operation has started, there is no option to abort. This is intentional, as the idea is to never leave the system in an inconsistent state. Simply allow the operation to complete and then reverse the procedure to undo (e.g., install package A, then uninstall it).
- Selecting more than one version of the same package for installation always results in the latest version being installed. If it is necessary to install an older version of a package, use the menu choice to install a specific version.
- It is possible that in some circumstances, enabling the path validation check may cause other applications to stop working correctly. If this is the case for your system, simply disable the path validation check in the Preferences dialog and restore CONFIG.SYS from backup.
Inability to reach one or more enabled repositories results in no packages listed as available (refresh fails). This is a limitation of YUM. Verify the repository configuration in the Repository Manager, and perhaps temporarily disable any non-responsive repositories (transient server or network errors could account for being unable to reach an otherwise-valid repository).(Inaccessible repositories are now administratively disabled, after a generous retry period of 1-2 minutes. Exit ANPM, ensure that connectivity has been established, perhaps by pinging the repository’s server, and restart ANPM to retry.)
- Damaged repository metadata may appear to hang ANPM for an extended period of time with the progress bar reporting:
Updating repository data...
Exit ANPM and restart ANPM to retry. If this does not result in an expected update time, exit ANPM and wait some time before retrying. Generally, the repository or mirror maintainer will address the issue without requiring third-party notification of the problem. In extreme cases, notify the repository or mirror maintainer of the problem.
- While it is possible to share the yum cache between multiple boot partitions, be careful to set the UNIXROOT environment variable appropriately for each partition. ANPM will attempt to warn before downloading and (re)installing a yum/rpm configuration, but it is not possible to foresee every possible scenario.
- If using a local YUM repository, it must reside on the same volume as the one where ANPM has been installed.
- Currently, only RPM packages may be managed by ANPM. A future release will add support for managing WarpIN archives and repositories.
- After installing or updating one or more RPM packages, an information panel is displayed reporting:
Error: Rpmdb checksum is invalid: dCDPT(pkg checksums): <package name>
This is a known YUM defect. ANPM is not generating this error, only passing it through from YUM. See the Netlabs RPM project ticket 117 for more information. (Generally, this error is only cosmetic, though it has been known to appear on multiple platforms, not just OS/2.)
- If multiple versions of the same package are listed as installed, from the Manage menu, try running YUM tools > Maintenance > Complete transaction. Usually, this is just the result of the prior version of an update package not being removed from the RPM database.
This entry last updated: by