[opensuse-packaging] Building of python packages disabled
I notice that building has been disabled for everything but factory for a large number of python packages in devel:languages:python. These packages build fine for earlier releases, in fact some haven't been updated in years (others were updated within the last few weeks). I don't see any mention of this happening on the mailing list. Is there a reason this was done? Since packages were disabled while their dependencies were sometimes not, it has resulted in a number of packages being left in an unresolvable state. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 08/15/2013 03:54 PM, Todd Rme wrote:
I notice that building has been disabled for everything but factory for a large number of python packages in devel:languages:python. These packages build fine for earlier releases, in fact some haven't been updated in years (others were updated within the last few weeks).
Reducing build failures increases the project's ranking, so you get faster rebuilds. The magic words are "earlier releases". Sometimes people just do one-off submits and forget about the package and their responsibility :-)
I don't see any mention of this happening on the mailing list. Is there a reason this was done?
I've been fixing countless Python packages over the years but I just disabled building against SLE for those I don't care about. Whenever somebody needs a specific package for SLE but lacks the coding skills, I even kindly fix those. The rest lies in the hand of the greater community. Packages that are broken for more than one year are simply dropped. This is a rather conservative rule I've been following for all projects where I am maintainer. So far nobody even noticed that :-) However, I always appreciate submit requests and it's also great if people want to revive stuff.
Since packages were disabled while their dependencies were sometimes not, it has resulted in a number of packages being left in an unresolvable state.
d:l:p is a rather big project and it's not always easy to react on time or check all the new packages that arrive. Not so long ago we had less than 10 build failures for more than 1200 packages. I admit we've got a little road to walk until we reach that again. -- 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 Thu, Aug 15, 2013 at 5:05 PM, Sascha Peilicke <speilicke@suse.com> wrote:
On 08/15/2013 03:54 PM, Todd Rme wrote:
I notice that building has been disabled for everything but factory for a large number of python packages in devel:languages:python. These packages build fine for earlier releases, in fact some haven't been updated in years (others were updated within the last few weeks).
Reducing build failures increases the project's ranking, so you get faster rebuilds. The magic words are "earlier releases". Sometimes people just do one-off submits and forget about the package and their responsibility :-)
I've tested some of these packages and they build fine on other releases. There doesn't seem to be any pattern related to how well-maintained they are, either. Some have had updates within a few months, other not in years, while other packages that have been updated much further in the past are still enabled.
I don't see any mention of this happening on the mailing list. Is there a reason this was done?
I've been fixing countless Python packages over the years but I just disabled building against SLE for those I don't care about. Whenever somebody needs a specific package for SLE but lacks the coding skills, I even kindly fix those. The rest lies in the hand of the greater community.
This isn't just SLE, the packages have building disabled generally and have only openSUSE_Factory manually set to enabled. Examples include python-zdaemon, python-bsddb3, python-setproctitle, and python-xdg. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 08/15/2013 05:27 PM, Todd Rme wrote:
On Thu, Aug 15, 2013 at 5:05 PM, Sascha Peilicke <speilicke@suse.com> wrote:
On 08/15/2013 03:54 PM, Todd Rme wrote:
I notice that building has been disabled for everything but factory for a large number of python packages in devel:languages:python. These packages build fine for earlier releases, in fact some haven't been updated in years (others were updated within the last few weeks).
Reducing build failures increases the project's ranking, so you get faster rebuilds. The magic words are "earlier releases". Sometimes people just do one-off submits and forget about the package and their responsibility :-)
I've tested some of these packages and they build fine on other releases.
Oh that's good news then. Feel free to either enable them or send a request. Unfortunately, OBS doesn't have a "repository request" where you could ask for such things in an automated way :-/
There doesn't seem to be any pattern related to how well-maintained they are, either. Some have had updates within a few months, other not in years, while other packages that have been updated much further in the past are still enabled.
You are right. If a very old package just builds fine it's absolutely perfect. If a package is failing on SLE and it's due to something that isn't easily backported to Python-2.6, it's best do disable it. However, since SUSE is heavily participating in the OpenStack community, we do have an interest to fix SLE issues. But we've got to concentrate on our direct dependencies and tend to ignore those we care less for.
I don't see any mention of this happening on the mailing list. Is there a reason this was done?
I've been fixing countless Python packages over the years but I just disabled building against SLE for those I don't care about. Whenever somebody needs a specific package for SLE but lacks the coding skills, I even kindly fix those. The rest lies in the hand of the greater community.
This isn't just SLE, the packages have building disabled generally and have only openSUSE_Factory manually set to enabled.
Uhm, that's odd I agree. Usually, these are linked from other devel projects. For instance, everything GNOME-related (python-gtk, python-cairo, python-gnome, ...) usually on builds on Factory. Similarly, python-qt4 / python-sip / python-pyside(-shiboken) from KDE:Qt also don't work on all platforms.
Examples include python-zdaemon, python-bsddb3, python-setproctitle, and python-xdg.
You could do submit some add_role requests so that you can work on those. Thanks for digging these up btw. -- 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 Fri, Aug 16, 2013 at 8:53 AM, Sascha Peilicke <speilicke@suse.com> wrote:
On 08/15/2013 05:27 PM, Todd Rme wrote:
Examples include python-zdaemon, python-bsddb3, python-setproctitle, and python-xdg.
You could do submit some add_role requests so that you can work on those. Thanks for digging these up btw.
I already have full access to devel:languages:python. I didn't fix these myself yet because I wanted to find out if there was a good reason for them being this way. Someone seems to have done this deliberately, and I didn't want to change it if it would cause problems. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (2)
-
Sascha Peilicke -
Todd Rme