reportbug wrapper and template file for filing alignment bugs
authorSteve McIntyre <steve@einval.com>
Thu, 20 Dec 2018 16:01:15 +0000 (16:01 +0000)
committerSteve McIntyre <steve@einval.com>
Thu, 20 Dec 2018 16:01:15 +0000 (16:01 +0000)
bug-script [new file with mode: 0755]
template.txt [new file with mode: 0644]

diff --git a/bug-script b/bug-script
new file mode 100755 (executable)
index 0000000..ce1b023
--- /dev/null
@@ -0,0 +1,36 @@
+#!/bin/bash
+
+LOGFILE=$1
+LOGFILE=$(basename $LOGFILE)
+PKG_VER_ARCH=$(basename $LOGFILE .log)
+
+PKG=$(echo $PKG_VER_ARCH | cut -d _ -f1)
+VER=$(echo $PKG_VER_ARCH | cut -d _ -f2)
+ARCH=$(echo $PKG_VER_ARCH | cut -d _ -f3)
+
+TEMPLATE=/scratch/rebuild/buildd-scripts/template.txt
+
+URL="https://www.einval.com/debian/arm/rebuild-logs/$ARCH/FAIL/$LOGFILE"
+
+echo "Build log at $URL"
+
+TMPL=$(tempfile)
+
+cat $TEMPLATE | sed "s,LOG_URL,$URL," > $TMPL
+
+reportbug -b -c -I --no-check-available \
+         --no-debconf --no-bug-script --no-query-bts \
+         -i $TMPL \
+         -P "User: debian-arm@lists.debian.org" \
+         -P "Usertags: alignment" \
+         -S important \
+         -T none \
+         --no-cc-menu \
+         -s "${PKG} ${VER}: FTBFS, alignment problem" \
+         --src --from-buildd=${PKG}_${VER}
+
+# Debug
+#        -d \
+
+
+rm -vf $TMPL
diff --git a/template.txt b/template.txt
new file mode 100644 (file)
index 0000000..5d0ac2e
--- /dev/null
@@ -0,0 +1,24 @@
+Hi!
+
+I've been doing a full rebuild of the Debian archive, building all
+source packages targeting armel and armhf using arm64 hardware. We are
+planning in future to move all of our 32-bit armel/armhf builds to
+using arm64 machines, so this rebuild is to identify packages that
+might have problems with this configuration.
+
+A feature of the arm64 kernel is that it does *not* support fixing up
+code with broken alignment, so code that might have built and run OK
+on our older armel/armhf build machines due to kernel fixups will now
+fail.
+
+When building your package, I've found a bus error (aka alignment
+fault). The full log is online at
+
+  LOG_URL
+
+for reference
+
+I've done a quick bit of debugging to find the source of the
+bug. Here's a gdb stacktrace and variable printout to demonstrate the
+problem.
+