Bug#858800: RFS: xtrs/4.9d-1 [ITA]
On Mon, Mar 27, 2017 at 07:11:10PM -0700, Sean Whitton wrote:
> control: tag -1 +moreinfo
>
> Dear Branden,
>
> On Sun, Mar 26, 2017 at 06:45:34PM -0400, Branden Robinson wrote:
> > Changes since the last upload:
> >
> > * Merge new upstream release.
> > + "Deleted all SIGIO code. The code was a kludge to begin with and it no
> > longer worked with current X libraries and Linux kernels, causing xtrs
> > to hang. It was also reported to cause hangs when xtrs was compiled for
> > Windows using Cygwin. Thanks to Howard Pepper, Dennis Lovelady, Arumin
> > Nueckel, Christopher Currie, and Joe Peterson for bug reports."
> > (Closes: #511645)
>
> Is it impossible to backport this fix to the version currently in
> stretch?
No, likely not impossible. The crudest fix might be simply to just
#undef SIGIO in Makefile.local.
I will explore this.
> You are very unlikely to get release team approval for this upload as it
> stands. Given what you wrote in #511645, is your intention for xtrs to
> drop out of stretch, to be reintroduced in buster?
I've been making conservative (pessimistic) estimates about how fast I'd
be getting things done since I'm freshly back to the project after a
long absence. There were and are best practices I need(ed) to get
caught up on. I also couldn't be absolutely sure I'd get a sponsor
before the removal-from-testing date (scheduled for 11 April); I don't
know when I'll be able to get my new GPG key into the Debian keyring so
that I can upload under my own power[1], and so forth. Finally, I don't
want to cause the release team any trouble.
So my goals were, in this order:
1) Get the package suitable for unstable (which it wasn't); then
2) Get the package suitable for testing.
Thanks for following up!
Regards,
Branden
[1] That might take a while; my new key is not in the web of trust.
Reply to: