Re: Keeping upstream commits separate from Debian packaging commits

2014-10-12 Thread Thomas Goirand
On 10/10/2014 12:59 PM, Ben Finney wrote: Scott Kitterman deb...@kitterman.com writes: Changing the number of commits is solving the wrong problem. The problem that needs to be solved is including upstream commits. That's thoroughly uninteresting for a packaging team. Agreed. This is a

Re: Keeping upstream commits separate from Debian packaging commits

2014-10-12 Thread Tristan Seligmann
On 12 October 2014 08:49, Thomas Goirand z...@debian.org wrote: Also, during the Debconf discussion, we decided we would use the pristine-tar workflow, *not* using upstream VCS merge. A git-import-orig normally goes into a single commit, which I don't think would bother anyone (not on the

Using pristine-tar (was: Keeping upstream commits separate from Debian packaging commits)

2014-10-12 Thread W. Martin Borgert
On 2014-10-12 14:49, Thomas Goirand wrote: Let's say there's a few more other people which were not accounted for and that were not at Debconf, those who prefers having upstream source code in the VCS are still the majority. And some weren't at Debconf and prefer to work with upstream sources.

Re: Using pristine-tar (was: Keeping upstream commits separate from Debian packaging commits)

2014-10-12 Thread Tristan Seligmann
On 12 October 2014 12:36, W. Martin Borgert deba...@debian.org wrote: Isn't pristine-tar deprecated by its author? I read https://bugs.debian.org/737871 and That's interesting, I didn't know about that. I'm not really sure I understand how dgit replaces pristine-tar, unless you assume that

Bug#764931: ITP: django-assets -- integrate webassets into Django applications

2014-10-12 Thread Michael Fladischer
Package: wnpp Severity: wishlist Owner: Michael Fladischer fladischermich...@fladi.at -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: django-assets Version : 0.10 Upstream Author : Michael Elsdörfer mich...@elsdoerfer.com * URL :

Re: Keeping upstream commits separate from Debian packaging commits

2014-10-12 Thread Scott Kitterman
On October 12, 2014 2:49:47 AM EDT, Thomas Goirand z...@debian.org wrote: On 10/10/2014 12:59 PM, Ben Finney wrote: Scott Kitterman deb...@kitterman.com writes: Changing the number of commits is solving the wrong problem. The problem that needs to be solved is including upstream commits.

Bug#764945: ITP: djangorestframework-nested-resource -- DRF view mixin for nested resources

2014-10-12 Thread Michael Fladischer
Package: wnpp Severity: wishlist Owner: Michael Fladischer fladischermich...@fladi.at -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: djangorestframework-nested-resource Version : 1.2.0 Upstream Author : SimpleEnergy pi...@simpleenergy.com * URL :

Bug#764969: ITP: djangorestframework-gis -- Geographic add-ons for Django REST Framework

2014-10-12 Thread Michael Fladischer
Package: wnpp Severity: wishlist Owner: Michael Fladischer fladischermich...@fladi.at -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: djangorestframework-gis Version : 0.7 Upstream Author : Douglas Meehan dmee...@gmail.com * URL :

Re: Keeping upstream commits separate from Debian packaging commits

2014-10-12 Thread Barry Warsaw
On Oct 12, 2014, at 02:49 PM, Thomas Goirand wrote: Also, during the Debconf discussion, we decided we would use the pristine-tar workflow, *not* using upstream VCS merge. More specifically, as I remember the discussion, it was decided that if upstream uses tarball based releases (as most PyPI

Re: Using pristine-tar (was: Keeping upstream commits separate from Debian packaging commits)

2014-10-12 Thread Barry Warsaw
On Oct 12, 2014, at 01:27 PM, Tristan Seligmann wrote: That's interesting, I didn't know about that. I'm not really sure I understand how dgit replaces pristine-tar, unless you assume that every tarball you want to store is in the archive. (Perhaps that's a reasonable assumption?) And since we

Re: Keeping upstream commits separate from Debian packaging commits

2014-10-12 Thread Barry Warsaw
On Oct 12, 2014, at 11:15 AM, Tristan Seligmann wrote: I wasn't at Debconf, maybe this is why I'm a bit confused by what you wrote here. pristine-tar and upstream VCS merge are in no way mutually exclusive, but you seem to be implying that they are Maybe not mutually exclusive, but what's the

Request to join the team

2014-10-12 Thread debian
Dear all, some of you may have noticed my e-mail about approaching the recent Attempt to unlock mutex that was not locked-issue that several (Python) applications encounter [1]. Anyways, after several years of using Debian --and always returning from straying toward derived distros-- I would like

Re: Using pristine-tar (was: Keeping upstream commits separate from Debian packaging commits)

2014-10-12 Thread Charles Plessy
Le Sun, Oct 12, 2014 at 06:14:19PM -0400, Barry Warsaw a écrit : On Oct 12, 2014, at 01:27 PM, Tristan Seligmann wrote: That's interesting, I didn't know about that. I'm not really sure I understand how dgit replaces pristine-tar, unless you assume that every tarball you want to store is in