None of the versions in tree works with stable glibc, or kernel. So it's fair to say the situatuation has detoriated to a state where removal is viable option. Bug list here: http://tinyurl.com/ydgcdzt Alternatively bug 310627 would solve most of above, but I haven't heard from the maintainer...
One month later and no response from maintainers net-fs/openafs net-fs/openafs-legacy net-fs/openafs-kernel ... will be masked for removal in 2 weeks, includes dropping "afs" support from heimdal, root, cyrus-imap-dev and gdm via optional USE="afs".
The afs is of utmost importance to our 1k core cluster. Can we take over the maintenance? 1.4.12.1 ebuilds are trivial to create from the 1.4.11.
what packages specifically are you talking about ? there are three in question.
Bug 290529 is for stabilizing openafs >= 1.4.10 (and notice it's a blocker for glibc-2.10 stabilization) Bug 310627 is for bumping to latest version, mentioning ~arch openafs doesn't compile with kernel >= 2.6.33 Bug 282196 is about openafs = 1.4.10 freezing with kernel >= 2.6.30 Bug 273723 is about openafs = 1.4.9 not building with kernel >= 2.6.30 Bug 314715 is about openafs = 1.4.11 (latest in ~arch) causing kernel panic with current stable gentoo-sources (2.6.32) To put it short: There's nothing usable in tree for stable, or ~arch users at the moment.
1.4.12.1 release should solve all the bugs. From the release notes: An update of the 1.4.12 release, 1.4.12.1 adds support for Linux kernel 2.6.34, fixes a bug with 64 bit kernels on 32 bit hardware, and avoids a panic when the volume data cannot be read or written from persistent storage. ebuilds net-fs/openafs and net-fs/openafs-kernel for 1.4.12.1 could be just clones of 1.4.11 ebuilds except for fixing the source location (last subdir is 1.4.12 and not 1.4.12.1)
(In reply to comment #5) > 1.4.12.1 release should solve all the bugs. From the release notes: > An update of the 1.4.12 release, 1.4.12.1 adds support for Linux kernel 2.6.34, > fixes a bug with 64 bit kernels on 32 bit hardware, and avoids a panic when the > volume data cannot be read or written from persistent storage. > ebuilds net-fs/openafs and net-fs/openafs-kernel for 1.4.12.1 could be just > clones of 1.4.11 ebuilds except for fixing the source location (last subdir is > 1.4.12 and not 1.4.12.1) > I hear you, but there is often more than it looks like at first -- it really needs a dedicated maintainer...
ive updated the ebuild and added Andrej as proxy maintainer and closed all bugs
