[01:27:02] --- squinney has become available [01:30:28] --- dev-zero@jabber.org has become available [01:31:13] --- dev-zero@jabber.org has left [01:31:17] --- dev-zero@jabber.org has become available [01:51:30] --- dev-zero@jabber.org has left [03:13:52] --- dev-zero@jabber.org has become available [03:15:00] --- dev-zero@jabber.org has left [03:15:01] --- dev-zero@jabber.org has become available [03:48:40] --- abo has become available [05:04:53] --- Simon Wilkinson has become available [05:20:16] --- Simon Wilkinson has left [05:28:22] --- Simon Wilkinson has become available [05:32:25] --- Simon Wilkinson has left [05:43:21] --- Simon Wilkinson has become available [05:58:17] --- Simon Wilkinson has left [05:58:38] --- Simon Wilkinson has become available [06:09:48] --- Simon Wilkinson has left [06:19:10] --- meffie has become available [06:45:17] --- Brandon Allbery has become available [06:48:50] --- squinney has left [06:49:20] --- squinney has become available [07:46:58] --- deason has become available [08:09:45] --- kula has left [08:09:48] --- kula has become available [09:22:59] --- squinney has left [09:38:32] --- Simon Wilkinson has become available [10:00:43] --- meffie has left [10:17:43] --- mmeffie has become available [10:32:20] --- mmeffie has left [10:34:49] --- ktdreyer has left [10:35:08] --- ktdreyer has become available [10:39:32] --- mvitale has become available [10:44:13] --- jaltman/FrogsLeap has left: Disconnected [10:51:23] --- mmeffie has become available [10:58:03] --- jaltman/FrogsLeap has become available [13:23:30] I can't (easily?) build a package of openafs in freebsd's new package system, because kpasswd conflicts with MIT krb5. I thought I had seen traffic on this front go by on master, but all I'm finding is some rpm packaging change; is that right? [13:24:02] It's tempting to make kaserver a build-time option... [13:26:18] Yeah. I looked into that at one point. [13:26:32] But it has its fingers in a lot of pies. [13:26:36] "What was sufficiently annoying to cause you to stop?" [13:26:54] I think the shared library stuff broke me. [13:26:57] But that might be easier now. [13:27:07] It might, true. [13:27:35] And you could have an option which just doesn't install the binaries, rather than disabling the whole build. [13:28:26] I suppose that would be the easy way out, sure. [13:29:49] IIRC, there are political niceties here as well. In order to keep calling ourselves "AFS" we need to remain compatible with IBM's last AFS release. And I think that requires that we not disable kaserver entirely. [13:30:17] But Derrick can probably go into more detail about what we can or can't do. [13:31:00] I did vaguely recall such an issue, though I (naively?) assumed that keeping it off by default would be sufficient. [13:32:22] I suspect that a run-time switch would be fine. I don't know where we stand with build-time switches. [13:44:54] See http://www.openafs.org/pages/no-more-des.html [13:45:17] Thanks. [13:46:26] We missed the "before 1.6 release" bit, I see. [13:50:25] FWIW, I don't think we should be disabling any of our code from being built by default on master. Things bit rot far too fast if developers aren't forced to build them. [13:51:44] Yes, but ... would we complain so hard if kaserver rotted away? [13:52:27] there are still people using it, sadly [13:53:26] and as long as we are required to maintain compatibility with IBM AFS we must be able to build and package it [13:54:32] What does "package it" mean in this context? [13:54:49] What it would mean is that we'd do a 1.x rc, someone would complain that kaserver was broken, and then we'd have to wait until someone fixed it until the we could declare that release as final. [13:55:07] And that someone would probably be Derrick, because nobody else steps up to do that work. [13:55:27] --- Derrick Brashear has become available [13:55:41] i don't get to reply to anything from barnowl. [13:55:53] Derrick: that seems ... unfortunate. [13:55:56] actually it would be worse. The 1.x release would go final and then someone would complain and Derrick would be forced to fix it and push a 1.x.1 release [13:56:18] "Error 403 sending to openafs@conference.openafs.org Forbidden" [13:56:48] I keep getting 404s from jabber in barnowl that pop up periodically, but I have no idea why. [13:56:57] anyway, we are required to support it. it's unclear if that means we need to ship it by default. we should not turn it off by default. a —disable for it (which might secretly build and then not install it) would probably be ok. [14:37:04] --- mdionne has become available [14:53:47] --- Brandon Allbery has left [14:58:40] --- mvitale has left [14:59:11] --- mvitale has become available [15:01:39] --- mvitale has left [15:16:19] --- mmeffie has left [15:26:48] --- jaltman/FrogsLeap has left: Disconnected [15:28:10] --- jaltman/FrogsLeap has become available [18:13:09] --- dev-zero@jabber.org has left [18:13:18] --- dev-zero@jabber.org has become available [18:24:16] --- Derrick Brashear has left [18:47:57] --- mdionne has left [20:18:05] --- Derrick Brashear has become available [23:54:33] --- dev-zero@jabber.org has left [23:54:34] --- dev-zero@jabber.org has become available