-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
One more doubt. Where are new packages uploaded to in Python Modules
Team? Is there a git repo or should I upload to Debian Mentors? I am
asking this because, in Ruby team, the uploads usually happen to the
git repos created inside pkg-ruby-extra
W dniu 31.03.2015 o 09:44, Balasankar C pisze:
Hi,
One more doubt. Where are new packages uploaded to in Python Modules
Team? Is there a git repo or should I upload to Debian Mentors? I am
asking this because, in Ruby team, the uploads usually happen to the
git repos created inside pkg-ruby-ex
On 31/03/15 09:44, Balasankar C wrote:
Hi,
One more doubt. Where are new packages uploaded to in Python Modules
Team? Is there a git repo or should I upload to Debian Mentors? I am
asking this because, in Ruby team, the uploads usually happen to the
git repos created inside pkg-ruby-extras folder
2015-03-30 20:50 GMT+01:00 Adrien Clerc :
> Le 30/03/2015 20:50, Ghislain Vaillant a écrit :
>
> Package: wnpp
> Severity: wishlist
> Owner: Ghislain Antony Vaillant
>
> * Package name: bitstring
> Version : 3.1.3
> Upstream Author : Scott Griffiths
> * URL : https:/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
> The repos creation would be (with an alioth account in the team
> project)
>
> ssh git.debian.org cd /git/python-modules ./setup-repository
> 'python-wget' 'python-wget packaging'
Thanks for the detailed instructions. I believe it is ok if I
Hi Guys,
I have a package I'm working on which makes use of aiohttp and was
wondering what the plans were for the python3-aiohttp package in Debian?
I can't find an ITP/RFP bug for the package, but see that there are some
files already in SVN.
Please cc me in any replies as I'm not subscribed to
On Mar 31, 2015, at 01:14 PM, Balasankar C wrote:
>One more doubt. Where are new packages uploaded to in Python Modules
>Team? Is there a git repo or should I upload to Debian Mentors?
The team still officially supports only Subversion, but we have been
experimenting with switching to git.
https
Barry the import script looks pretty cool.
Any chance to package it and bless it as the official conversion script?
Best regards
ZK
On Tue, Mar 31, 2015 at 3:57 PM, Barry Warsaw wrote:
> On Mar 31, 2015, at 01:14 PM, Balasankar C wrote:
>
>>One more doubt. Where are new packages uploaded to in
On Mar 31, 2015, at 04:04 PM, Zygmunt Krynicki wrote:
>Barry the import script looks pretty cool.
Thanks!
>Any chance to package it and bless it as the official conversion script?
Either that or donate it to the git-dpm project. Either way is cool with me,
though I'd love for it to get more te
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Barry,
> * Do we adopt git-dpm or something else?
I saw a mention about inter-operability of git-dpm and git-bp in the
link you provided[1]. What is the current status of this
inter-operability? Are there any roadblocks for the same?
AFAIK, both
Breaking from another thread
On 31/03/15 15:57, Barry Warsaw wrote:
The team still officially supports only Subversion, but we have been
experimenting with switching to git.
https://wiki.debian.org/Python/GitPackaging
I personally favor and advocate git-dpm, but this has not yet been decided b
On 31 March 2015 at 07:24, Daniel Lintott wrote:
> I can't find an ITP/RFP bug for the package, but see that there are some
> files already in SVN.
I was packaging it originally for something paultag was working on,
but he no longer needed it so I didn't finish (and it felt like a
waste to just p
On Mar 31, 2015, at 04:48 PM, Antoine Musso wrote:
>I have only been introduced to git-buildpackage and using Jenkins to more or
>less automatically build them when proposing a patch or a change is merged.
Really, git-dpm is just the patch manager. There are a few others, but I
found git-dpm to
On Mar 31, 2015, at 08:23 PM, Balasankar C wrote:
>I saw a mention about inter-operability of git-dpm and git-bp in the
>link you provided[1]. What is the current status of this
>inter-operability?
I haven't seen any discussion of this in a long time. I think it was
happening on debian-devel.
C
Is there a way to use git but build with sbuild. I kind of don't want
to go back to pbuilder and IIRC git-buildpackage requires it.
On Tue, Mar 31, 2015 at 5:43 PM, Barry Warsaw wrote:
> On Mar 31, 2015, at 04:48 PM, Antoine Musso wrote:
>
>>I have only been introduced to git-buildpackage and usi
On Mar 31, 2015, at 05:46 PM, Zygmunt Krynicki wrote:
>Is there a way to use git but build with sbuild. I kind of don't want
>to go back to pbuilder and IIRC git-buildpackage requires it.
>> gitbp is aliased to `git-buildpackage --git-ignore-new --git-export=WC -S
>> -us -uc'
Notice the -S? I p
On 31 March 2015 at 17:46, Zygmunt Krynicki
wrote:
>
> Is there a way to use git but build with sbuild. I kind of don't want
> to go back to pbuilder and IIRC git-buildpackage requires it.
I build packages with --git-builder=sbuild all the time, and haven't
had any issues. You can also build sour
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Tianon,
On 31 March 2015 16:35:00 BST, Tianon Gravi wrote:
>On 31 March 2015 at 07:24, Daniel Lintott wrote:
>> I can't find an ITP/RFP bug for the package, but see that there are
>some
>> files already in SVN.
>
>I was packaging it originally
18 matches
Mail list logo
