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 cand
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 stretch?
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 st
* 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
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
5 matches
Mail list logo
