I would like to request removal of libxml (version 1): - it is not maintained upstream - last upstream release was in 2002 - it is "maintainer-needed" in Gentoo, but patrick and vostorga have recently committed some patches We currently have the library building against stable again, and patches for several security issues are committed. It needs to be audited against more security issues between 2004 and 2008 that we do not currently patch but which might affect libxml. However, the library only has three reverse dependencies. Two of these are false, and the only real reverse dependency (loki_setupdb) has support for libxml2 in its latest version. Since it's only a question of time until new bugs pop up and nothing really needs this anymore, let's get the blocking bugs fixed, and then mask and last-rite it with an extended period of 60 days. Victor, you seem to care about this package. Please comment.
I agree with the removal of dev-libs/libxml if and only if this does not force the removal of the reverse dependencies
(In reply to comment #1) > I agree with the removal of dev-libs/libxml if and only if this does not force > the removal of the reverse dependencies > Only 2 things depends on it? 22:37 <darkside_> !rdep dev-libs/libxml 22:37 <Willikins> Reverse RDEPEND for dev-libs/libxml: games-util/loki_setupdb-20050109 22:38 <darkside_> !ddep dev-libs/libxml 22:38 <Willikins> Reverse DEPEND for dev-libs/libxml: games-util/loki_patch-20050324 games-util/loki_setupdb-20050109 @security team: Can you provide a stronger recommendation to move this along.. ? :)
=games-util/loki_patch-20091105 now ships loki_setupdb and links against libxml2. As for a timeline, I propose to get it the new loki_patch stable in four weeks (2009-12-03) and mask the old ebuilds along with libxml two weeks later (2009-12-17) for removal.
Latest loki_patch is stable. Shall we proceed with the removal of libxml?
Yes, please. Be sure to include security bug 281446 in the mask message.
(In reply to comment #3) > =games-util/loki_patch-20091105 now ships loki_setupdb and links against > libxml2. > As for a timeline, I propose to get it the new loki_patch stable in four weeks > (2009-12-03) and mask the old ebuilds along with libxml two weeks later > (2009-12-17) for removal. > where in loki_patch can you detect loki_setupdb?: # equery f games-util/loki_patch-20091105 [ Searching for packages matching games-util/loki_patch-20091105... ] * Contents of games-util/loki_patch-20091105: /usr /usr/bin /usr/bin/loki_patch /usr/bin/make_patch /usr/share /usr/share/doc /usr/share/doc/loki_patch-20091105 /usr/share/doc/loki_patch-20091105/CHANGES.bz2 /usr/share/doc/loki_patch-20091105/NOTES.bz2 /usr/share/doc/loki_patch-20091105/README.bz2 /usr/share/doc/loki_patch-20091105/TODO.bz2 * Contents of games-util/loki_setupdb-20050109: /usr /usr/bin /usr/bin/setupdb /usr/share /usr/share/doc /usr/share/doc/loki_setupdb-20050109 /usr/share/doc/loki_setupdb-20050109/CHANGES.bz2 /usr/share/doc/loki_setupdb-20050109/README.bz2 /usr/share/loki_setupdb /usr/share/loki_setupdb/amd64 /usr/share/loki_setupdb/amd64/arch.o /usr/share/loki_setupdb/amd64/libsetupdb.a /usr/share/loki_setupdb/amd64/md5.o /usr/share/loki_setupdb/amd64/setupdb.o /usr/share/loki_setupdb/include /usr/share/loki_setupdb/include/arch.h /usr/share/loki_setupdb/include/config.h /usr/share/loki_setupdb/include/md5.h /usr/share/loki_setupdb/include/setupdb.h i cannot detect any flags for setupdb to be built. can you please let us know how this works out?
it's gone now, finally, thanks to games@ cooperation :)
