[pkg-php-pear] Crypt_Blowfish conflict between PEAR and phpseclib
taffit at debian.org
Sun Jun 30 16:11:14 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
Le 30/06/2013 11:00, Mathieu Parent a écrit :
> 2013/6/29 David Prévot <david at tilapin.org>:
> I packaged php-crypt-blowfish because it was a Horde dependency at
> that time. […] As php-crypt-blowfish doesn't have any
> rdepends, it may be removed.
Well, owncloud is currently its only rdepends then, thanks.
> Also, is there any link between PEAR's Crypt_Blowfish and Owncloud
They ship en embedded copy of it, yes:
(And the owncloud Debian package instead depend on php-crypt-blowfish).
> is this a fork, with compatible API? A quick read suggests that
> it is compatible
Thanks, I must have a closer look, and may eventually take over
php-crypt-blowfish and use the phpseclib as a source instead of PEAR
(can do a provide and conflict from php-seclib as a start).
> Also, for the binary package name, ask pkg-php-tools. This will probably be:
Wouldn’t that contradict the naming scheme? I thought that a package
providing /usr/share/php/Crypt/Blowfish.php, taking its source from the
Crypt_Blowfish PEAR package, should have been named php-crypt-blowfish.
Is that reserved to source coming from pear.php.net?
> Which is not very good (read dh_pear manpage about overrides).
Did you meant dh-make-pear(1)?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the pkg-php-pear