This is an automated email from the git hooks/post-receive script.

fsfs pushed a commit to branch master
in repository libfile-policy-perl.

commit aa3b75e2bda297aed6722e93adedde5b5f387aa9
Author: Florian Schlichting <f...@debian.org>
Date:   Fri Nov 25 21:41:54 2016 +0100

    Declare compliance with Debian Policy 3.9.8
---
 debian/control | 32 ++++++++++++++++----------------
 1 file changed, 16 insertions(+), 16 deletions(-)

diff --git a/debian/control b/debian/control
index 00efdfb..4022a1b 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,7 @@ Build-Depends-Indep: perl,
                      libtest-assertions-perl,
                      liblog-trace-perl,
                      libfile-slurp-perl
-Standards-Version: 3.7.3
+Standards-Version: 3.9.8
 Vcs-Browser: 
https://anonscm.debian.org/cgit/pkg-perl/packages/libfile-policy-perl.git
 Vcs-Git: 
https://anonscm.debian.org/git/pkg-perl/packages/libfile-policy-perl.git
 Homepage: https://metacpan.org/release/File-Policy
@@ -22,25 +22,25 @@ Depends: ${perl:Depends},
          libtest-assertions-perl,
          liblog-trace-perl,
          libfile-slurp-perl
-Description: Simple policy for file I/O functions
- This defines the policy for file I/O with modules such as 
- File::Slurp::WithinPolicy. The purpose is to allow systems administrators to 
- define locations and restrictions for applications' file I/O and give app 
- developers a policy to follow. Note that the module doesn't ENFORCE the 
policy 
- - application developers can choose to ignore it (and systems administrators 
+Description: simple policy for file I/O functions
+ File::Policy defines the policy for file I/O with modules such as
+ File::Slurp::WithinPolicy. The purpose is to allow systems administrators to
+ define locations and restrictions for applications' file I/O and give app
+ developers a policy to follow. Note that the module doesn't ENFORCE the policy
+ - application developers can choose to ignore it (and systems administrators
  can choose not to install their applications if they do!).
  .
- You may control which policy gets applied by creating a File::Policy::Config 
- module with an IMPLEMENTATION constant. You may write your own policy as a 
+ You may control which policy gets applied by creating a File::Policy::Config
+ module with an IMPLEMENTATION constant. You may write your own policy as a
  module within the File::Policy:: namespace.
  .
- By default (if no File::Policy::Config is present), the File::Policy::Default 
- policy gets applied which doesn't impose any restrictions and provides 
+ By default (if no File::Policy::Config is present), the File::Policy::Default
+ policy gets applied which doesn't impose any restrictions and provides
  reasonable default locations for temporary and log files.
  .
- The motivation behind this module was a standard, flexible approach to allow 
- a site wide file policy to be defined. This will be most useful in large 
- environments where a few sysadmins are responsible for code written by many 
- other people. Simply ensuring that submitted code calls check_safe() ensures 
- file access is sane, reducing the amount of effort required to do a security 
+ The motivation behind this module was a standard, flexible approach to allow
+ a site wide file policy to be defined. This will be most useful in large
+ environments where a few sysadmins are responsible for code written by many
+ other people. Simply ensuring that submitted code calls check_safe() ensures
+ file access is sane, reducing the amount of effort required to do a security
  audit.

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/pkg-perl/packages/libfile-policy-perl.git

_______________________________________________
Pkg-perl-cvs-commits mailing list
Pkg-perl-cvs-commits@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-perl-cvs-commits

Reply via email to