From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from <gentoo-dev+bounces-24677-garchives=archives.gentoo.org@gentoo.org>) id 1I6AFT-00014U-Oo for garchives@archives.gentoo.org; Wed, 04 Jul 2007 19:10:48 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l64J9jsH000306; Wed, 4 Jul 2007 19:09:45 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l64J7hDs030397 for <gentoo-dev@lists.gentoo.org>; Wed, 4 Jul 2007 19:07:43 GMT Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id EC3306445E for <gentoo-dev@lists.gentoo.org>; Wed, 4 Jul 2007 19:07:42 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: 0.016 X-Spam-Level: X-Spam-Status: No, score=0.016 required=5.5 tests=[AWL=0.016] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KCi93C-v+yJ5 for <gentoo-dev@lists.gentoo.org>; Wed, 4 Jul 2007 19:07:41 +0000 (UTC) Received: from homeless.linbsd.net (homeless.linbsd.net [64.127.112.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 5A6C765063 for <gentoo-dev@gentoo.org>; Wed, 4 Jul 2007 19:07:41 +0000 (UTC) Received: from [66.92.11.131] (dsl092-011-131.sfo1.dsl.speakeasy.net [66.92.11.131]) by homeless.linbsd.net (Postfix) with ESMTP id 1A2B658424 for <gentoo-dev@gentoo.org>; Wed, 4 Jul 2007 12:07:40 -0700 (PDT) Subject: [gentoo-dev] New Linux-PAM stabling plans From: Ned Ludd <solar@gentoo.org> To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Date: Wed, 04 Jul 2007 12:07:39 -0700 Message-Id: <1183576059.7927.2.camel@localhost> Precedence: bulk List-Post: <mailto:gentoo-dev@lists.gentoo.org> List-Help: <mailto:gentoo-dev+help@gentoo.org> List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@gentoo.org> List-Subscribe: <mailto:gentoo-dev+subscribe@gentoo.org> List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org> X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id l64J9juK000306 X-Archives-Salt: 04370232-0535-4404-b094-b473330eaf33 X-Archives-Hash: 5987e33311d78997c2b47472fdcf5052 Forwarded by request of somebody thats smart/lucky enough to not=20 be on this list but still monitoring it. -------- Forwarded Message -------- From: Diego 'Flameeyes' Petten=F2 <flameeyes@gentoo.org> Subject: New Linux-PAM stabling plans Date: Wed, 4 Jul 2007 20:51:36 +0200 Hi everybody; sorry to mail here rather than -dev, but I'm not subscribed to it and I have no intention to subscribe in the next future. Please forward a copy of this message to gentoo-dev if you can and want, thanks. Since while I was gone nobody took care of PAM, I had to resume work on it (sigh), and almost at the same time I got reported that PAM 0.78 doesn't allow to set some limits in limits.conf to "unlimited" value. This is a good enough reason to work actively on marking 0.99 stable. Unfortunately, 0.99 upgrade isn't entirely trivial, as pam_stack.so is gone, pam_userdb is moved and so is pam_console, plus a few more modules are no more present at all. To solve this issue, I just wrote an upgrade guide in the PAM project that will appear soon at [1]. That guide should contain all the information needed to pass through the upgrade easily. I also have an ebuild ready to commit that will make a lot of warnings and various noise when the pam.d file in the system still refers to the removed packages, pointing to the upgrade guide. It also dies if the user still has pam_stack or other modules that are not moved but really not available. (I'm still not sure where I should die: pkg_setup would stop users from building pkgs, pkg_preinst would waste people time if they didn't notice the warnings at setup stage, as right now the warnings are printed in both, and preinst dies). I'd really like comments on the guide (that still has to pass through an editor -- Josh would you mind? :) -- so please skip grammar check for now ;) ), so that I can address whatever is needed. Now, I could ask stabilization even right now, but, I'm not sure how to convey enough focus on what is going to happen. I'll write about this on Planet for sure, but then? Is GLEP42 ready? Should I ask PR people to publish this? Anyway, I'll at least give it a week or two for more testing and for proofreading the guide; developers are invited to try the upgrade on their (non-production first) machines, and report immediately any problem with the procedure. Sorry for the delay to get a decent PAM working, thanks for waiting. [1] http://www.gentoo.org/proj/en/base/pam/upgrade-0.99.xml Diego "Flameeyes" Petten=F2 http://farragut.flameeyes.is-a-geek.org/ --=20 gentoo-dev@gentoo.org mailing list