1 files changed, 57 insertions, 0 deletions
diff --git a/results/classifier/118/device/1033 b/results/classifier/118/device/1033
new file mode 100644
index 000000000..96229de66
--- /dev/null
+++ b/results/classifier/118/device/1033
@@ -0,0 +1,57 @@
+architecture: 0.972
+device: 0.962
+graphic: 0.936
+semantic: 0.894
+debug: 0.835
+PID: 0.807
+arm: 0.780
+ppc: 0.765
+user-level: 0.689
+performance: 0.681
+peripherals: 0.616
+register: 0.604
+network: 0.590
+risc-v: 0.568
+kernel: 0.515
+files: 0.492
+mistranslation: 0.449
+vnc: 0.435
+hypervisor: 0.423
+permissions: 0.410
+socket: 0.386
+VMM: 0.298
+virtual: 0.294
+i386: 0.246
+x86: 0.205
+boot: 0.199
+TCG: 0.186
+assembly: 0.138
+KVM: 0.044
+
+fakeroot under qemu fails with 'semop(1): encountered an error: Function not implemented'
+Description of problem:
+Appears to be the same issue as that discussed and reportedly fixed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965109
+
+Running raspberry pi os in a chroot (using schroot). Execution of fakeroot as part of dpkg-buildpackage results in:
+
+```
+dpkg-buildpackage: info: source package clementine
+dpkg-buildpackage: info: source version 1.4.0rc1-836-g4665916ba~bullseye
+dpkg-buildpackage: info: source distribution bullseye
+dpkg-buildpackage: info: source changed by David Sansome <me@davidsansome.com>
+dpkg-buildpackage: info: host architecture armhf
+ dpkg-source --before-build .
+ fakeroot debian/rules clean
+semop(1): encountered an error: Function not implemented
+dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 1
+```
+
+This is the same error as reported in bug 965109, but I'm running the most recent version of qemu - I built it from the git repo, so it should include the fix for 965109.
+Steps to reproduce:
+1. Setup (s)chroot with arm architecture (although the architecture may not matter) 
+2. Run fakeroot in the chroot
+3. Observe the failure related to the semop syscall
+Additional information:
+- Not sure what other information I can provide to be helpful.
+- The command line listed above is what I gather from ps; it's how qemu-arm-static is called by schroot. I've not been able to figure out _how_ schroot calls qemu-arm-static, I only know it does.
+- I compiled qemu from source using my own user id, and ran into an issue with make install, so I manually used install to deploy the executable to /usr/local/bin... And then had to symlink that to /usr/bin as schroot apparently hardcodes the location of qemu-arm-static (at least it did not pick up the version I'd placed in /usr/local/bin).