Custom Query (344 matches)
Results (139 - 141 of 344)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#200 | fixed | %prein scriptlet fails with status 2 with coreutils-8.25-1 update | ||
Description |
I have seen this on several systems now, but I am not sure whether it may be a dependency issue (ordering of packages). YUM | update all from ANPM produces an error panel when finishing:
I can;t find a report in yum.log or in anpm.log, and yum reinstall coreutils from a prompt seems to run without the error. I'll update a few more systems from the prompt and see if i can catch this happening, as it would be odd for it to be coming from ANPM. I also can't find anything actually wrong with anything in the coreutils package, either, even without the reinstall. |
|||
#201 | fixed | rpmbuild | ||
Description |
The below sequence is executed as in the macros to see how many CPU's are available. But as we don't have getconf, RPM_BUILD_NCPUS is uninitialized. This leads to warnings and errors in the log. As we don't have getconf, I vote for initializing the value with 1 # Maximum number of CPU's to use when building, 0 for unlimited. #%_smp_ncpus_max 0 %_smp_mflags %([ -z "$RPM_BUILD_NCPUS" ] \\\ && RPM_BUILD_NCPUS="`/usr/bin/getconf _NPROCESSORS_ONLN`"; \\\ ncpus_max=%{?_smp_ncpus_max}; \\\ if [ -n "$ncpus_max" ] && [ "$ncpus_max" -gt 0 ] && [ "$RPM_BUILD_NCPUS" -gt "$ncpus_max" ]; then RPM_BUILD_NCPUS="$ncpus_max"; fi; \\\ if [ "$RPM_BUILD_NCPUS" -gt 1 ]; then echo "-j$RPM_BUILD_NCPUS"; fi) |
|||
#202 | duplicate | Package wipfc as additional Watcom tool | ||
Description |
It looks like the existing watcom.spec could be easily tweaked to include wipfc as an extra package. the latest one I have is version 1.9, but I'm sure there are newer ones available. We're updating the building instructions for Lucide, and want to point to an RPM for this. |