Correct misspellings in Net::LDAP::FAQ

perl-LDAP.spec

@@ -1,11 +1,13 @@
 Name:           perl-LDAP
 Version:        0.65
-Release:        12%{?dist}
+Release:        13%{?dist}
 Epoch:          1
 Summary:        LDAP Perl module
 License:        GPL+ or Artistic
 URL:            https://metacpan.org/release/perl-ldap
 Source0:        https://cpan.metacpan.org/authors/id/M/MA/MARSCHAP/perl-ldap-%{version}.tar.gz
+# Correct misspellings in Net::LDAP::FAQ, in upstream after 0.65
+Patch0:         perl-ldap-0.65-Correct-misspellings.patch
 BuildArch:      noarch
 BuildRequires:  perl-interpreter
 BuildRequires:  perl-generators
@@ -70,6 +72,7 @@ maintenance functions such as adding, deleting or modifying entries.
 
 %prep
 %setup -q -n perl-ldap-%{version}
+%patch0 -p1
 chmod -c 644 bin/* contrib/* lib/Net/LDAP/DSML.pm
 perl -pi -e 's|^#!/usr/local/bin/perl\b|#!%{__perl}|' contrib/*
 # Remove bundled libraries
@@ -98,6 +101,9 @@ make test
 %{_mandir}/man3/*.3pm*
 
 %changelog
+* Thu Apr 04 2019 Petr Pisar <ppisar@redhat.com> - 1:0.65-13
+- Correct misspellings in Net::LDAP::FAQ
+
 * Fri Feb 01 2019 Fedora Release Engineering <releng@fedoraproject.org> - 1:0.65-12
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
 

perl-ldap-0.65-Correct-misspellings.patch

@@ -0,0 +1,88 @@
+From fba956c630d10b6ab1453f195d28dd1d3196bd04 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= <ppisar@redhat.com>
+Date: Tue, 4 Oct 2016 13:44:35 +0200
+Subject: [PATCH] Correct misspellings
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Signed-off-by: Petr Písař <ppisar@redhat.com>
+---
+ lib/Net/LDAP/FAQ.pod      | 4 ++--
+ lib/Net/LDAP/Schema.pod   | 2 +-
+ lib/Net/LDAP/Security.pod | 8 ++++----
+ 3 files changed, 7 insertions(+), 7 deletions(-)
+
+diff --git a/lib/Net/LDAP/FAQ.pod b/lib/Net/LDAP/FAQ.pod
+index fd34ccb..99d9036 100644
+--- a/lib/Net/LDAP/FAQ.pod
++++ b/lib/Net/LDAP/FAQ.pod
+@@ -1195,7 +1195,7 @@ attribute name and no values.
+ In LDAPv3, this is defined to always work even if that attribute
+ doesn't exist in the entry.
+ 
+-ie:
++I.e.:
+ 
+   my $mesg = $ldap->modify( $entry, replace => { %qv_del_arry } );
+ 
+@@ -1770,7 +1770,7 @@ eldapo - a directory manager's blog
+ http://eldapo.blogspot.de/
+ 
+ Eine deutsche LDAP Website
+-A german LDAP Website
++A German LDAP Website
+ http://verzeichnisdienst.de/ldap/Perl/index.html
+ 
+ (non-exhaustive) list of LDAP software on Wikipedia
+diff --git a/lib/Net/LDAP/Schema.pod b/lib/Net/LDAP/Schema.pod
+index 92ab69c..e222b72 100644
+--- a/lib/Net/LDAP/Schema.pod
++++ b/lib/Net/LDAP/Schema.pod
+@@ -32,7 +32,7 @@ may be an object class, attribute or syntax) then a case-insensitive name
+ or raw OID (object identifier, in dotted numeric string form, e.g. 2.5.4.0)
+ may be supplied.
+ 
+-Each returned item of schema (eg an attribute definition) is returned
++Each returned item of schema (e.g. an attribute definition) is returned
+ in a HASH. The keys in the returned HASH are lowercase versions of
+ the keys read from the server. Here's a partial list (not all HASHes
+ define all keys) although note that RFC 4512 permits other keys as
+diff --git a/lib/Net/LDAP/Security.pod b/lib/Net/LDAP/Security.pod
+index a12a259..6ca48f1 100644
+--- a/lib/Net/LDAP/Security.pod
++++ b/lib/Net/LDAP/Security.pod
+@@ -130,7 +130,7 @@ standardized version of SSL.
+ 
+ You can only use TLS with an LDAPv3 server. That is because the
+ standard (RFC 4511) for LDAP and TLS requires that the I<normal> LDAP
+-connection (ie., on port 389) can be switched on demand from plain text
++connection (i.e., on port 389) can be switched on demand from plain text
+ into a TLS connection. The switching mechanism uses a special extended
+ LDAP operation, and since these are not legal in LDAPv2, you can only
+ switch to TLS on an LDAPv3 connection.
+@@ -151,18 +151,18 @@ I<mechanism>. A number of mechanisms are defined, such as CRAM-MD5.
+ 
+ The use of a mechanism like CRAM-MD5 provides a solution to the
+ password sniffing vulnerability, because these mechanisms typically do
+-not require the user to send across a secret (eg., a password) in the
++not require the user to send across a secret (e.g., a password) in the
+ clear across the network. Instead, authentication is carried out in a
+ clever way which avoids this, and so prevents passwords from being
+ sniffed.
+ 
+ B<Net::LDAP> supports SASL using the B<Authen::SASL> class. Currently the
+-only B<Authen::SASL> subclasses (ie., SASL mechanism) available are
++only B<Authen::SASL> subclasses (i.e., SASL mechanism) available are
+ CRAM-MD5 and EXTERNAL.
+ 
+ Some SASL mechanisms provide a general solution to the sniffing of all
+ data on the network vulnerability, as they can negotiate confidential
+-(ie., encrypted) network connections. Note that this is over and above
++(i.e., encrypted) network connections. Note that this is over and above
+ any SSL or TLS encryption! Unfortunately, perl's B<Authen::SASL> code
+ cannot negotiate this.
+ 
+-- 
+2.20.1
+