Re: lintian and team uploads
On Tuesday, September 29, 2015 10:31:23 PM Julien Puydt wrote: > Le mardi 29 sept. 2015 à 15:51:44 (-0400), Barry Warsaw a écrit : > > On Sep 29, 2015, at 09:46 PM, Piotr Ożarowski wrote: > > >(and remember to remove DPMT from debian/control if it's not in SVN ;P) > > > > Given that the final git migration is imminent (really! otherwise I'm > > going to scream ;), can we not force people to go through this churn > > right now? > Indeed, I find that offensive : if git is a better tool than subversion, > and if it's going to be used, what's the point? > > > Yes, let's discourage any new packages from manually migrating or starting > > out in git just until flag day. But I'm not sure it's worth removing > > DPMT on existing repos just to add it back, hopefully RSN. > > I would like to make some points clear: > 1. I wouldn't have contributed a single package in subversion, as it's just > too cumbersome to use. I liked svn when it replaced cvs, but not so much > since I started using git. > 2. When I saw the DPMT policy mentioned only subversion, I asked around > (can't remember if it was just on IRC or on this ml) and was told it was ok > to use git since the migration was bound to happen sooner or later. > 3. Afterwards, being just a DM, I sent RFS mails through this very list in > which I generally gave the Vcs-* fields from the d/control files, which > clearly showed I used git : no complaint about it. > 4. Those package got sponsored without complaint about it either. > > So you'll understand that getting flames (even with smileys) about it > now is quite annoying. > > I still have a series of things I plan to package for Debian ; those are > Python Modules, and I'll use git. If that's a problem for the Debian > Python Modules Team, can you point me to a more appropriate team? Just chill out and have a little patience. What VCS gets used just doesn't make that much different for most things we need to do. If you can't bring yourself to commit to svn, then just have a bit of patience. Scott K
Re: lintian and team uploads
On Tuesday, September 29, 2015 04:48:09 PM Barry Warsaw wrote: > On Sep 29, 2015, at 10:31 PM, Julien Puydt wrote: > >I still have a series of things I plan to package for Debian ; those are > >Python Modules, and I'll use git. If that's a problem for the Debian > >Python Modules Team, can you point me to a more appropriate team? > > This illustrates my concern. We've already had defections from the team > because of the prohibition against git. Once gone from the team, it will be > difficult to bring them back into the fold. I would like to be creating > *more* collaboration, not less, otherwise, what's the point of having a > team? We don't have a prohibition against git. We have a prohibition against using multiple repositories. Once we switch to git, it'll be svn gets prohibited. The thing that needs doing is whatever's blocking you and tumbleweed from pulling the trigger on the migration. Scott K
Re: lintian and team uploads
On Sep 29, 2015, at 10:31 PM, Julien Puydt wrote: >I still have a series of things I plan to package for Debian ; those are >Python Modules, and I'll use git. If that's a problem for the Debian >Python Modules Team, can you point me to a more appropriate team? This illustrates my concern. We've already had defections from the team because of the prohibition against git. Once gone from the team, it will be difficult to bring them back into the fold. I would like to be creating *more* collaboration, not less, otherwise, what's the point of having a team? Cheers, -Barry
Re: lintian and team uploads
Le mardi 29 sept. 2015 à 15:51:44 (-0400), Barry Warsaw a écrit : > On Sep 29, 2015, at 09:46 PM, Piotr Ożarowski wrote: > > >(and remember to remove DPMT from debian/control if it's not in SVN ;P) > > Given that the final git migration is imminent (really! otherwise I'm going to > scream ;), can we not force people to go through this churn right now? Indeed, I find that offensive : if git is a better tool than subversion, and if it's going to be used, what's the point? > Yes, let's discourage any new packages from manually migrating or starting out > in git just until flag day. But I'm not sure it's worth removing DPMT on > existing repos just to add it back, hopefully RSN. I would like to make some points clear: 1. I wouldn't have contributed a single package in subversion, as it's just too cumbersome to use. I liked svn when it replaced cvs, but not so much since I started using git. 2. When I saw the DPMT policy mentioned only subversion, I asked around (can't remember if it was just on IRC or on this ml) and was told it was ok to use git since the migration was bound to happen sooner or later. 3. Afterwards, being just a DM, I sent RFS mails through this very list in which I generally gave the Vcs-* fields from the d/control files, which clearly showed I used git : no complaint about it. 4. Those package got sponsored without complaint about it either. So you'll understand that getting flames (even with smileys) about it now is quite annoying. I still have a series of things I plan to package for Debian ; those are Python Modules, and I'll use git. If that's a problem for the Debian Python Modules Team, can you point me to a more appropriate team? Snark on #debian-python
Re: lintian and team uploads
On Sep 29, 2015, at 09:46 PM, Piotr Ożarowski wrote: >(and remember to remove DPMT from debian/control if it's not in SVN ;P) Given that the final git migration is imminent (really! otherwise I'm going to scream ;), can we not force people to go through this churn right now? Yes, let's discourage any new packages from manually migrating or starting out in git just until flag day. But I'm not sure it's worth removing DPMT on existing repos just to add it back, hopefully RSN. Cheers, -Barry
