Fix plugin registration issues caused by changes in RPM (rhbz#1523296).

Originally, the transaction file triggers provided just list of
filenames, but that was not intentional and the list now contains also
directory entries. Fortunatelly, these entries can be filtered out if
the path end withi '/'.

vagrant.spec

@@ -4,7 +4,7 @@
 
 Name: vagrant
 Version: 1.9.1
-Release: 2%{?dist}
+Release: 3%{?dist}
 Summary: Build and distribute virtualized development environments
 Group: Development/Languages
 License: MIT
@@ -213,7 +213,7 @@ rescue => e
   puts "Vagrant plugin.json is not properly initialized: #{e}"
 end
 
-%transfiletriggerin -p %{_bindir}/ruby -- %{dirname:%{vagrant_plugin_spec}}
+%transfiletriggerin -p %{_bindir}/ruby -- %{dirname:%{vagrant_plugin_spec}}/
 begin
   $LOAD_PATH.unshift "%{vagrant_dir}/lib"
   begin
@@ -232,7 +232,7 @@ rescue => e
   puts "Vagrant plugin register error: #{e}"
 end
 
-%transfiletriggerun -p %{_bindir}/ruby -- %{dirname:%{vagrant_plugin_spec}}
+%transfiletriggerun -p %{_bindir}/ruby -- %{dirname:%{vagrant_plugin_spec}}/
 begin
   $LOAD_PATH.unshift "%{vagrant_dir}/lib"
   begin
@@ -308,6 +308,9 @@ end
 
 
 %changelog
+* Tue Dec 12 2017 Vít Ondruch <vondruch@redhat.com> - 1.9.8-3
+- Fix plugin registration issues caused by changes in RPM (rhbz#1523296).
+
 * Tue Feb 28 2017 Vít Ondruch <vondruch@redhat.com> - 1.9.1-2
 - Obsolete vagrant-atomic, since it is now merged in Vagrant.