1 files changed, 63 insertions, 0 deletions
diff --git a/results/classifier/105/other/1918975 b/results/classifier/105/other/1918975
new file mode 100644
index 000000000..2cdcb1b42
--- /dev/null
+++ b/results/classifier/105/other/1918975
@@ -0,0 +1,63 @@
+other: 0.919
+instruction: 0.855
+mistranslation: 0.839
+semantic: 0.802
+graphic: 0.767
+socket: 0.673
+network: 0.662
+device: 0.607
+vnc: 0.530
+KVM: 0.481
+boot: 0.478
+assembly: 0.429
+
+[Feature request] Propagate interpreter to spawned processes
+
+I want QEMU user static to propagate interpreter to spawned processes, for instances by adding -R recursive.
+
+I.e. if my program is interpreted by QEMU static than everything what it launches should be interpreted by it, too.
+
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+Also, is this a duplicate of https://bugs.launchpad.net/qemu/+bug/1912107 or do you mean something different here?
+
+Hi,
+
+This is the same bug, child processes from quemu are not quemu. I think I know how this can be fixed, but right now I have no time to even try it.
+
+However use case is a bit different, I don't use binfmtmisc - so I will leave it to your decision, if it's same or not.
+
+I.e. Imagine I run sh with qemu - I want any process launched from sh to be as well qemu interpreted.
+
+I think one ticket should be enough to track this problem, so let's continue the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/306
+