1 files changed, 0 insertions, 35 deletions

diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/1033.toml b/gitlab/issues/target_missing/host_missing/accel_missing/1033.toml
deleted file mode 100644
index b52246b98..000000000
--- a/gitlab/issues/target_missing/host_missing/accel_missing/1033.toml
+++ /dev/null
@@ -1,35 +0,0 @@
-id = 1033
-title = "fakeroot under qemu fails with 'semop(1): encountered an error: Function not implemented'"
-state = "opened"
-created_at = "2022-05-23T01:09:03.763Z"
-closed_at = "n/a"
-labels = ["linux-user", "workflow::Needs Info"]
-url = "https://gitlab.com/qemu-project/qemu/-/issues/1033"
-host-os = "xubuntu 20.04 (Focal)"
-host-arch = "x86_64"
-qemu-version = "version 7.0.50 (v7.0.0-1171-g3757b0d08b)"
-guest-os = "raspberry pi os bullseye (raspbian)"
-guest-arch = "armv7l"
-description = """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."""
-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 = """- 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)."""