[opensuse-packaging] python-gobject and python3-gobject
Currently python-gobject in the devel:languages:python and python3-gobject in devel:languages:python3 are separated into two packages. However, python-gobject is linked to the version on openSUSE:Factory, which still has python 2 and python 3 spec files in one package. Its devel project is GNOME:Factory, which also still has both spec files. This is leading to frequency breakage in the devel:languages:python version, since it links to a package that has two spec files while it only has one. If we are going to go with the separate packages we should to it in factory as well. It would be easy to provide a submit request for this. However, currently python3-gobject in openSUSE:Factory and GNOME:Factory are linked to their respective python-gobject packages, so doing the submission now would break python3-gobject. So if we are going to go with the separate python2 and python3 packages, can we do so for python-gobject as well? If not, we need to either unlike python-gobject from factory, go back to using two spec files, or remove it from devel:languages:python entirely (which may not be a bad idea since it often depends on the latest GTK version anyway). -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 08/18/2013 02:57 PM, Todd Rme wrote:
Currently python-gobject in the devel:languages:python and python3-gobject in devel:languages:python3 are separated into two packages.
However, python-gobject is linked to the version on openSUSE:Factory, which still has python 2 and python 3 spec files in one package. Its devel project is GNOME:Factory, which also still has both spec files.
That doesn't look right. Seems like Factory has the wrong devel project link. It should come from GNOME:Factory instead.
This is leading to frequency breakage in the devel:languages:python version, since it links to a package that has two spec files while it only has one. If we are going to go with the separate packages we should to it in factory as well.
As said, python-gobject (including both spec files) comes from GNOME:... in is linked/branched in both d:l:p and d:l:p3. Even though both projects get both spec files only the one matching the OBS package name is build (e.g. python3-gobject in d:l:p3).
It would be easy to provide a submit request for this. However, currently python3-gobject in openSUSE:Factory and GNOME:Factory are linked to their respective python-gobject packages, so doing the submission now would break python3-gobject.
So if we are going to go with the separate python2 and python3 packages, can we do so for python-gobject as well? If not, we need to either unlike python-gobject from factory, go back to using two spec files, or remove it from devel:languages:python entirely (which may not be a bad idea since it often depends on the latest GTK version anyway).
It's a somewhat similar situation with python-qt4 (and friends), which is situated in KDE:Qt. It makes sense to keep those packages in those more on-topic devel project rather than in d:l:p / d:l:p3 since usually it's best to update the python binding alongside it'S C/C++ equivalent. As long as those are properly branched into d:l:p / d:l:p3, it shouldn't make a difference if the package(s) is/are split by spec files or not. -- Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)
On 08/18/2013 02:57 PM, Todd Rme wrote:
Currently python-gobject in the devel:languages:python and python3-gobject in devel:languages:python3 are separated into two packages.
However, python-gobject is linked to the version on openSUSE:Factory, which still has python 2 and python 3 spec files in one package. Its devel project is GNOME:Factory, which also still has both spec files.
This is leading to frequency breakage in the devel:languages:python version, since it links to a package that has two spec files while it only has one. If we are going to go with the separate packages we should to it in factory as well.
It would be easy to provide a submit request for this. However, currently python3-gobject in openSUSE:Factory and GNOME:Factory are linked to their respective python-gobject packages, so doing the submission now would break python3-gobject.
So if we are going to go with the separate python2 and python3 packages, can we do so for python-gobject as well? If not, we need to either unlike python-gobject from factory, go back to using two spec files, or remove it from devel:languages:python entirely (which may not be a bad idea since it often depends on the latest GTK version anyway).
Mhm, I don't think dropping both packages from d:l:p / d:l:p3 was a solution. I'll rebranch both from GNOME:Factory... -- Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)
participants (2)
-
Sascha Peilicke
-
Todd Rme