Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #8217 > unrolled thread

gphoto2 package name problem

Back to article view | Back to linux.debian.maint.python

Contents

  gphoto2 package name problem Damon Lynch <damonlynch@gmail.com> - 2016-02-20 08:00 +0100
    Re: gphoto2 package name problem Dmitry Shachnev <mitya57@debian.org> - 2016-02-20 12:50 +0100
      Re: gphoto2 package name problem Damon Lynch <damonlynch@gmail.com> - 2016-02-21 20:00 +0100
        Re: gphoto2 package name problem Dmitry Shachnev <mitya57@debian.org> - 2016-02-22 08:40 +0100
          Re: gphoto2 package name problem Damon Lynch <damonlynch@gmail.com> - 2016-02-22 09:30 +0100
          Re: gphoto2 package name problem Damon Lynch <damonlynch@gmail.com> - 2016-03-30 15:30 +0200
            Re: gphoto2 package name problem Dmitry Shachnev <mitya57@debian.org> - 2016-03-30 22:50 +0200

#8217 — gphoto2 package name problem

Several python bindings exist for gphoto2. The two most prominent are:

"python-gphoto2": https://pypi.python.org/pypi/gphoto2/
"gphoto2-cffi" gphoto2-cffi: https://pypi.python.org/pypi/gphoto2-cffi

The second of these, gphoto2-cffi, is packaged in Debian as 
"python-gphoto2". The first project is not currently packaged in Debian. 
As you might notice, the name of the Debian package is the same as the 
first project, not the second. I imagine that is pretty confusing for 
the casual user / developer who may not necessarily be paying careful 
attention to package and project names.

Until 12 days ago, both project's module namepspaces clashed with each 
other. Until the situation was resolved, it was impossible to have both 
installed simultaneously, because they both required this import:

 >>> import gphoto2

The problem was resolved when the developer of gphoto2-cffi agreed to 
rename the imported module as gphoto2cffi instead of gphoto2. This 
module name change has been reflected in github: 
https://github.com/jbaiter/gphoto2-cffi/commit/6de87c88e56b59588fe1be48e9227dfa00382b91
However the project has not had a new release since then.

When discussing the namespace problem, the developer of gphoto2-cffi 
commented "I created the library mainly for my own purposes . . . and 
did *not* expect it to end up in the Debian repositories as the default 
Python bindings for gphoto2"

Now the namespace problem has been resolved,  the project python-gphoto2 
can be included in python. I very much hope it will be packaged, as it's 
evolved into a mature project that provides the most comprehensive 
python binding available to gphoto2. In other words, it provides 
important functionality that other bindings do not.

This leaves the problem of the confusing Debian package name for the 
project gphoto2-cffi. Can it be changed to "python-gphoto2-cffi"?
Assuming the project "python-gphoto2" is packaged in Debian, what should 
it be called?

Thanks.

Best,
Damon

-- 

http://www.damonlynch.net

[toc] | [next] | [standalone]

#8218

[Multipart message — attachments visible in raw view] — view raw

Hi Damon,

On Sat, Feb 20, 2016 at 11:53:18AM +0500, Damon Lynch wrote:
> The problem was resolved when the developer of gphoto2-cffi agreed to rename
> the imported module as gphoto2cffi instead of gphoto2.
>
> [...]
>
> This leaves the problem of the confusing Debian package name for the project
> gphoto2-cffi. Can it be changed to "python-gphoto2-cffi"?

In this case it should be changed to python-gphoto2cffi.

> Assuming the project "python-gphoto2" is packaged in Debian, what should it
> be called?

When the other package is renamed, the new one can (in theory) take its past
name. There should be no problem because the old package had no rdepends and
the new one has a higher version number. However, you should probably talk to
the gphoto2-cffi maintainer first anyway to check if he's OK with you taking 
over the name.

--
Dmitry Shachnev

[toc] | [prev] | [next] | [standalone]

#8224

Hi Dimitry,

On 02/20/2016 04:47 PM, Dmitry Shachnev wrote:
> On Sat, Feb 20, 2016 at 11:53:18AM +0500, Damon Lynch wrote:
>> The problem was resolved when the developer of gphoto2-cffi agreed to rename
>> the imported module as gphoto2cffi instead of gphoto2.
>>
>> [...]
>>
>> This leaves the problem of the confusing Debian package name for the project
>> gphoto2-cffi. Can it be changed to "python-gphoto2-cffi"?
> In this case it should be changed to python-gphoto2cffi.
>
>> Assuming the project "python-gphoto2" is packaged in Debian, what should it
>> be called?
> When the other package is renamed, the new one can (in theory) take its past
> name. There should be no problem because the old package had no rdepends and
> the new one has a higher version number. However, you should probably talk to
> the gphoto2-cffi maintainer first anyway to check if he's OK with you taking
> over the name.

Good news: the developer of gphoto2-cffi has just confirmed that he is 
happy for both the package name of his project to be renamed into 
"python-gphoto2cffi" in Debian, and for the currently unpackaged project 
"python-gphoto2" to be given the Debian package name his project 
currently uses, "python-gphoto2".

As at the time of writing this email, the project "gphoto2-cffi" has not 
made a new release with the changed module name: 
https://github.com/jbaiter/gphoto2-cffi , although as I noted in my 
previous email, it has made the necessary commit: 
https://github.com/jbaiter/gphoto2-cffi/commit/6de87c88e56b59588fe1be48e9227dfa00382b91

I am assuming it will take a bit of time for for "python-gphoto2" 
(https://github.com/jim-easterbrook/python-gphoto2) to make it into 
Debian. Let me know if I can help, keeping in mind I'm very much a 
python application developer and not a packager! ;-)

I'm not sure on which day the deadline for Ubuntu to exclude/include 
Debian packages for the upcoming 16.04 release falls, but given it might 
be some time before the Python project "python-gphoto2" is made into a 
Debian package, is it possible to rename Debian package currently named 
"python-gphoto2" into "python-gphoto2cffi" as soon as is practical? It 
would be very nice if we could have the properly named package 
"python-gphoto2cffi" in Ubuntu 16.04, instead of the wrong name.

Thanks!
Damon

-- 

http://www.damonlynch.net

[toc] | [prev] | [next] | [standalone]

#8225

[Multipart message — attachments visible in raw view] — view raw

Hi Damon,

On Sun, Feb 21, 2016 at 11:55:28PM +0500, Damon Lynch wrote:
> Good news: the developer of gphoto2-cffi has just confirmed that he is happy
> for both the package name of his project to be renamed into
> "python-gphoto2cffi" in Debian, and for the currently unpackaged project
> "python-gphoto2" to be given the Debian package name his project currently
> uses, "python-gphoto2".

Great!

Have you talked to the upstream developer or to the Debian maintainer?
I meant the latter in my previous message.

> As at the time of writing this email, the project "gphoto2-cffi" has not
> made a new release with the changed module name:
> https://github.com/jbaiter/gphoto2-cffi , although as I noted in my previous
> email, it has made the necessary commit: https://github.com/jbaiter/gphoto2-cffi/commit/6de87c88e56b59588fe1be48e9227dfa00382b91
>
> I am assuming it will take a bit of time for for "python-gphoto2"
> (https://github.com/jim-easterbrook/python-gphoto2) to make it into Debian.
> Let me know if I can help, keeping in mind I'm very much a python
> application developer and not a packager! ;-)

Have you filed a request for packaging (RFP) then?

> I'm not sure on which day the deadline for Ubuntu to exclude/include Debian
> packages for the upcoming 16.04 release falls, but given it might be some
> time before the Python project "python-gphoto2" is made into a Debian
> package, is it possible to rename Debian package currently named
> "python-gphoto2" into "python-gphoto2cffi" as soon as is practical? It would
> be very nice if we could have the properly named package
> "python-gphoto2cffi" in Ubuntu 16.04, instead of the wrong name.

Again, that's a question to the maintainer. That package is not maintained
by our team.

Ubuntu 16.04 is already in the feature freeze, so maybe you'll need to ask for
a freeze exception if you want to need this done. If it'll be a sync from
Debian, the changes are high that it will be approved.

--
Dmitry Shachnev

[toc] | [prev] | [next] | [standalone]

#8226

On 02/22/2016 12:37 PM, Dmitry Shachnev wrote:
[...]
>> I am assuming it will take a bit of time for for "python-gphoto2"
>> (https://github.com/jim-easterbrook/python-gphoto2) to make it into Debian.
>> Let me know if I can help, keeping in mind I'm very much a python
>> application developer and not a packager! ;-)
> Have you filed a request for packaging (RFP) then?
>

I filed a request on April 1 last year, Debian Bug#781693.

I have just now contacted the Debian maintainer, as you suggested. Thanks!

Best,
Damon

-- 

http://www.damonlynch.net

[toc] | [prev] | [next] | [standalone]

#8362

[Multipart message — attachments visible in raw view] — view raw

On Mon, Feb 22, 2016 at 12:37 PM, Dmitry Shachnev <mitya57@debian.org>
wrote:

> Hi Damon,
>
> On Sun, Feb 21, 2016 at 11:55:28PM +0500, Damon Lynch wrote:
> > Good news: the developer of gphoto2-cffi has just confirmed that he is
> happy
> > for both the package name of his project to be renamed into
> > "python-gphoto2cffi" in Debian, and for the currently unpackaged project
> > "python-gphoto2" to be given the Debian package name his project
> currently
> > uses, "python-gphoto2".
>
> Great!
>
> Have you talked to the upstream developer or to the Debian maintainer?
> I meant the latter in my previous message.


> > As at the time of writing this email, the project "gphoto2-cffi" has not
> > made a new release with the changed module name:
> > https://github.com/jbaiter/gphoto2-cffi , although as I noted in my
> previous
> > email, it has made the necessary commit:
> https://github.com/jbaiter/gphoto2-cffi/commit/6de87c88e56b59588fe1be48e9227dfa00382b91
>

I'd like the help of a Debian packager / developer to rename a Debian
package before Ubuntu 16.04 is released. Very likely also required is
changing the name of the package's python module. The Debian package
maintainer and upstream developer are in full agreement regarding the
changes; all that is lacking is implementing it.

Specifically, via email, I have confirmed that the Debian maintainer of the
project "gphoto2-cffi"[1] agrees that its Debian package should be renamed
to "python-gphoto2cffi" and that it's python module should be "gphoto2cffi".
However the Debian maintainer says he/she been unable to make the changes
himself because he/she is too busy. Meanwhile the next Ubuntu release is
drawing ever closer.

Thanks,
Damon

[1] https://github.com/jbaiter/gphoto2-cffi
-- 
http://www.damonlynch.net

[toc] | [prev] | [next] | [standalone]

#8364

[Multipart message — attachments visible in raw view] — view raw

Hi Damon,

On Wed, Mar 30, 2016 at 06:19:58PM +0500, Damon Lynch wrote:
> I'd like the help of a Debian packager / developer to rename a Debian
> package before Ubuntu 16.04 is released. Very likely also required is
> changing the name of the package's python module. The Debian package
> maintainer and upstream developer are in full agreement regarding the
> changes; all that is lacking is implementing it.
>
> Specifically, via email, I have confirmed that the Debian maintainer of the
> project "gphoto2-cffi"[1] agrees that its Debian package should be renamed
> to "python-gphoto2cffi" and that it's python module should be "gphoto2cffi".
> However the Debian maintainer says he/she been unable to make the changes
> himself because he/she is too busy. Meanwhile the next Ubuntu release is
> drawing ever closer.

This was not difficult — a debdiff is attached.

If you want this in Ubuntu 16.04, you need to file a feature freeze exception
request first (and preferably get the Debian maintainer to upload it first, so
that it can be synced).

--
Dmitry Shachnev

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web