[Calypso] [Calypso-maint] calypso is marked for autoremoval from testing
jelmer at jelmer.uk
Thu Dec 8 05:30:45 PST 2016
On Thu, Dec 08, 2016 at 09:21:26AM +0100, Guido Günther wrote:
> On Thu, Dec 08, 2016 at 02:29:19AM +0000, Jelmer Vernooĳ wrote:
> > On Sat, Nov 19, 2016 at 04:39:08AM +0000, Debian testing autoremoval watch wrote:
> > > calypso 1.5-3 is marked for autoremoval from testing on 2016-12-18
> > >
> > > It (build-)depends on packages with these RC bugs:
> > > 841247: python-vobject: Unicode handling broken in 0.9.x with python 2.7
> > It looks like ENCODING handling has been fixed upstream, but they've
> > kept the change in behaviour - using unicode strings in its API
> > everywhere rather than bytestrings.
> > https://github.com/eventable/vobject/issues/51
> > It's not just calypso that depends on vobject though, but also triton
> > and some other packages. I'll see if I can patch the bytestring
> > support back in..
> Other packages don't seem to have issues and since it seems upstream
> wants to stick to internal unicode I wonder if we should change calypso?
> If we do so we could probably do the switch to python3 altogether.
> I have looking into this on my TODO list (and it slowly bubbles up) but
> if you can have a look sooner that's great. I'll ping once I start
> working on it.
If nobody else is affected, moving calypso to unicode seems
I feel a bit uneasy porting calypso to Python3 this late in the
release cycle for stretch considering there are no unit tests for it.
It seems likely it'll take a couple of weeks for the porting to happen,
we'll probably miss some python2isms and then not discover them before
the release happens.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: not available
More information about the Calypso