Re: pkg/44814: security/py-crypto contains (indirect probably) dependency inconsistency

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR pkg/44814; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/44814: security/py-crypto contains (indirect probably) 
dependency inconsistency
Date: Tue, 05 Apr 2011 05:11:00 +0700

     Date:        Mon,  4 Apr 2011 13:30:05 +0000 (UTC)
     From:        Thomas Klausner <wiz%NetBSD.org@localhost>
     Message-ID:  <20110404133005.2FA5963B84D%www.NetBSD.org@localhost>
 
   |  Well, I just installed the dependencies of py-crypto in an empty
   |  sandbox and ended up with:
 
 Yes, sorry for the state of that PR, I was in a hurry to get on a plane
 and just wanted to get out the PRs that I thought I sort of understood,
 and I didn't look at my build log nearly closely enough.
 
 For the problem I thought I was seeing (which it turns out I wasn't, it
 is something quite different) it actually made no sense for the problem
 to be with either one of the two packages involved (py-crypto or py-amkcrypto
 here) - they each need to build separately, so binary packages for both
 can exist, then one of them gets picked, which turns out to be the wrong one
 for some other package that's needed, then pkgsrc tries to build the other
 (by this stage it won't try a binary package install again, it reverts to
 compiling, even if a binary package exists) and then we find the conflict
 when compiling the one of the two that wasn't picked perviously.
 
 And sure enough, when I looked at the old build log more closely, it was
 really sysutils/fabric that my system was trying to build, that needs
 py-crypto, but py-amkcrypto had already been installed as a dependency
 (hence the pkg_add of py-crypto fails, pkgsrc then tries building it from
 source, that fails, which is what I saw when I filed the PR).
 
   |  So I cannot reproduce your problem. Please find out why py-amkcrypto
   |  is installed for you.
 
 OK, I have done that now, and it turns out to be a really silly bug
 (in a pkgsrc package) and not the more complex one I had thought it
 might be.
 
 sysutils/fabric needs both security/py-crypto and security/py-paramiko
 and for my binary package of py-paramiko ...
 
 Information for py26-paramiko-1.7.6.tgz:
 
 Comment:
 SSH2 protocol library
 
 Requires:
 py26-setuptools>=0.6c9
 python26>=2.6
 py26-amkCrypto>=2.0.1nb1
 
 Description:
 paramiko is a module for python 2.2 (or higher) that implements the SSH2
 protocol for secure (encrypted and authenticated) connections to remote
 machines. unlike SSL (aka TLS), SSH2 protocol does not require heirarchical
 certificates signed by a powerful central authority. you may know SSH2 as
 the protocol that replaced telnet and rsh for secure access to remote shells,
 but the protocol also includes the ability to open arbitrary channels to
 remote services across the encrypted tunnel (this is how sftp works,
 for example).
 
 Homepage:
 http://www.lag.net/paramiko/
 
 
 and that's why pm-amcrypto got installed, and then py-crypto can't be.
 
 But, back in December (Dec 6, 2010) py-paramiko was switched from using
 pk-amcrypto to py-crypto, so the question became why my binary package was
 still using py-amcrypto as its dependency.
 
 This one turns out to be really simple - my system had no idea it was
 supposed to have replaced its version of py-paramiko, because of a trivial
 bug that the patch below corrects ...
 
 Index: Makefile
 ===================================================================
 RCS file: /cvsroot/NetBSD/pkgsrc/security/py-paramiko/Makefile,v
 retrieving revision 1.9
 diff -u -r1.9 Makefile
 --- Makefile   6 Dec 2010 22:22:08 -0000       1.9
 +++ Makefile   4 Apr 2011 21:47:50 -0000
 @@ -3,7 +3,7 @@
  
  DISTNAME=             paramiko-1.7.6
  PKGNAME=              ${PYPKGPREFIX}-${DISTNAME}
 -PKG_REVISION= 2
 +PKGREVISION=  2
  CATEGORIES=           security
  MASTER_SITES= http://pypi.python.org/packages/source/p/paramiko/
  EXTRACT_SUFX= .zip