On Sat, Apr 28, 2012 at 21:36, Jakub Wilk <jw...@debian.org> wrote: > * Russ Allbery <r...@debian.org>, 2012-04-27, 20:20: >> Stefano Zacchiroli <lea...@debian.org> writes: > [...] >>> >>> Considering the potential incompatibilities, it seems that the possible >>> maintenance "teams" boil down to: >>> >>> - a maintenance team formed by Sandro >>> - a maintenance team formed by Matthias and Barry > > Did Matthias even express his willingness to collaborate with Barry?
Or, from the other side, what's preventing Barry to collaborate with Matthias *right now*, without waiting? I can't find signs of any Barry's contributions in the Debian changelogs for Python interpreters or -defaults packages (but there was some minor fixups in Ubuntu in the past). Since we are at it, there are recurring problems reappearing: - python2.6 removal willingness was only reported to debian-release [1] (opinionatedly late in the development process) without any collaboration/coordination (request) with python modules/apps team. - python2.7 (a security-fix release, which is outdated since 20 days, like python3.2, while Ubuntu had them uploaded even before the official availability announce[2]) is keeping FTBFS in mips while on GNU/kFreeBSD was fixed by a NMU helping those archs catching up, as confirmed by release team on irc. [1] http://lists.debian.org/debian-release/2012/04/msg00218.html [2] http://mail.python.org/pipermail/python-announce-list/2012-April/009420.html History repeating? -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
