Summary: | Vulnerability in kdepim (VCF reader) | ||
---|---|---|---|
Product: | Gentoo Security | Reporter: | fbusse |
Component: | Vulnerabilities | Assignee: | Gentoo Security <security> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kde |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
fbusse
2004-01-14 21:58:52 UTC
note for security folks/gleppers: this is fixed by an upgrade to kdelibs-3.1.5 (or 3.2.0), which is in portage. sparc,amd64: could you guys please move either 3.1.5 or 3.2.0 to stable ? all other archs already have moved to one of those Sorry, just got back into the swing of things. Building KDE-3.2.0 now and if there aren't any problems I'll stabilize it. Was having problems with kde-3.1.5 components building but hoping 3.2.0 fixes them. OK, having trouble building kde because of a dependency and xine-lib's libtool not doing the right thing. This is causing kdeaddons to fail consistantly, which is causing problems stabilizing. Trying various elibtoolize args in xine-lib currently, but if anyone has any suggestions to help get this fixed, that would be great. The error seems to be related to the fact that kdemultimedia was built before a recent libtool fix was made to xine-lib. Re-emerging kdemultimedia now, hopefully that will make kdeaddons happy. Rebuilding kdemultimedia fixed the problem. KDE-3.2.0 is new stable on sparc. At the time of this announcment was sparc the only arch affected? IE was it stable already for all other arches? we still need amd64 [thats why they're in the cc list still] 3.2.0 is stable on amd64... Going to mark 3.1.5 stable as well today... GLSA 200404-02 issued. Did you CC -core this time? |