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)