Summary: | Stabilize sys-devel/libtool-2.2.10 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | SpanKY <vapier> |
Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | jeremy.william.murphy |
Priority: | High | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
sys-devel/libtool-2.2.10 failed tests
x86 emerge --info |
Description
SpanKY
![]() Created attachment 248062 [details]
sys-devel/libtool-2.2.10 failed tests
ERROR: 99 tests were run,
5 failed (4 expected failures).
7 tests were skipped.
Created attachment 248063 [details]
x86 emerge --info
if you're getting failures, you're supposed to file a new bug and mark it a blocker of this one (In reply to comment #3) > if you're getting failures, you're supposed to file a new bug and mark it a > blocker of this one > OK bug 338102 Test failures seem to be fixed when bug 338113 goes to stable. Any hints on how to actually test libtool in situ? About a third of my installed packages depend on it but I'm not sure how/when they use it. (In reply to comment #6) > Any hints on how to actually test libtool in situ? About a third of my > installed packages depend on it but I'm not sure how/when they use it. > About any library package (with shared library) that runs eautoreconf (i.e. has inherit autotools) will use libtool. Then imagemagick and mpg123 will use libltdl.so from libtool to load it's plugins, so if 'convert foo.jpg bar.png' or 'mpg123 foo.mp3' still works... it can load the plugins, and works. Kewl. x86 OK. btw, there arent any blockers for this stabilizing in case arch maintainers think there's something left to be done first ... amd64 done =sys-devel/libtool-2*:1.5 ("=sys-devel/libtool-2*:1.5" is blocking sys-devel/libtool-2.2.10) What is the procedure for upgrading from libtool 2.2.6b to 2.2.10? I'm nervous about removing libtool and reinstalling it. resolve it like any other blocker. please seek assistance in a user support forum as bugzilla isnt for that. ppc64 stable (passes all but one "archive" test, and it's expected one (for gentoo because of sandbox) -> so, no issues) x86 stable, thanks David and Myckel Stable for HPPA. arm stable ppc done Tested on SPARC64 with no regressions from the previous stable version (2.2.6b). Please consider for stabalisation. alpha/ia64/m68k/s390/sh/sparc stable, closing |