From 9111a3982f9e17b770e6c882694da635cf675638 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=B6rg=20Frings-F=C3=BCrst?= <debian@jff-webhosting.net>
Date: Sun, 5 Apr 2015 11:43:35 +0200
Subject: Add bugscripts; transition libgphoto2

---
 debian/shotwell.bug-script | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 debian/shotwell.bug-script

(limited to 'debian/shotwell.bug-script')

diff --git a/debian/shotwell.bug-script b/debian/shotwell.bug-script
new file mode 100644
index 0000000..bcb8409
--- /dev/null
+++ b/debian/shotwell.bug-script
@@ -0,0 +1,28 @@
+#!/bin/bash
+
+REPORTBUG_VERSION=$(dpkg-query -f '${source:Version}' -W reportbug)
+LOG_FILE='~/.cache/shotwell/shotwell.log'
+
+# Depending on whether reportbug is new enough, we either write the output of
+# our various commands to a file and attach them to the report (this needs
+# reportbug ≥ 6.5.0) or just write them to the body of the bug report.
+if dpkg --compare-versions "$REPORTBUG_VERSION" ge "6.5.0"; then
+
+    # We don’t clean up this directory because there is no way to know when
+    # reportbug finished running, and reportbug needs the files around.
+    # Given that those are just a couple of kilobytes in size and people
+    # generally don’t file a lot of bugs, I don’t think it’s a big deal.
+    DIR=$(mktemp -d)
+
+    echo "-- BEGIN ATTACHMENTS --" >&3
+
+    #
+    # logfile
+    #
+    if [ -f ${LOG_FILE} ]; then
+	cat ${LOG_FILE} >$DIR/logfile.user
+	echo $DIR/logfile.user >&3
+    fi
+
+    echo "-- END ATTACHMENTS --" >&3
+fi
-- 
cgit v1.2.3