Hi Thomas,

On Tue, 15 Oct 2019, Thomas Goirand wrote:
> It's been nearly a month that the calibre package is in this shape, ie
> not converted to Python 3. Besides this:

Wrong. If you could step down from your github hate line, you could
check the experimental branch of the debian calibre package, which 
already is prepared for Python3.
        export CALIBRE_PY3_PORT=1
        SETUP=python3 setup.py
and it actually works. The only problem (AFAIS) at the moment are
- libqt is too old in Debian (5.12 has been released long ago)
- all the plugins will be broken.

> How is this a lie? There's no FUD either, just facts. There's also this,

Besides, that you never checked the facts, right? Have you build Calibre
once? have you tried to do it with Python3? You just rely on hearsay and
old bug reports. Very impressive.

> I don't see any sign that the upstream author has changed his mind, and
> is willing to do the work of moving to Python 3. Or has this changed? If

Yes it has, and looking (sorry, again your behated) at his github you
would have seen that there is considerable P3 conversion going on for
**months** now.

> so, please point to some upstream commit showing there's ongoing work.
> Then you'll be able to tell me I was *mistaking* (and not lying).

What about looking at
https://github.com/kovidgoyal/calibre/commits/master ??? I assume you
are able to understand commit messages like
        py3 compat
        Avoid error on python3 about str and bytes
        Fix failing test on py3
        py3 porting
etc etc etc.

> > Lie:
> >> to, this wont help. Doing BTS ping-pong wont help either.
> 
> I completely fail to see where the lie is... You've downgraded the
> severity for your package to normal, cloned it to cherrypy3 where you've
> set the severity to serious. That's BTS ping-pong to me. Or did I miss
> something?

No. Ping-pong would have been if I have re-downgraded after it was
raised recently. I accept the explanation of the recent raising of
severity, but my initial downgrade is completely in the authority
of the package maintainer.

So if you consider one time adjustment of severity a "ping-pong", then
about every maintainer here in Debian would play your so called
"ping-pong" game.

So please, stop calling out such things without providing reason.

> In any case, CC-ing the community team is a good idea, especially when
> gratuitously calling me a liar publicly.

Not gratuitously, not at all.

So please stop spreading FUD again and again, I am sick of it.
In your email you again spread lies like
        It's been nearly a month that the calibre package is in
        this shape, ie not converted to Python 3
and
        I don't see any sign that the upstream author has changed his mind, and
        is willing to do the work of moving to Python 3. Or has this changed? If
These kind of statements are the reason that upstream communication are
getting difficult. I have worked hard to get good communication with
upstream, and your unfounded statements, without even the slightest
trial to verify your statements are painful at best.

Before posting fake statements, please check the facts, they are public
in the git repositories.

Best

Norbert

--
PREINING Norbert                               http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Reply via email to