new upstream release

[perltidy.git] / debian / changelog

diff --git a/debian/changelog b/debian/changelog
index e3ecf72c1c017b5efbfda6c6f1e2496e0fce1e9a..f6f78d5d0085a3b1467044f83153f58729e45916 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,10 +1,37 @@
+perltidy (20170521-1) unstable; urgency=medium
+
+  * New upstream release
+  * Die if an existing perltidy.ERR cannot be removed to block overwriting
+    of arbitrary files by a symlink attack. (closes: #862667) Thanks to
+    Jakub Wilk for identifying this issue.
+  * Update standards version to 4.1.1; no changes
+
+ --
+
+perltidy (20140328-1) unstable; urgency=medium
+
+  * New upstream release
+    + Avoid creating perltidy.LOG file
+
+ -- Don Armstrong <don@debian.org>  Mon, 07 Apr 2014 18:27:01 -0700
+
+perltidy (20130922-1) unstable; urgency=medium
+
+  * New upstream release (closes: #740559)
+  * Update VCS location after switching to git
+  * Fix insecure tmpfile creation (closes: #740670)
+
+ -- Don Armstrong <don@debian.org>  Fri, 07 Mar 2014 18:18:01 -0800
+
 perltidy (20120701-1) unstable; urgency=low
 
-  * New upstream release 
+  * New upstream release (closes: #681368)
     + Don't munge contents of __DATA__ even when they
     look like POD (closes: #614288)
+  * Switch to debhelper auto rules
+  * Document VCS location
 
- -- Don Armstrong <don@debian.org>  Fri, 13 Jul 2012 15:00:16 -0700
+ -- Don Armstrong <don@debian.org>  Fri, 13 Jul 2012 16:50:35 -0700
 
 perltidy (20101217-1) unstable; urgency=low