Re: DPMT membership request

[Felix Krull, 2016-08-08] > I'd like to join the DPMT to maintain quark-sphinx-theme (ITP at [1]) > which is going to be needed as a build dependency for the next > SpeedCrunch version [2]. > > I have read the policy [3] and accept it. My Alioth login is fkrull-guest. welcome :) -- Piotr

Re: Request to join DPMT

[Tobias Hansen, 2016-08-10] > I would like to join the team to help maintain Python modules that are > dependencies of SageMath (at the moment, I'd like to update pexpect to > the new upstream version). > > My alioth login is thansen. > > I have read

Re: Acceptance of team policy

[Dominik George, 2016-08-10] > of course, I have read and accept the DPMT policy. > > I have also already workde with gbp in the way described in the policy. welcome in the team :) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc

Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was: PAPT Git)

On Aug 10, 2016, at 08:49 PM, Brian May wrote: >Most of the time it works pretty well... It looked good compared with >the alternatives available at the time we made the decision. > >However this is irrelevant IMHO if it isn't being mantained. Yep. git-dpm was the best of breed at the time we

Request to join DPMT

Dear DPMT, I would like to join the team to help maintain Python modules that are dependencies of SageMath (at the moment, I'd like to update pexpect to the new upstream version). My alioth login is thansen. I have read https://python-modules.alioth.debian.org/policy.html and accept it.

Re: using git-dpm or plain git-buildpackage in PAPT and DPMT

On Aug 10 2016, Thomas Goirand wrote: > As I only heard complains about git-dpm, maybe someone would like to > express his joy using it, and explain why they think it's a nice tool. > But is there such person? It seems git-dpm only brings frustration. In my opinion, git-dpm

Re: using git-dpm or plain git-buildpackage in PAPT and DPMT

On Wed, 10 Aug 2016, Nikolaus Rath wrote: > I don't believe that switching from git-dpm to git-buildpackage is going > to make things easier, it'll just be trading one set of problems for > another. I don't agree on this. I have been a happy git-buildpackage user for all my packages. The problem

Re: using git-dpm or plain git-buildpackage in PAPT and DPMT

On Aug 10, 2016, at 11:53 AM, Nikolaus Rath wrote: >I think the only way to make this less painful is to get rid of the idea >of managing patches in a VCS and use something like gitpkg. This has the >drawback source package is now *generated* from the Git repository >(i.e., you can't do git clone

Re: PAPT Git (was: pypi2deb 1.20160809 and --profile dpmt)

On Tue, Aug 9, 2016 at 11:50 PM, W. Martin Borgert wrote: > On 2016-08-09 23:28, Daniel Stender wrote: >> On this occasion ... let it be me to start the discussion: let's get into Git >> also for Python Apps soon. > > A common VCS for both DPMT and PAPT would be nice, indeed.

Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was: PAPT Git)

On 08/10/2016 09:21 AM, Sandro Tosi wrote: > On Tue, Aug 9, 2016 at 11:50 PM, W. Martin Borgert wrote: >> On 2016-08-09 23:28, Daniel Stender wrote: >>> On this occasion ... let it be me to start the discussion: let's get into >>> Git >>> also for Python Apps soon. >> >> A

Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was: PAPT Git)

On 2016-08-10 10:18, Thomas Goirand wrote: > Instead of > accepting the merge, and resolving conflicts later on, git-dpm goes into > the rebase conflict mode of Git, and it's often not obvious what to do > there. Messing-up everything, and restart from scratch (and then iterate > until done

Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was: PAPT Git)

Thomas Goirand writes: > git-dpm also fails to tag upstream/foo automatically when importing a > new version. I've been told to use "git-dpm tag", but that's not > obvious. My own experience managing debian/patches quilt patches > manually or through gbp pq is actually much much

Re: Maintenance of new Flask extensions

[Dominik George, 2016-08-10] > > https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin > > I have tried to request team membership, and found that I already requested > that (probably some years ago) and the request is still pending. I don't know how to disable these join request on

Re: PAPT Git

[Sandro Tosi, 2016-08-10] > should we try and use plain git-buildpackage instead of git-dpm? the plan is to test something else (git-pq), yes (and maybe even later replace git-dpm with it in DPMT if it proves to be better) -- Piotr Ożarowski Debian GNU/Linux Developer

Acceptance of team policy

Hi, of course, I have read and accept the DPMT policy. I have also already workde with gbp in the way described in the policy. Cheers, Nik -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Mobil: +49-1520-1981389 Teckids e.V. · FrOSCon e.V. ·

Re: using git-dpm or plain git-buildpackage in PAPT and DPMT

On Wed, 10 Aug 2016 at 16:41:40 -0400, Barry Warsaw wrote: > * With git-dpm we *had* to enforce the tool choice because git-dpm's artifacts > had to be preserved. If we ditch git-dpm, is that still the case? IOW, if > you choose to use gbp-pq, am I forced to do so when I modify the same repo?

Re: Maintenance of new Flask extensions

Hi Ondrej, > I'm Flask Debian packaging maintainer. Not much to do with packaging, but > help is always welcome. > > > I would initially like to add these two extensions: > > Flask-Restless > > Flask-Compress > > Flask-LDAPConn > > go ahead and pack it under DPMT. Alright, thanks! > >

Bug#833920: ITP: flask-restless -- Flask extension which provides simple generation of ReSTful JSON APIs

Package: wnpp Severity: wishlist Owner: Dominik George -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: flask-restless Version : 1.0.0b1 Upstream Author : Jeffrey Finkelstein * URL : https://github.com/jfinkels/flask-restless *

Bug#833921: ITP: flask-compress -- Compress responses in your Flask app with gzip

Package: wnpp Severity: wishlist Owner: Dominik George -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: flask-compress Version : 1.3.0 Upstream Author : William Fagan * URL : https://github.com/wichitacode/flask-compress * License

Bug#833922: ITP: flask-ldapconn -- LDAP connection and ORM for Flask Applications

Package: wnpp Severity: wishlist Owner: Dominik George -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: flask-ldapconn Version : 0.6.13 Upstream Author : Rafael Römhild * URL : http://github.com/rroemhild/flask-ldapconn * License