Bug#851841: xonsh: jobs and backgrounding broken

As noted above, the bug severity was upgraded too late to stop 0.5.2 migrating. There have been a series of releases since, and while this bug was mostly fixed in 0.5.3 it appears there were still some edge cases. The code is still fairly fast moving, and in the end I don't think it's a good

Bug#851841: xonsh: jobs and backgrounding broken

On Thu, 19 Jan 2017 22:14:25 +0100 Gordon Ball wrote: > I have upgraded the bug to severity:serious to prevent migration, so > stretch will get 0.4.7 It looks like stretch currently lacks xonsh at all, be it 0.4.7, broken 0.5.2 or recent 0.5.6. Will any xonsh get into

Bug#851841: xonsh: jobs and backgrounding broken

Apparently I was too slow. It migrated only about an hour after I increased the severity, which was too late for the RC bug to be considered. Given the proximity to the freeze, I'm tempted to allow xonsh to be removed from testing and provide a backport in due course when the current branch has

Bug#851841: xonsh: jobs and backgrounding broken

* Gordon Ball [170123 00:23]: > I have upgraded the bug to severity:serious to prevent migration, so > stretch will get 0.4.7 and unstable will be updated when patches for 0.5 > are available. That clearly did not work. 0.5.2+dfsg-1 is now in stretch. -ch

Bug#851841: xonsh: jobs and backgrounding broken

Thanks for reporting. I think I have to agree. I pushed the 0.5 series when it was released thinking it would be a better base if patching was required in future, but there do appear to be too many bugs which cannot be patched at the moment. I have upgraded the bug to severity:serious to prevent

Bug#851841: xonsh: jobs and backgrounding broken

Package: xonsh Version: 0.5.2+dfsg-1 Severity: important Hi, This is about https://github.com/xonsh/xonsh/issues/2071 >From a comment in there: I think there are two separate issues here (that I've noticed). One is that backgrounding doesn't seem to work (the big issue). The other is that