Re: Backport of python-lockfile and suggested team maintenance

2017-03-10 Thread Ben Finney
Andreas Tille writes: > In your last mail you agreed that team maintenance would acceptable To clarify: I've not agreed with that. Rather, I've agreed with your position that the practice of a team as maintainer is sensible, and I've said the practice of an individual as maintainer is sensible.

Re: Backport of python-lockfile and suggested team maintenance

2017-03-10 Thread Andreas Tille
Hi Ben, On Thu, Mar 09, 2017 at 11:41:44PM +1100, Ben Finney wrote: > > You decided to use github instead of git.debian.org. > > Is your complaint that the Debian packaging for ‘python-lockfile’ is on > GitHub? This is the first time it's been raised in this thread. May be I messed up with Githu

Re: Backport of python-lockfile and suggested team maintenance

2017-03-09 Thread Ben Finney
My bafflement at the particulars of your complaint have not been resolved, Andreas. I can only think you're confused about ‘python-lockfile’; much of your latest message just doesn't match the facts. Andreas Tille writes: > You decided to use github instead of git.debian.org. Is your complaint

Re: Backport of python-lockfile and suggested team maintenance

2017-03-08 Thread Andreas Tille
Hi Ben, On Wed, Mar 08, 2017 at 03:13:09AM +1100, Ben Finney wrote: > Andreas Tille writes: > > > However, if maintainers decide from deriving what several people > > consider good practice of team maintenance and put extra work on me > > (like creating an extra public repository) I'm not willin

Re: Backport of python-lockfile and suggested team maintenance

2017-03-07 Thread Ben Finney
Andreas Tille writes: > However, if maintainers decide from deriving what several people > consider good practice of team maintenance and put extra work on me > (like creating an extra public repository) I'm not willing to do this. I'm sorry to say that I am not clear on what that sentence means

Re: Backport of python-lockfile and suggested team maintenance

2017-03-06 Thread Andreas Tille
Hi Ben, On Fri, Mar 03, 2017 at 09:50:59PM +1100, Ben Finney wrote: > > Fortunately, Git is a distributed VCS; we can share changes between > repositories with all information preserved. > > If you also publish your repository, you can ‘git request-pull’ to the > package maintainer address and I

Re: Backport of python-lockfile and suggested team maintenance

2017-03-03 Thread Barry Warsaw
On Mar 03, 2017, at 02:03 PM, Thomas Goirand wrote: >Please consider that python-lockfile is considered deprecated upstream, >and only maintained for bugs and security. There's alternative >available, like python-oslo.concurrency. ObPlug: Or flufl.lock, albeit with a different API and other (some

Re: Backport of python-lockfile and suggested team maintenance

2017-03-03 Thread Thomas Goirand
On 03/02/2017 10:52 AM, Andreas Tille wrote: > Hi Ben, > > I just uploaded python-lockfile 0.12.2-2~bpo8+1 to backports since I > need it to backport python-schema-salad. > > I would have loved to commit the changes to some team Git repository but > you are using a repository outside git.debian.o

Re: Backport of python-lockfile and suggested team maintenance

2017-03-03 Thread Ben Finney
Andreas Tille writes: > I would have loved to commit the changes to some team Git repository > but you are using a repository outside git.debian.org. Fortunately, Git is a distributed VCS; we can share changes between repositories with all information preserved. If you also publish your reposit

Backport of python-lockfile and suggested team maintenance

2017-03-02 Thread Andreas Tille
Hi Ben, I just uploaded python-lockfile 0.12.2-2~bpo8+1 to backports since I need it to backport python-schema-salad. I would have loved to commit the changes to some team Git repository but you are using a repository outside git.debian.org. I'd consider it sensible if you would consider maintai