The Debian packaging of emacs-buttercup is maintained in git, using
the merging workflow described in dgit-maint-merge(7).  There isn't a
patch queue that can be represented as a quilt series.

A detailed breakdown of the changes is available from their canonical
representation - git commits in the packaging repository.  For
example, to see the changes made by the Debian maintainer in the first
upload of upstream version 1.2.3, you could use:

    % git clone https://git.dgit.debian.org/emacs-buttercup
    % cd emacs-buttercup
    % git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian'

(If you have dgit, use `dgit clone emacs-buttercup`, rather than plain
`git clone`.)

A single combined diff, containing all the changes, follows.
--- emacs-buttercup-1.26.orig/Makefile
+++ emacs-buttercup-1.26/Makefile
@@ -1,7 +1,7 @@
 EMACS := emacs
 VERSION := $(shell sed -ne 's/^;; Version: \(.*\)/\1/p' buttercup.el)
 ELISP_FILES := $(wildcard *.el)
-
+TEMP_DIR := $(shell mktemp -d /tmp/butterdocXXXXXX)
 .PHONY: test compile clean
 
 all: test
@@ -12,7 +12,8 @@ check-buttercup test-buttercup: compile
 	./bin/buttercup -L . tests $(if $(CI),--traceback pretty)
 
 check-docs test-docs: compile
-	$(EMACS) -batch -L . -l buttercup.el -f buttercup-run-markdown docs/writing-tests.md
+	$(EMACS) -batch -L . --eval "(setq native-compile-target-directory \"${TEMP_DIR}\")" -l buttercup.el -f buttercup-run-markdown docs/writing-tests.md
+	rm -r ${TEMP_DIR}
 
 compile: $(patsubst %.el,%.elc,$(ELISP_FILES))
 
--- emacs-buttercup-1.26.orig/README.md
+++ emacs-buttercup-1.26/README.md
@@ -1,10 +1,5 @@
 # Buttercup — Behavior-Driven Emacs Lisp Testing
 
-[![Build and test](https://github.com/jorgenschaefer/emacs-buttercup/workflows/Build%20and%20test/badge.svg)](https://github.com/jorgenschaefer/emacs-buttercup/actions?query=workflow%3A%22Build+and+test%22+branch%3Amaster)
-[![MELPA Stable](http://stable.melpa.org/packages/buttercup-badge.svg)](http://stable.melpa.org/#/buttercup)
-
-![Ranculus repens, photo by sannse](docs/images/buttercup.jpg)
-
 Buttercup is a behavior-driven development framework for testing Emacs
 Lisp code. It allows to group related tests so they can share common
 set-up and tear-down code, and allows the programmer to “spy” on
@@ -16,7 +11,7 @@ The framework is heavily inspired by
 
 ## Example
 
-*Full article: [Writing Tests](docs/writing-tests.md)*
+*Full article: [Writing Tests](writing-tests.md)*
 
 A simple test looks like this.
 
@@ -26,26 +21,11 @@ A simple test looks like this.
     (expect t :to-be t)))
 ```
 
-## Installation and Usage
-
-*Full article: [Running Tests](docs/running-tests.md)*
-
-You can install buttercup from
-[MELPA Stable](http://stable.melpa.org/). Add the following to your
-`init.el` or `.emacs` file:
-
-```
-(require 'package)
-(add-to-list 'package-archives
-             '("melpa-stable" . "http://stable.melpa.org/packages/") t)
-```
-
-This should allow you to `M-x package-install RET buttercup RET`.
+## Usage
 
-Alternatively, users of Debian 9 or later or Ubuntu 16.10 or later may
-simply `apt-get install elpa-buttercup`.
+*Full article: [Running Tests](running-tests.md)*
 
-Now create a file called `test-feature.el` with these contents:
+Create a file called `test-feature.el` with these contents:
 
 ```Lisp
 (describe "A suite"
--- emacs-buttercup-1.26.orig/bin/buttercup
+++ emacs-buttercup-1.26/bin/buttercup
@@ -102,8 +102,14 @@ do
     esac
 done
 
+tempdir=$(mktemp -d /tmp/buttercupXXXXXX)
+cleanup () {
+    rm -rf $tempdir
+}
+trap cleanup EXIT
+
 # `--' is needed so that Buttercup options don't get parsed by Emacs itself.
-exec "$EMACS_BIN" -batch "${EMACS_ARGS[@]}" -l buttercup -f buttercup-run-discover -- "${BUTTERCUP_ARGS[@]}"
+"$EMACS_BIN" -batch "${EMACS_ARGS[@]}" --eval "(setq native-compile-target-directory \"$tmpdir\")" -l buttercup -f buttercup-run-discover -- "${BUTTERCUP_ARGS[@]}"
 
 # Local Variables:
 # indent-tabs-mode: nil
