Hi,
Le 16/10/2015 20:48, Julien Puydt a écrit :
I'm looking for a sponsor for my package:
* Package name:pickleshare
Version: 0.5
Upstream author: Ville Vainio
* URL: https://github.com/pickleshare/pickleshare
* License: Expat
Progr. lang.:Python
Hi,
Le 23/10/2015 00:46, Brian May a écrit :
Package: wnpp
Severity: wishlist
Owner: Brian May
* Package name: python-setuptools-scm
Version : 1.8.0
Upstream Author : Ronny Pfannschmidt
* URL : https://github.com/pypa/setuptools_scm/
* License : MIT
Pro
On Oct 22, 2015, at 09:09 AM, Raphael Hertzog wrote:
>Yeah :( That makes another point that was missed in the evaluation of
>git-dpm vs git-buildpackage and its "gpb pq" command.
When we started down this road, `gbp pq` was pretty unusable and git-dpm was
much better (IMHO, others who did provide
On Oct 22, 2015, at 01:04 PM, W. Martin Borgert wrote:
>So far, it just seems to work for (most of?) us.
Yep, pretty much.
Cheers,
-Barry
On Oct 22, 2015, at 11:11 AM, IOhannes m zmölnig (Debian/GNU) wrote:
>something else i wonder whether we shouldn't drop it, as i don't quite
>understand why it has to be in the policy.
>
>i *think* it's supposed to urge DDs into becoming team members, even though
>they can ("are able to") already
On Oct 22, 2015, at 11:14 AM, IOhannes m zmölnig (Debian/GNU) wrote:
>thanks for gender neutral wording. however, you missed one "his" in the
>first sentence (probably more in other paragraphs).
Got it, thanks.
-Barry
pgpm4DkniheG1.pgp
Description: OpenPGP digital signature
Package: wnpp
Severity: wishlist
Owner: Brian May
* Package name: python-setuptools-scm
Version : 1.8.0
Upstream Author : Ronny Pfannschmidt
* URL : https://github.com/pypa/setuptools_scm/
* License : MIT
Programming Lang: Python 2 and Python 3
Description
Package: wnpp
Severity: wishlist
Owner: Brian May
* Package name: pytest-django
Version : 2.9.1
Upstream Author : Andreas Pelme
* URL : https://github.com/pytest-dev/pytest-django
* License : BSD
Programming Lang: Python 2 and Python 3
Description : Tes
On 10/22/2015 05:34 PM, Jeremy Lainé wrote:
> Hi all,
>
> I had not followed the transition to git too closely and had assumed the
> new repos were to be managed with git-buildpackage. So I imported a new
> upstream version of python-netfilter using git-buildpackage, only to
> realise I am supposed
Hi all,
I had not followed the transition to git too closely and had assumed the
new repos were to be managed with git-buildpackage. So I imported a new
upstream version of python-netfilter using git-buildpackage, only to
realise I am supposed to use git-dpm. Now my repo is in a state which
git-dp
Cześć Piotr,
I found this thread while trying to update the Debian packaging
for a Python library that I maintain. The library has Sphinx
documentation that is quite complex to build: First, the library
needs to be built (it contains C extensions), then figures are
generated by scripts, and
Quoting Julien Puydt :
Do you know pristine-tar is orphaned ? (bug #737871)
This is known to readers of this mailing list, e.g.
https://lists.debian.org/debian-python/2014/10/msg00039.html
So far, it just seems to work for (most of?) us.
Cheers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2015-10-22 11:30, Piotr Ożarowski wrote:
>> i have to admit i'm not totally used to an reviewing git patches
>> per mailinglists, and in this case i got lost a little bit what
>> the current draft is. would it be possible to put a complete
>> draf
> i have to admit i'm not totally used to an reviewing git patches per
> mailinglists, and in this case i got lost a little bit what the
> current draft is.
> would it be possible to put a complete draft online somewhere (maybe
> even as an r/o git), in addition to posting the patches on the ml.
g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2015-10-21 15:54, Barry Warsaw wrote:
> Hopefully, the latest changes (see previous follow up) are both
> more concise and coherent.
maybe.
i have to admit i'm not totally used to an reviewing git patches per
mailinglists, and in this case i got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2015-10-20 22:53, Barry Warsaw wrote:
> +Any·Debian·developer·who·wishes·to·integrate·his·packages·in·the·team
·can·do
>
>
+so·without·requesting·access·(as·the·repository·is·writable·by·all·DD).
·If·one
> wants·to·be·more·involved·in·the·team,·w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2015-10-20 22:53, Barry Warsaw wrote:
> +Any·Debian·developer·who·wishes·to·integrate·his·packages·in·the·team
·can·do
>
>
+so·without·requesting·access·(as·the·repository·is·writable·by·all·DD).
·If·one
> wants·to·be·more·involved·in·the·team,·w
Sandro Tosi writes:
> On Wed, Oct 21, 2015 at 11:01 PM, Brian May wrote:
>> Maybe we should fix #801666 first and then revisit this question?
>
> git-dpm hasnt seen a single line changed since more than a year
> (http://anonscm.debian.org/cgit/git-dpm/git-dpm.git/) so I wont hold
> my breath on
you guys had plenty of time to propose something else, you stil have,
it's easy: just do the work which was done for git-dpm migration
If you just want to whine, then SHUT UP or go fix git-dpm or
pristine-tar instead!
It's not democracy, it's DOocracy so spend your time on
reporting bugs or provi
Le mercredi 21 oct. 2015 à 23:28:47 (+0100), Sandro Tosi a écrit :
> On Wed, Oct 21, 2015 at 11:01 PM, Brian May wrote:
> > Maybe we should fix #801666 first and then revisit this question?
>
> git-dpm hasnt seen a single line changed since more than a year
> (http://anonscm.debian.org/cgit/git-d
On Wed, 21 Oct 2015, Sandro Tosi wrote:
> On Wed, Oct 21, 2015 at 11:01 PM, Brian May wrote:
> > Maybe we should fix #801666 first and then revisit this question?
>
> git-dpm hasnt seen a single line changed since more than a year
> (http://anonscm.debian.org/cgit/git-dpm/git-dpm.git/) so I wont
21 matches
Mail list logo
