[Pkg-openssl-changes] r619 - openssl/trunk/debian/patches

Sun Dec 22 15:37:06 UTC 2013

Author: kroeckx
Date: 2013-12-22 15:37:06 +0000 (Sun, 22 Dec 2013)
New Revision: 619

Modified:
   openssl/trunk/debian/patches/libdoc-manpgs-pod-spell.patch
Log:
Fix libdoc-manpgs-pod-spell.patch to only fix spalling errors

It was also doing things like adding =back and =over 4 where not needed
and reordering the items.


Modified: openssl/trunk/debian/patches/libdoc-manpgs-pod-spell.patch
===================================================================

--- openssl/trunk/debian/patches/libdoc-manpgs-pod-spell.patch	2013-12-22 14:55:27 UTC (rev 618)
+++ openssl/trunk/debian/patches/libdoc-manpgs-pod-spell.patch	2013-12-22 15:37:06 UTC (rev 619)
@@ -1,5 +1,7 @@
---- a/doc/crypto/ASN1_generate_nconf.pod
-+++ b/doc/crypto/ASN1_generate_nconf.pod
+Index: openssl-1.0.1e/doc/crypto/ASN1_generate_nconf.pod
+===================================================================
+--- openssl-1.0.1e.orig/doc/crypto/ASN1_generate_nconf.pod	2013-12-22 16:16:44.695836636 +0100
++++ openssl-1.0.1e/doc/crypto/ASN1_generate_nconf.pod	2013-12-22 16:16:44.691836721 +0100
 @@ -61,7 +61,7 @@
  =item B<INTEGER>, B<INT>
  
@@ -9,8 +11,10 @@
  is normally interpreted as a decimal value unless the prefix B<0x>
  is included.
  
---- a/doc/crypto/BN_BLINDING_new.pod
-+++ b/doc/crypto/BN_BLINDING_new.pod
+Index: openssl-1.0.1e/doc/crypto/BN_BLINDING_new.pod
+===================================================================
+--- openssl-1.0.1e.orig/doc/crypto/BN_BLINDING_new.pod	2013-12-22 16:16:44.695836636 +0100
++++ openssl-1.0.1e/doc/crypto/BN_BLINDING_new.pod	2013-12-22 16:16:44.691836721 +0100
 @@ -48,7 +48,7 @@
  
  BN_BLINDING_convert_ex() multiplies B<n> with the blinding factor B<A>.
@@ -20,8 +24,10 @@
  several threads). BN_BLINDING_invert_ex() multiplies B<n> with the
  inverse blinding factor B<Ai>. If B<r> is not NULL it will be used as
  the inverse blinding.
---- a/doc/crypto/EVP_BytesToKey.pod
-+++ b/doc/crypto/EVP_BytesToKey.pod
+Index: openssl-1.0.1e/doc/crypto/EVP_BytesToKey.pod
+===================================================================
+--- openssl-1.0.1e.orig/doc/crypto/EVP_BytesToKey.pod	2013-12-22 16:16:44.695836636 +0100
++++ openssl-1.0.1e/doc/crypto/EVP_BytesToKey.pod	2013-12-22 16:16:44.691836721 +0100
 @@ -17,7 +17,7 @@
  
  EVP_BytesToKey() derives a key and IV from various parameters. B<type> is
@@ -31,8 +37,10 @@
  an 8 byte buffer or NULL if no salt is used. B<data> is a buffer containing
  B<datal> bytes which is used to derive the keying data. B<count> is the
  iteration count to use. The derived key and IV will be written to B<key>
---- a/doc/crypto/EVP_EncryptInit.pod
-+++ b/doc/crypto/EVP_EncryptInit.pod
+Index: openssl-1.0.1e/doc/crypto/EVP_EncryptInit.pod
+===================================================================
+--- openssl-1.0.1e.orig/doc/crypto/EVP_EncryptInit.pod	2013-12-22 16:16:44.695836636 +0100
++++ openssl-1.0.1e/doc/crypto/EVP_EncryptInit.pod	2013-12-22 16:16:44.691836721 +0100
 @@ -152,7 +152,7 @@
  
  EVP_EncryptInit(), EVP_DecryptInit() and EVP_CipherInit() behave in a
@@ -42,8 +50,10 @@
  initialized and they always use the default cipher implementation.
  
  EVP_EncryptFinal(), EVP_DecryptFinal() and EVP_CipherFinal() behave in a
---- a/doc/crypto/EVP_PKEY_cmp.pod
-+++ b/doc/crypto/EVP_PKEY_cmp.pod
+Index: openssl-1.0.1e/doc/crypto/EVP_PKEY_cmp.pod
+===================================================================
+--- openssl-1.0.1e.orig/doc/crypto/EVP_PKEY_cmp.pod	2013-12-22 16:16:44.695836636 +0100
++++ openssl-1.0.1e/doc/crypto/EVP_PKEY_cmp.pod	2013-12-22 16:16:44.691836721 +0100
 @@ -26,7 +26,7 @@
  The funcion EVP_PKEY_cmp_parameters() compares the parameters of keys
  B<a> and B<b>.
@@ -53,19 +63,10 @@
  (if present) of keys B<a> and B<b>.
  
  =head1 NOTES
---- a/doc/crypto/X509_STORE_CTX_get_error.pod
-+++ b/doc/crypto/X509_STORE_CTX_get_error.pod
-@@ -278,6 +278,8 @@
- an application specific error. This will never be returned unless explicitly
- set by an application.
- 
-+=back
-+
- =head1 NOTES
- 
- The above functions should be used instead of directly referencing the fields
---- a/doc/crypto/pem.pod
-+++ b/doc/crypto/pem.pod
+Index: openssl-1.0.1e/doc/crypto/pem.pod
+===================================================================
+--- openssl-1.0.1e.orig/doc/crypto/pem.pod	2013-12-22 16:16:44.695836636 +0100
++++ openssl-1.0.1e/doc/crypto/pem.pod	2013-12-22 16:16:44.691836721 +0100
 @@ -201,7 +201,7 @@
  PEM_write_bio_PKCS8PrivateKey() and PEM_write_PKCS8PrivateKey()
  write a private key in an EVP_PKEY structure in PKCS#8
@@ -75,21 +76,10 @@
  use: unlike all other PEM routines the encryption is applied at the
  PKCS#8 level and not in the PEM headers. If B<cipher> is NULL then no
  encryption is used and a PKCS#8 PrivateKeyInfo structure is used instead.
---- a/doc/ssl/SSL_CTX_set_client_CA_list.pod
-+++ b/doc/ssl/SSL_CTX_set_client_CA_list.pod
-@@ -70,6 +70,10 @@
- 
- The operation succeeded.
- 
-+=back
-+
-+=over 4
-+
- =item 0
- 
- A failure while manipulating the STACK_OF(X509_NAME) object occurred or
---- a/doc/ssl/SSL_CTX_set_verify.pod
-+++ b/doc/ssl/SSL_CTX_set_verify.pod
+Index: openssl-1.0.1e/doc/ssl/SSL_CTX_set_verify.pod
+===================================================================
+--- openssl-1.0.1e.orig/doc/ssl/SSL_CTX_set_verify.pod	2013-12-22 16:16:44.695836636 +0100
++++ openssl-1.0.1e/doc/ssl/SSL_CTX_set_verify.pod	2013-12-22 16:16:44.695836636 +0100
 @@ -169,8 +169,8 @@
  failure, if wished. The callback realizes a verification depth limit with
  more informational output.
@@ -101,136 +91,3 @@
  The example is realized for a server that does allow but not require client
  certificates.
  
---- a/doc/ssl/SSL_CTX_use_psk_identity_hint.pod
-+++ b/doc/ssl/SSL_CTX_use_psk_identity_hint.pod
-@@ -81,6 +81,8 @@
- 
- Return values from the server callback are interpreted as follows:
- 
-+=over 4
-+
- =item > 0
- 
- PSK identity was found and the server callback has provided the PSK
-@@ -94,9 +96,15 @@
- connection will fail with decryption_error before it will be finished
- completely.
- 
-+=back
-+
-+=over 4
-+
- =item 0
- 
- PSK identity was not found. An "unknown_psk_identity" alert message
- will be sent and the connection setup fails.
- 
-+=back
-+
- =cut
---- a/doc/ssl/SSL_accept.pod
-+++ b/doc/ssl/SSL_accept.pod
-@@ -49,12 +49,20 @@
- The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
- established.
- 
-+=back
-+
-+=over 4
-+
- =item 0
- 
- The TLS/SSL handshake was not successful but was shut down controlled and
- by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
- return value B<ret> to find out the reason.
- 
-+=back
-+
-+=over 4
-+
- =item E<lt>0
- 
- The TLS/SSL handshake was not successful because a fatal error occurred either
---- a/doc/ssl/SSL_connect.pod
-+++ b/doc/ssl/SSL_connect.pod
-@@ -41,10 +41,13 @@
- 
- =over 4
- 
--=item 1
-+=item E<lt>0
- 
--The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
--established.
-+The TLS/SSL handshake was not successful, because a fatal error occurred either
-+at the protocol level or a connection failure occurred. The shutdown was
-+not clean. It can also occur of action is need to continue the operation
-+for non-blocking BIOs. Call SSL_get_error() with the return value B<ret>
-+to find out the reason.
- 
- =item 0
- 
-@@ -52,13 +55,10 @@
- by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
- return value B<ret> to find out the reason.
- 
--=item E<lt>0
-+=item 1
- 
--The TLS/SSL handshake was not successful, because a fatal error occurred either
--at the protocol level or a connection failure occurred. The shutdown was
--not clean. It can also occur of action is need to continue the operation
--for non-blocking BIOs. Call SSL_get_error() with the return value B<ret>
--to find out the reason.
-+The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
-+established.
- 
- =back
- 
---- a/doc/ssl/SSL_do_handshake.pod
-+++ b/doc/ssl/SSL_do_handshake.pod
-@@ -50,12 +50,20 @@
- The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
- established.
- 
-+=back
-+
-+=over 4
-+
- =item 0
- 
- The TLS/SSL handshake was not successful but was shut down controlled and
- by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
- return value B<ret> to find out the reason.
- 
-+=back
-+
-+=over 4
-+
- =item E<lt>0
- 
- The TLS/SSL handshake was not successful because a fatal error occurred either
---- a/doc/ssl/SSL_shutdown.pod
-+++ b/doc/ssl/SSL_shutdown.pod
-@@ -97,6 +97,10 @@
- The shutdown was successfully completed. The "close notify" alert was sent
- and the peer's "close notify" alert was received.
- 
-+=back
-+
-+=over 4
-+
- =item 0
- 
- The shutdown is not yet finished. Call SSL_shutdown() for a second time,
-@@ -104,6 +108,10 @@
- The output of L<SSL_get_error(3)|SSL_get_error(3)> may be misleading, as an
- erroneous SSL_ERROR_SYSCALL may be flagged even though no error occurred.
- 
-+=back
-+
-+=over 4
-+
- =item -1
- 
- The shutdown was not successful because a fatal error occurred either


