[kloczek@zie.pg.gda.pl: Re: [Pkg-shadow-devel] Debian patch to configure.in]

Martin Quinson martin.quinson@loria.fr
Sat, 7 May 2005 21:47:39 +0200


--/e2eDi0V/xtL+Mc8
Content-Type: multipart/mixed; boundary="neYutvxvOLaeuPCA"
Content-Disposition: inline


--neYutvxvOLaeuPCA
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello pam guys,

As shadow packaging follower, I would like to have your advice on this one.
It looks like that the attached patch against upstream shadow is needed only
because of the debian patches against the pam. Would you mind to explain the
situation to me, please?

We try to reduce the amount of debian specific patching as much as possible
by reinjecting the good bits to upstream...

Thanks for your time, Mt.

----- Forwarded message from Tomasz K?oczko <kloczek@zie.pg.gda.pl> -----

=46rom: Tomasz K?oczko <kloczek@zie.pg.gda.pl>
To: Christian Perrier <bubulle@kheops.frmug.org>
Cc: pkg-shadow-devel@lists.alioth.debian.org
Subject: Re: [Pkg-shadow-devel] Debian patch to configure.in
Date: Thu, 5 May 2005 15:36:13 +0200 (CEST)

On Wed, 4 May 2005, Christian Perrier wrote:

> Tomasz, the attached patch is a Debian patch to ./configure.in
>=20
> Do you have an advice about integrating it upstream=A0?
>=20
> I indeed have no idea of the real purpose, but you people developers
> will certainly know..:-)

I can only ones more repeat: this is not bug in shadow but in PAM=20
disributed in Debian. libpam_misc uses libpam API and must be linked with=
=20
libpam. If this library will be linked with this libpam attached patch=20
will be not neccessary :)

kloczek
--=20
-----------------------------------------------------------
*Ludzie nie maj? problem=F3w, tylko sobie sami je stwarzaj?*
-----------------------------------------------------------
Tomasz K?oczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gda.pl*

----- End forwarded message -----

--neYutvxvOLaeuPCA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="004_configure.in.dpatch"

--- shadow-4.0.3.orig/configure.in
+++ shadow-4.0.3/configure.in
@@ -265,9 +265,10 @@
 	AC_CHECK_LIB(pam, pam_start,
 		[AC_DEFINE(USE_PAM)
 		LIBPAM="-lpam"
-		AC_CHECK_LIB(pam_misc, main,
+		AC_CHECK_LIB(pam_misc, misc_conv,
 			[LIBPAM="$LIBPAM -lpam_misc"],
-			AC_MSG_ERROR(libpam_misc is missing)
+			AC_MSG_ERROR(libpam_misc is missing),
+			-lpam
 		)]
 		[AC_MSG_CHECKING(use login access checking if PAM not used)
 		AC_DEFINE(LOGIN_ACCESS)

--neYutvxvOLaeuPCA--

--/e2eDi0V/xtL+Mc8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCfRtbIiC/MeFF8zQRAg1YAKDLWknTAXwJmNXnScWC01jsk9EPwACg1sXb
m276M4I+kvW8PmAcZ97mATc=
=OgQY
-----END PGP SIGNATURE-----

--/e2eDi0V/xtL+Mc8--