Package: php-crypt-gpg / 1.6.11-3
Metadata
| Package | Version | Patches format |
|---|---|---|
| php-crypt-gpg | 1.6.11-3 | 3.0 (quilt) |
Patch series
view the series file| Patch | File delta | Description |
|---|---|---|
| Group write if write access is needed.patch | (download) |
Crypt_GPG-1.6.11/tests/GeneralTest.php |
3 3 + 0 - 0 ! |
group write if write access is needed
In the build and autopkgtest environment ~/.gnupg is not accessible and
cannot be created, failing GeneralTestCase::testSetEngine with
Crypt_GPG_FileException: The 'homedir' "/.gnupg" is not readable or
does not exist and cannot be created. This can happen if 'homedir'
is not specified in the Crypt_GPG options, Crypt_GPG is run as the
web user, and the web user has no home directory.
|
| testExportPrivateKey_with_bad_pass Ignore E_NOTICE report.patch | (download) |
Crypt_GPG-1.6.11/tests/ExportPrivateKeyTest.php |
1 1 + 0 - 0 ! |
testexportprivatekey_with_bad_pass(): ignore e_notice reporting. Depending on the output of a race condition gpg(1) might terminate before the call to `fwrite($fdCommand,,)` which then issues an E_NOTICE report about the EPIPE. That is allowed behavior for which we don't want PHPUnit to convert the notice into an exception. Bug-Debian: https://bugs.debian.org/1006028 |
| Tests Fix race condition during GNUPGHOME cleanup.patch | (download) |
Crypt_GPG-1.6.11/tests/TestCase.php |
14 7 + 7 - 0 ! |
test suite: fix race condition during $gnupghome cleanup. gpg tries to remove sockets hence races against tearDown(). We therefore ignore unlink()/rmdir() errors. Bug-Debian: https://bugs.debian.org/1080394 |
| Compatibility with recent PHPUnit 13.patch | (download) |
Crypt_GPG-1.6.11/tests/KeyTest.php |
12 6 + 6 - 0 ! |
compatibility with recent phpunit (13) Use assertContainsOnlyInstancesOf() instead of assertContainsOnly(). |
1
