Re: Pushing a bunch of packages to jessie-backports

2015-11-24 Thread Vincent Bernat
 ❦ 23 novembre 2015 09:20 +0100, Thomas Goirand  :

> alabaster contextlib2 kazoo python-cachetools python-cffi python-cliff
> python-crank python-ddt python-docker python-eventlet python-git
> python-gitdb python-hypothesis python-ldap3 python-mock python-mysqldb
> python-pathlib python-repoze.who python-setuptools python-smmap
> python-unicodecsv python-urllib3 requests routes ryu sphinx sqlalchemy
> turbogears2 unittest2 zzzeeksphinx

For python-cffi, its upload will break other packages in stable. This
has been discussed on IRC a few months ago. I don't remember
exactly. It will break snimpy, but not silently, so I'll upload a new
version in backports. It will break python-cryptography silently (will
happily coinstall but will crash on run). But some people wanted to have
a backport for it.

I can manage the backport of python-hypothesis myself, but I think you
will be faster than me, so go ahead.
-- 
Keep it right when you make it faster.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Re: Pushing a bunch of packages to jessie-backports

2015-11-24 Thread Sandro Tosi
On Mon, Nov 23, 2015 at 8:32 AM, Piotr Ożarowski  wrote:
> About sqlalchemy - Sandro is already working on it AFAICT, so you can
> skip this one.

gaah, sorry for not following up with this: we used that package to do
some training at work, and for various reason we cant upload the same
exact package we built here; anyway it was just a mare rebuild of
1.0.8+ds1-1 in jessie with the bpo tag appended to the pkg version. If
you want I can quickly rebuild one, or use zigo's one, Piotr just
lemme know.

regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi



Re: Pushing a bunch of packages to jessie-backports

2015-11-24 Thread Piotr Ożarowski
[Sandro Tosi, 2015-11-24]
> gaah, sorry for not following up with this: we used that package to do
> some training at work, and for various reason we cant upload the same
> exact package we built here; anyway it was just a mare rebuild of
> 1.0.8+ds1-1 in jessie with the bpo tag appended to the pkg version. If
> you want I can quickly rebuild one, or use zigo's one, Piotr just
> lemme know.

there's no "zigo's one", that's the point, he hides them.
I would much more prefer you to do it (and I don't need debdiff from
you, just upload)
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645



Re: Pushing a bunch of packages to jessie-backports

2015-11-24 Thread Sandro Tosi
On Tue, Nov 24, 2015 at 8:32 AM, Piotr Ożarowski  wrote:
> [Sandro Tosi, 2015-11-24]
>> gaah, sorry for not following up with this: we used that package to do
>> some training at work, and for various reason we cant upload the same
>> exact package we built here; anyway it was just a mare rebuild of
>> 1.0.8+ds1-1 in jessie with the bpo tag appended to the pkg version. If
>> you want I can quickly rebuild one, or use zigo's one, Piotr just
>> lemme know.
>
> there's no "zigo's one", that's the point, he hides them.
> I would much more prefer you to do it (and I don't need debdiff from
> you, just upload)

cool, will do soon then! do you want me to push a branch to git? if
so, how would you like it to be called: 'jessie', 'bpo8', else?

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi



Request to join the team

2015-11-24 Thread Dariusz Dwornikowski
Hi,

I would like to join the DPMT team to help maintaining python
packages, especially those that are dependencies of awscli, and those
I use on a day to day basis. I know Python, I do a lot of Python
programming at the University. 

I am almost DD, I am waiting for DAM to create my account. 

My alioth account is tdi-guest. 
I have read Debian Python Modules Team - Policy and I accept it. 


-- 
Dariusz Dwornikowski, 
  Institute of Computing Science, Poznań University of Technology
  www.cs.put.poznan.pl/ddwornikowski/  
  room 1.6.2 BTiCW | tel. +48 61 665 23 71


signature.asc
Description: PGP signature


Re: Pushing a bunch of packages to jessie-backports

2015-11-24 Thread Piotr Ożarowski
[Sandro Tosi, 2015-11-24]
> cool, will do soon then! do you want me to push a branch to git? if
> so, how would you like it to be called: 'jessie', 'bpo8', else?

I don't have strong opinion about branch names yet. I like standards, so
I'd prefer one described in DEP but they're not compatible with git-dpm,
unfortunately.

>From the two suggested ones I prefer jessie, but if it's just rebuild,
I'm also fine if you don't push it at all.
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645



Re: Pushing a bunch of packages to jessie-backports

2015-11-24 Thread Dmitry Shachnev
Hi Thomas,

On Mon, Nov 23, 2015 at 06:17:33PM +0100, Thomas Goirand wrote:
>> I will appreciate if you backport Sphinx because I was recently asked about
>> the same [1].
>
> Cool.
>
>> You will maybe also want to backport sphinx-rtd-theme ≥ 0.1.8-2,
>> where the dh_sphinxdoc experience was greatly improved.
>
> As much as I could see, I don't need sphinx-rtd-theme in backports.

OK.

>> You will also definitely have to do some changes like reverting the jquery
>> dependency bump made in 1.3.1-7 — Sphinx works with previous jquery versions,
>> but it had some issues with browser supports, that's why the dependency was
>> bumped.
>
> There's already a version 1.11.3+dfsg-4~bpo8+1 of jquery in backports,
> which is the one I also need for my other packages. So I don't think
> that one is a blocker.

Ack, I didn't notice that. Then there is a chance that you won't need any
changes (except adding a changelog entry) :)

--
Dmitry Shachnev


signature.asc
Description: PGP signature


Re: Pushing a bunch of packages to jessie-backports

2015-11-24 Thread Sandro Tosi
On Tue, Nov 24, 2015 at 9:28 AM, Piotr Ożarowski  wrote:
> [Sandro Tosi, 2015-11-24]
>> cool, will do soon then! do you want me to push a branch to git? if
>> so, how would you like it to be called: 'jessie', 'bpo8', else?
>
> I don't have strong opinion about branch names yet. I like standards, so
> I'd prefer one described in DEP but they're not compatible with git-dpm,
> unfortunately.
>
> >From the two suggested ones I prefer jessie, but if it's just rebuild,
> I'm also fine if you don't push it at all.

great, less work for me! I've just uploaded sqlalchemy 1.0.9 to jessie
backports, it was indeed just a rebuild. Thanks Piotr!

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi



Re: Pushing a bunch of packages to jessie-backports

2015-11-24 Thread Thomas Goirand
On 11/23/2015 09:54 PM, Piotr Ożarowski wrote:
>>> so my packages are out of limits for you
>>
>> Could you care to explain what you mean here?
> 
> it means I ask you (as that's all I can do) to not upload packages I
> maintain.

If you don't say you'll maintain the packages in backports (which I
warmly would welcome) and at the same time tell that you don't want me
to upload to stable-backports, what other choice do I have but to ignore
you? It wouldn't be a reasonable answer to give-up uploading OpenStack
to jessie-backports just because of this.

The rest of your message is only provocation (for example, when you
write that I don't do tests, when you perfectly know I run a CI to do
functional testing). I don't think replying to it will help.

Thomas Goirand (zigo)



Re: Pushing a bunch of packages to jessie-backports

2015-11-24 Thread Piotr Ożarowski
[Thomas Goirand, 2015-11-24]
> If you don't say you'll maintain the packages in backports (which I
> warmly would welcome) and at the same time tell that you don't want me
> to upload to stable-backports, what other choice do I have but to ignore
> you?

see my first email

PS I'm getting all the emails from backports even if I wasn't the one
who uploaded so this is official after all.
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645



Re: Pushing a bunch of packages to jessie-backports

2015-11-24 Thread Thomas Goirand
On 11/24/2015 01:32 PM, Sandro Tosi wrote:
> On Tue, Nov 24, 2015 at 9:28 AM, Piotr Ożarowski  wrote:
>> [Sandro Tosi, 2015-11-24]
>>> cool, will do soon then! do you want me to push a branch to git? if
>>> so, how would you like it to be called: 'jessie', 'bpo8', else?
>>
>> I don't have strong opinion about branch names yet. I like standards, so
>> I'd prefer one described in DEP but they're not compatible with git-dpm,
>> unfortunately.
>>
>> >From the two suggested ones I prefer jessie, but if it's just rebuild,
>> I'm also fine if you don't push it at all.
> 
> great, less work for me! I've just uploaded sqlalchemy 1.0.9 to jessie
> backports, it was indeed just a rebuild. Thanks Piotr!

Thanks for this upload.

Thomas Goirand (zigo)



Re: Pushing a bunch of packages to jessie-backports

2015-11-24 Thread Thomas Goirand
On 11/24/2015 07:29 PM, Piotr Ożarowski wrote:
> [Thomas Goirand, 2015-11-24]
>> If you don't say you'll maintain the packages in backports (which I
>> warmly would welcome) and at the same time tell that you don't want me
>> to upload to stable-backports, what other choice do I have but to ignore
>> you?
> 
> see my first email

Which part of it? The one where you're asking for a mail per package, or
the one where you're telling that your packages are off limit? The 2
parts are contradicting each other btw, so it's confusing.

> PS I'm getting all the emails from backports even if I wasn't the one
> who uploaded so this is official after all.

This isn't new, and it's been discussed at large. Basically, we would
all like the BTS to have the feature to select which is the maintainer
for a given suite. It is supposed to be fixed for the PPA^WBikeshed
support. In the mean time, we have to deal with it.

Cheers,

Thomas Goirand (zigo)



Re: Pushing a bunch of packages to jessie-backports

2015-11-24 Thread Piotr Ożarowski
[Thomas Goirand, 2015-11-24]
> Which part of it? The one where you're asking for a mail per package, or

debdiff of what you want to upload + time for me to check it (a week, I
will respond most probably in 24h, though)

> the one where you're telling that your packages are off limit? The 2
> parts are contradicting each other btw, so it's confusing.

this part is a response to what you wrote, see what I quoted

> > PS I'm getting all the emails from backports even if I wasn't the one
> > who uploaded so this is official after all.
> 
> This isn't new, and it's been discussed at large. Basically, we would
> all like the BTS to have the feature to select which is the maintainer
> for a given suite. It is supposed to be fixed for the PPA^WBikeshed
> support. In the mean time, we have to deal with it.

until this is fixed, I consider it official Debian archive and thus
any upload of *my* package that I do not approve: a hijack
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645



Re: Pushing a bunch of packages to jessie-backports

2015-11-24 Thread Thomas Goirand
On 11/25/2015 12:00 AM, Piotr Ożarowski wrote:
> [Thomas Goirand, 2015-11-24]
>> Which part of it? The one where you're asking for a mail per package, or
> 
> debdiff of what you want to upload + time for me to check it (a week, I
> will respond most probably in 24h, though)

I'll have to repeat myself then: there's no change but an entry in
debian/changelog for all packages which I listed, including the ones you
maintain. Or is it that you still require a debdiff for that? I hope
not, this would be an annoying loss of time for both you and me.



Re: [Python-modules-team] New git repository is not available in git/http protocol

2015-11-24 Thread Brian May
ChangZhuo Chen  writes:

> I setup a git repository in anonscm fir pgspecial packaging (#805882).
> The repositoy works fine in ssh, but it is not available for git/http.
> Do I need to do anything other than "gbp create-remote-repo" to make
> this repository available on git/http?

The correct procedure is here:
https://wiki.debian.org/Python/GitPackaging#Creating_new_repositories

You should use the "setup-repository" script.

The correct mailing list to use for questions like this is
debian-python@lists.debian.org - which I sent this message too, the
python-modules-team address is intended for automatic messages.
-- 
Brian May 
https://linuxpenguins.xyz/brian/