Custom Query (344 matches)
Results (94 - 96 of 344)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#322 | fixed | man-db 2.7.6.1-2 should require newer db4 | ||
Description |
This is a similar case to issues reported and discussed in #257 and #259, I think. System was a fresh ArcaOS 5.0.3.4 beta with updated bootstrap (20181127), which includes: db4-4.8.30-6 db4-utils-4.8.30-6 Installing the above man-db and detected prerequisites of: groff-base libiconv libiconv-utils libpipeline leaves man unable to function: N:\USR\BIN\MAN.EXE MAND2761->DB48.___db185_open 127 Updating db4 to 4.8.30-8 apparently provides the missing export. Recommend handling this the same way as #257 until the enhancement discussed in #259 has been implemented. The average user is not going to know what's wrong, I'm afraid. |
|||
#323 | invalid | Consider setting sane value for INFOPATH in postin scriptlet | ||
Description |
Currently, info (5.2-3) and man-db (2.7.6.1-3) do not set path variables during installation. While some of us prefer to set these values for ourselves, others may not be aware as to why, for example: [q:\] info info fails to find info. It might be wise to add basic settings via postin scriplet for each of these (basic = x:\usr\share\man and x:\usr\share\info, where x: is %UNIXROOT%). |
|||
#325 | fixed | createrepo 0.10.4-2 seems terribly broken (truncated metadata and bad behavior) | ||
Description |
createrepo-0.10.4-2.oc00.noarch.rpm is currently in experimental. This version of the script seems to dump all output to the console (even when told to be --quiet), and out of a total of 302 packages in the current on-disc ArcaOS repository, we seem to only get metadata built on the first(?) 34 of them. Invocation: [j:\localrep] sh -c j:/usr/bin/createrepo --no-database --simple-md-filenames . Result: scrolling output to the screen, and when done, very small metadata files, which, though readable, do not contain info on all files. --simple-md-filenames seems to be respected, as does --no-database. --quiet (or -q) has no effect on the excess screen output, though it does seem to suppress the initial report of workers starting up (tried with no additional workers, then 10, and finally 20) and the final report of the files being written. The older 0.4.11-2 works perfectly. I'm marking this as an "other" component instead of python itself. |