commit fea6fe64e1ebc9499c98163de17946cf7c78e2c0 (patch)
parent 0c097d9f devel/release-checks.sh: adjust to LIBNOTMUCH version checks
tree 2f86b7fe429a42a1fa954f4b86ed61476b4b88a2
author David Bremner <david@tethera.net> 2014-01-01 07:23:25 -0400
committer David Bremner <david@tethera.net> 2014-01-01 07:44:52 -0400
debian: rename NEWS.Debian to NEWS
Apparently I had it backwards: NEWS is installed as NEWS.Debian, not
vice-versa.
---
debian/{NEWS.Debian => NEWS} | 0
debian/changelog | 7 +++++++
2 files changed, 7 insertions(+)
diff --git a/debian/NEWS.Debian b/debian/NEWS
similarity index 100%
rename from debian/NEWS.Debian
rename to debian/NEWS
diff --git a/debian/changelog b/debian/changelog
index 0663f1d8..0f2b69b8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+notmuch (0.17-2) unstable; urgency=medium
+
+ * Bug fix: "package should warn in a NEWS.Debian file about possible
+ pre-upgrade action", thanks to Jonas Smedegaard (Closes: #733853).
+
+ -- David Bremner <bremner@debian.org> Wed, 01 Jan 2014 07:44:25 -0400
+
notmuch (0.17-1) unstable; urgency=low
* New upstream feature release. See /usr/share/doc/notmuch/NEWS.gz
glossary
--------
Commit objects reference one tree, and zero or more parents.
Single parent commits can typically generate a patch in
unified diff format via `git format-patch'.
Multiple parents means the commit is a merge.
Root commits have no ancestor. Note that it is
possible to have multiple root commits when merging independent histories.
Every commit references one top-level tree object.
git clone https://yhetil.org/notmuch.git