Bug#708573: trac-accountmanager: Please remove Python Applications Packaging Team as maintainer
Package: trac-accountmanager Version: 0.4.3-1 Severity: normal Since the package has been removed from the PAPT repository, please remove PAPT as maintainer. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#708573: trac-accountmanager: Please remove Python Applications Packaging Team as maintainer
Quoting "Scott Kitterman" :
Package: trac-accountmanager
...
Since the package has been removed from the PAPT repository, please remove
PAPT as maintainer.
OK, will do.
The same would apply to trac, right?
Daniel (dkg) moved the latest version to collab-maint git.
And python-pyscss ("my" package).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#708573: trac-accountmanager: Please remove Python Applications Packaging Team as maintainer
On Friday, May 17, 2013 02:22:49 PM W. Martin Borgert wrote:
> Quoting "Scott Kitterman" :
> > Package: trac-accountmanager
>
> ...
>
> > Since the package has been removed from the PAPT repository, please remove
> > PAPT as maintainer.
>
> OK, will do.
> The same would apply to trac, right?
> Daniel (dkg) moved the latest version to collab-maint git.
> And python-pyscss ("my" package).
Yes. Use of the team repo for team maintained packages isn't optional.
Thanks,
Scott K
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#708573: trac-accountmanager: Please remove Python Applications Packaging Team as maintainer
On 05/17/2013 08:22 AM, W. Martin Borgert wrote:
> Quoting "Scott Kitterman" :
>> Package: trac-accountmanager
> ...
>> Since the package has been removed from the PAPT repository, please
>> remove
>> PAPT as maintainer.
>
> OK, will do.
> The same would apply to trac, right?
> Daniel (dkg) moved the latest version to collab-maint git.
> And python-pyscss ("my" package).
I would be quite happy to have all these packages stay under PAPT, but i
find i am much more effective at contributing to packaging that uses a
distributed revision control system.
I would be fine moving these packages to a python-apps git repo instead
of collab-maint if people on PAPT prefer that particular location.
Given how straightforward it is to join collab-maint, i also don't have
a problem with leaving PAPT-maintained packages within the collab-maint
umbrella either.
If there is a strong preference from PAPT folks about where
PAPT-maintained git repositories should end up, i haven't heard it, and
i've been trying to follow the mailing list. Is this discussion
happening somewhere else that i should be aware of?
--dkg
signature.asc
Description: OpenPGP digital signature
Bug#708573: trac-accountmanager: Please remove Python Applications Packaging Team as maintainer
On Friday, May 17, 2013 10:53:39 AM Daniel Kahn Gillmor wrote:
> On 05/17/2013 08:22 AM, W. Martin Borgert wrote:
> > Quoting "Scott Kitterman" :
> >> Package: trac-accountmanager
> >
> > ...
> >
> >> Since the package has been removed from the PAPT repository, please
> >> remove
> >> PAPT as maintainer.
> >
> > OK, will do.
> > The same would apply to trac, right?
> > Daniel (dkg) moved the latest version to collab-maint git.
> > And python-pyscss ("my" package).
>
> I would be quite happy to have all these packages stay under PAPT, but i
> find i am much more effective at contributing to packaging that uses a
> distributed revision control system.
>
> I would be fine moving these packages to a python-apps git repo instead
> of collab-maint if people on PAPT prefer that particular location.
> Given how straightforward it is to join collab-maint, i also don't have
> a problem with leaving PAPT-maintained packages within the collab-maint
> umbrella either.
>
> If there is a strong preference from PAPT folks about where
> PAPT-maintained git repositories should end up, i haven't heard it, and
> i've been trying to follow the mailing list. Is this discussion
> happening somewhere else that i should be aware of?
We've been through this a number of times for both PAPT and DPMT. We want a
common repository for each team (not split between different VCSs). There's
been discussion about what would be needed to migrate from SVN to something
else and about what work would need to be done to do that. So far no one has
done the work.
The shorter answer is that there are no PAPT maintained git repositories
because the team uses svn.
Scott K
signature.asc
Description: This is a digitally signed message part.
