> > if i dont hear anything back withing a week, i'll most likely opening
> > those RM bugs, so that we can work on their transitive dependencies.
>
> Just go ahead. I hope, we can reintroduce Trac in one or two
> years, maybe in time for Debian 12 (bookworm), but probably not
> for Debian 11
Quoting Sandro Tosi :
So Jan 1 arrived, what do you think we should do? i didnt see any
progress on the port to python3 upstream; should we start filing RM
for trac extensions/plugins and once they are gone, RM src:trac?
I don't expect a Python 3 version of Trac before a year from now.
Debian,
Hello Martin,
On Fri, Nov 29, 2019 at 6:55 PM Martin wrote:
>
> On 2019-11-29 18:13, Nicholas D Steeves wrote:
> > IMHO one of the Debian Trac uploaders should post to the #12130 Trac
> > ticket informing them of our plan.
>
> I linked to the email of 2019-10-14:
>
On 2019-11-29 18:13, Nicholas D Steeves wrote:
> IMHO one of the Debian Trac uploaders should post to the #12130 Trac
> ticket informing them of our plan.
I linked to the email of 2019-10-14:
https://trac.edgewall.org/ticket/12130#comment:63
On 2019-11-29 16:24, Sandro Tosi wrote:
> I know it may sound hard, but is it now time to remove trac from
> Debian, and ideally re-introduce it back when it's being ported to
> py3k?
See also:
https://groups.google.com/forum/#!topic/trac-users/5VMI83sbqFs
What would be the alternative?
It would
Hi,
Sandro Tosi writes:
> Hello everyone,
> i'd like to discuss the future of Trac in Debian. as we all know, Trac
> is still python2, and while there are plans to port it to python3
> (https://trac.edgewall.org/ticket/12130) that port is not there yet,
> and it may take quite some time to
Hello everyone,
i'd like to discuss the future of Trac in Debian. as we all know, Trac
is still python2, and while there are plans to port it to python3
(https://trac.edgewall.org/ticket/12130) that port is not there yet,
and it may take quite some time to reach a state it can be tested, let
alone
7 matches
Mail list logo
