On Mon, Jul 28, 2008 at 09:52:24PM -0700, Steve Langasek wrote:
> 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?
They weren't. The build-deps were changed to point to they previous
version of libxcrypt, which is in *lenny*. They were changed not "just
because", but because the newer version isn't working, and there is
little chance of getting it working soon.
> Also, why do you propose to address this by adding an epoch to a library
> (which is never good),
Precisely why I asked for advice before doing anything... it did sound
like there might be a better way..
> instead of fixing the libxcrypt build problem in
> unstable and getting that unblocked?
Perhaps I was unclear.
Take a look at the bug report, please.
To fix the libxcrypt build problem in unstable, I'll need to revert to
the previous version. 3.0 currently in unstable is unsuitable for
release.
How do you suggest I revert to libxcrypt 2.4 to fix the build problems
in unstable *without* using a library epoch?
(FWIW, nothing except libpam-unix2 links against libxcrypt)
--
_ivan