Re: Updating python-jsmin

2015-12-23 Thread Christopher Baines 
On 23/12/15 00:07, gustavo panizzo (gfa) wrote:
> On Tue, Dec 22, 2015 at 05:44:53PM +, Christopher Baines wrote:
>> python-jsmin [1] is not currently maintained by the Python Modules Team,
>> but I have made a attempt at updating it to the latest upstream version
>> in a manor compliant with the team policy.
>
> do you have a link for the team policy?

Yes, you can find it here:
  https://python-modules.alioth.debian.org/policy.html

> You could have open a bug and I would update the pkg, or just ping me.
> to get it updated to the latest version.

Ok, getting an up to date package in Debian would be great. Are you now
planning on updating it?

>> You can find the package here [2]. Is anyone (including the current
>> maintainer CC'ed) interested in updating this package, and possibly
>> bringing it in to the team?
> 
> I'm OK moving it into the python modules team, if I don't have to change
> my workflow much, or follow another mailing list

Sounds like team maintenance is not the best option then at the moment,
as I imagine that there are significant workflow changes (the
python-jsmin package is not in Git at the moment).

Re: Adopting factory-boy

2015-12-23 Thread Thomas Goirand 
On 12/19/2015 07:06 PM, Dmitry Shachnev wrote:
> Hi Christopher,
> 
> On Sat, Dec 19, 2015 at 11:34:15AM +, Christopher Baines wrote:
>> [...]
>>
>> The source package can be found here [3], would it be best to try to
>> continue with the history in that repository and bring it in to
>> compliance with the team policy (use pristine-tar, use upstream tarballs
>> to advance the upstream branch and use git-dpm), or to just start from
>> scratch?
> 
> Of course it would be better to preserve the changes history.
> 
> Basically you need to push the “debian/unstable” branch to the new repository
> as “master”, add missing “upstream” and “pristine-tar” branches, and call
> “git-dpm init”.
> 
> Your upstream branch should be based on commit ac7e11a3389f15bb, so that git
> can handle the merge correctly.
> 
> --
> Dmitry Shachnev

Hi Christopher,

I was the maintainer of this package, though I lost interest for it
because there's no reverse dependency for it.

If you want to continue maintaining it within the OpenStack PKG team,
you can do it as well. Though we're not using git-dpm, and rather a git
tag workflow, you're still free to use whatever workflow you want there,
as long as the package is well maintained.

If you need sponsoring for this package, I can review it and upload it
for you.

Cheers,

Thomas Goirand (zigo)

Re: Updating python-jsmin

2015-12-23 Thread Christopher Baines 
On 23/12/15 10:48, gustavo panizzo (gfa) wrote:
> I will update the pkg, last updates weren't difficult so I expect to get
> it done soon.
> 
> Pkg is already on git, in collab-maint

Ah, sorry, I missed that. I just used apt-get source to get the source
package.

Re: Adopting factory-boy

2015-12-23 Thread Christopher Baines 
On 23/12/15 11:31, Thomas Goirand wrote:
> I was the maintainer of this package, though I lost interest for it
> because there's no reverse dependency for it.

Thanks for packaging it :)

> If you want to continue maintaining it within the OpenStack PKG team,
> you can do it as well. Though we're not using git-dpm, and rather a git
> tag workflow, you're still free to use whatever workflow you want there,
> as long as the package is well maintained.
> 
> If you need sponsoring for this package, I can review it and upload it
> for you.

Great, thanks for the offer. I think I'll have to wait a couple of weeks
to see where things are for packaging this. There is at least one new
dependency for the latest release (python-fake-factory), I have packaged
that, but the tests currently don't pass. Once there is a release for
python-fake-factory, for which the tests pass, and that has been
uploaded to Debian, I'll get around to looking at factory-boy again.

RFS: python-prometheus-client /0.0.13

2015-12-23 Thread Christopher Baines 
Hello,

I am looking for a sponsor for python-prometheus-client.

* Package name: python-prometheus-client
  Version : 0.0.13
  Upstream Author : Brian Brazil 
* URL : https://github.com/prometheus/client_python
* License : Apache-2.0
  Programming Lang: Python
  Description : Python client for the Prometheus monitoring system

You can find this package here:

  http://git.cbaines.net/python-prometheus-client/

I have attempted to follow the team policy when packaging this.

Currently the tests do not pass for python 3, so I have disabled them.
This is an issue with the tests that will be fixed in the next upstream
release.

Thanks,

Chris

Re: Updating python-jsmin

2015-12-23 Thread Ben Finney 
Christopher Baines  writes:

> On 23/12/15 10:48, gustavo panizzo (gfa) wrote:
> > Pkg is already on git, in collab-maint
>
> Ah, sorry, I missed that. I just used apt-get source to get the source
> package.

For future reference: The ‘debcheckout(1)’ command will automatically
query the package's “VCS-*” fields and get the source from the specified
VCS repository.

That currently fails for ‘python-jsmin’. Gustavo, please read the
Developer's Reference §6.2.5 and add the appropriate “VCS-*” fields to
the source package.

-- 
 \  “We suffer primarily not from our vices or our weaknesses, but |
  `\from our illusions.” —Daniel J. Boorstin, historian, 1914–2004 |
_o__)  |
Ben Finney

Re: Updating python-jsmin

2015-12-23 Thread gustavo panizzo (gfa) 
I will update the pkg, last updates weren't difficult so I expect to get it 
done soon.

Pkg is already on git, in collab-maint


PS: sorry for the top posting

On December 23, 2015 6:03:13 PM GMT+08:00, Christopher Baines 
 wrote:
>On 23/12/15 00:07, gustavo panizzo (gfa) wrote:
>> On Tue, Dec 22, 2015 at 05:44:53PM +, Christopher Baines wrote:
>>> python-jsmin [1] is not currently maintained by the Python Modules
>Team,
>>> but I have made a attempt at updating it to the latest upstream
>version
>>> in a manor compliant with the team policy.
>>
>> do you have a link for the team policy?
>
>Yes, you can find it here:
>  https://python-modules.alioth.debian.org/policy.html
>
>> You could have open a bug and I would update the pkg, or just ping
>me.
>> to get it updated to the latest version.
>
>Ok, getting an up to date package in Debian would be great. Are you now
>planning on updating it?
>
>>> You can find the package here [2]. Is anyone (including the current
>>> maintainer CC'ed) interested in updating this package, and possibly
>>> bringing it in to the team?
>> 
>> I'm OK moving it into the python modules team, if I don't have to
>change
>> my workflow much, or follow another mailing list
>
>Sounds like team maintenance is not the best option then at the moment,
>as I imagine that there are significant workflow changes (the
>python-jsmin package is not in Git at the moment).

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.