| Summary: | warnings when installing rpms | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Nicolas Lécureuil <mageia> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Low | CC: | arnaud.patard, dan, mageia, pterjan, shlomif, thierry.vignaud, tmb |
| Version: | Cauldron | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | uClibc-0.9.33.2-4.mga4 | CVE: | |
| Status comment: | |||
|
Description
Nicolas Lécureuil
2014-01-01 01:15:49 CET
Manuel Hiebel
2014-01-01 21:50:09 CET
Keywords:
(none) =>
Triaged This warning is harmless, but it is a little disconcerting. ldconfig could be patched to stop looking in those locations by default on x86_64, but that would change it's default behaviour which may be unexpected. The simplest solution is probably to just pipe stderr to /dev/null in the postinstall script. The other option is to just include those two empty directories in the RPM. That might be the cleanest, as it also provides a hint to the user that they are there and available. BTW why do you have uclibc installed? Priority:
Normal =>
Low it was on a chroot to build rpms ( i don't recall which one btw ). uClibc gets sometimes pulled in by libz.so.1 (provided by lib(64)uClibc-zlib1) and urpmi tends to suggest picking the uClibc over the lib(64)zlib1 I guess we need to update prefer.vendor.list CC:
(none) =>
tmb I've now pushed new meta-task that prefers zlib over uClibc-zlib Fixed in uClibc-0.9.33.2-5.mga4 Status:
NEW =>
RESOLVED |