Hi Greg, On 30.04.23 17:09, Greg Troxel wrote:
The version of trac in pkgsrc does not support python 3, and that is of
course increasingly less ok. I no longer use trac, so I don't want to
put a lot of time into testing updates.
There is a 1.5.4 tag upstream, not labeled stable. I have updated to it
locally -- just version/distinfo, changing python version logic, and
PLIST.
There are wip/trac-foo, but those are also aligned to 2.7 and some have
unfetchable distfiles. Formally wip is not considered when maintaining
pkgsrc.
So options are:
A) I just commit this and newer trac is then available for python3, and
might or might not have issues, and anyone who cares can fix it.
B) We decide nobody cares and remove it, and anyone who cares can
re-add it.
C) Somebody who cares speaks up and stages an update in wip and then I
can move it to pkgsrc proper when ready.
D) As C, but also updating wip/trac-*.
I see A as better than B; the drive-by update ought to be mostly ok. So
I'm pruning B. I'm fine with someone doing C and whatever of D
happening or not later.
So this is a call for anyone who wants to take on C or D. If no one
speaks up in 7 days, I'll commit my untested update. If you see an
additional path please feel free to mention it, of course, or anything
else.
Greg
I remember that some (long) time ago I also tried to keep trac up to date in pkgsrc or wip. That was at a time when I still used trac myself. I still find the concept of Trac - the unmatched integration of wiki and bug tracker - very interesting and would be happy if Trac survives. On the other hand, I have to admit that waiting for a stable and supportable version on Python 3 has also led me to rely on alternatives like Redmine and MantisBT/Dokuwiki. So I'm out as a maintainer for Trac, because I think it's important that you use it actively yourself if you want to do it well.
Kind regards Matthias
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature