Re: Upstream has split a package in two -> new Debian package?

2016-04-04 Thread Christoph Mathys 

On 05.04.2016 03:51, Ben Finney wrote:

Christoph Mathys  writes:

Upstream has split some of the functionality of mercurial-keyring into
a separate python library and pip package (mercurial_extension_utils).


That seems to imply there will be separate releases and versions for
‘mercurial_extension_utils’. Is that correct?


Yes, this is the case.


If the source is managed and released separately, with distinct release
schedule and versions, yes there should be separate Debian packages for
that.


OK. Thanks for the clear and quick response!

Christoph

Re: Upstream has split a package in two -> new Debian package?

2016-04-04 Thread Ben Finney 
Christoph Mathys  writes:

> I'm the package maintainer of mercurial-keyring, a keyring extension
> for mercurial.

Thank you for maintaining this in Debian.

> Upstream has split some of the functionality of mercurial-keyring into
> a separate python library and pip package (mercurial_extension_utils).

That seems to imply there will be separate releases and versions for
‘mercurial_extension_utils’. Is that correct?

> Do I need to create and upload a new package for this library? Or is
> there another way?

If the source is managed and released separately, with distinct release
schedule and versions, yes there should be separate Debian packages for
that.

-- 
 \ “If nature has made any one thing less susceptible than all |
  `\others of exclusive property, it is the action of the thinking |
_o__)  power called an idea” —Thomas Jefferson, 1813-08-13 |
Ben Finney

Upstream has split a package in two -> new Debian package?

2016-04-04 Thread Christoph Mathys 

Hi!

I'm the package maintainer of mercurial-keyring, a keyring extension for 
mercurial. Upstream has split some of the functionality of 
mercurial-keyring into a separate python library and pip package 
(mercurial_extension_utils). Do I need to create and upload a new 
package for this library? Or is there another way?


I doubt that this library will get a second user, but you never know...

For reference:
https://pypi.python.org/pypi/mercurial_extension_utils
https://pypi.python.org/pypi/mercurial_keyring

Thanks.
Christoph