On Mon, Jul 28, 2008 at 07:58:46PM -0700, Ivan Kohler wrote:
> I'm looking for the recommended way (or at least some advice) to fix
> Bug#492814 <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492814>.
> Should I upload (to unstable) a libxcrypt version 1:2.4-2 (no changes
> from 2.4-2 currently in testing), and a 1:2.4.1-2 version of
> libpam-unix2 (no changes except to fix the build-dep)? And then ask for
> a freeze exception?
Er.
* Revert to upstream 2.4.1 to get this compiled & working against lenny
libxcrypt (closes: Bug#487487).
Why in the world, with that changelog entry, did the build-deps get changed
to point to a sid-only version of libxcrypt in the first place?
Also, why do you propose to address this by adding an epoch to a library
(which is never good), instead of fixing the libxcrypt build problem in
unstable and getting that unblocked?
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
