This was a bug in the python-bytecode debian/rules at that point:
40 │ before-pybuild-autopkgtest:
41 │ ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
42 │ ifeq ($(DEB_BUILD_ARCH),armhf)
43 │ patch -p1 < debian/armhf.patch
44 │ endif
45 │ endif
when the ifeq's don't evaluate to true (what happens everywhere but on
armhf), the body of the `before-pybuild-autopkgtest` target is empty,
and this causes make to call the default (%) target, which then calls
`dh`.
This can be reproduced in the following minimal example:
----------------8<----------------8<----------------8<-----------------
$ cat Makefile
───────┬───────────────────────────────────────────────────────────────
│ File: Makefile
───────┼───────────────────────────────────────────────────────────────
1 │ %:
2 │ @echo COMMON: $@
3 │
4 │ foo:
5 │ @echo FOO
6 │
7 │ bar:
───────┴───────────────────────────────────────────────────────────────
$ make foo
FOO
$ make bar
COMMON: bar
----------------8<----------------8<----------------8<-----------------
This could have been fixed at the time by making the patching
unconditional, or by patching the test itself to cause a skip on armhf.