[opensuse-packaging] URGENT: please review your project.diffs
Hi, On http://www.suse.de/~coolo/factory-status.html I try to collect all problematic packages. While it defaults to show only packages currently failing, you can switch to show all problems in the first line. And there a lot of packages where someone accepted it to the devel project reviewing and then didn't submit it for inclusion to the distribution. This is a problem as we're nearing already the 2nd milestone after version freeze and I see tons of such packages ;( Take e.g. python-cairo, a prime example ;( <collection> <request id="15026"> <action type="submit"> <source project="home:lmedinas:branches:GNOME:Factory" package="python- cairo" rev="2" /> <target project="GNOME:Factory" package="python-cairo" /> </action> <state name="accepted" who="vuntz" when="2009-07-21T13:55:05"> <comment></comment> </state> <history name="new" who="lmedinas" when="2009-07-21T13:49:04" /> <description>Update to 1.8.6</description> </request> <request id="16898"> <action type="submit"> <source project="GNOME:Factory" package="python-cairo" rev="9" /> <target project="devel:languages:python" package="python-cairo" /> </action> <state name="accepted" who="poeml" when="2009-08-06T14:44:30"> <comment>reviewed ok.</comment> </state> <history name="new" who="vuntz" when="2009-08-06T00:07:38" /> <description>New upstream version</description> </request> </collection> lmedinas, vuntz, poeml - 3 people worked on this package and still it isn't in 11.2 ;( I understand the problem very well and IMO the work flow just _asks_ for that trouble, but it is as it is - and _everyone_ needs to be aware of it and help others in looking at factory-status.html for packages he worked on and expected them to end in 11.2 Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Le jeudi 27 août 2009, à 15:03 +0200, Stephan Kulow a écrit :
Take e.g. python-cairo, a prime example ;(
The problem here is that the devel project was changed to devel:languages:python while it was GNOME:Factory before. And so what is in G:F never went anywhere... (will fix it with my next push to oS:F) Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Le jeudi 27 août 2009, à 16:31 +0200, Vincent Untz a écrit :
Le jeudi 27 août 2009, à 15:03 +0200, Stephan Kulow a écrit :
Take e.g. python-cairo, a prime example ;(
The problem here is that the devel project was changed to devel:languages:python while it was GNOME:Factory before. And so what is in G:F never went anywhere...
(will fix it with my next push to oS:F)
Actually, we pushed the update to d:l:p too; so someone from the project should push it to oS:F, I guess. (and please don't add me as maintainer of d:l:p, thanks :-)) Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Donnerstag 27 August 2009 schrieb Vincent Untz:
Le jeudi 27 août 2009, à 16:31 +0200, Vincent Untz a écrit :
Le jeudi 27 août 2009, à 15:03 +0200, Stephan Kulow a écrit :
Take e.g. python-cairo, a prime example ;(
The problem here is that the devel project was changed to devel:languages:python while it was GNOME:Factory before. And so what is in G:F never went anywhere...
(will fix it with my next push to oS:F)
Actually, we pushed the update to d:l:p too; so someone from the project should push it to oS:F, I guess.
Well, there is no maintainer/bugowner for that package - before the maintainer was gnome-maintainers@ and now it's in the garbage bin d:l:p and that's a huge problem ;( We urgently need people to care for packages to also register as maintainer / bugowner of them. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Donnerstag 27 August 2009 schrieb Stephan Kulow:
Am Donnerstag 27 August 2009 schrieb Vincent Untz:
Le jeudi 27 août 2009, à 16:31 +0200, Vincent Untz a écrit :
Le jeudi 27 août 2009, à 15:03 +0200, Stephan Kulow a écrit :
Take e.g. python-cairo, a prime example ;(
The problem here is that the devel project was changed to devel:languages:python while it was GNOME:Factory before. And so what is in G:F never went anywhere...
(will fix it with my next push to oS:F)
Actually, we pushed the update to d:l:p too; so someone from the project should push it to oS:F, I guess.
Well, there is no maintainer/bugowner for that package - before the maintainer was gnome-maintainers@ and now it's in the garbage bin d:l:p and that's a huge problem ;(
BTW: the better alternative for this very package is reverting the change from G:F to d:l:p because obviously the people in G:F are those that care for python-cairo and that's what should define the devel projects. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Le jeudi 27 août 2009, à 17:05 +0200, Stephan Kulow a écrit :
Am Donnerstag 27 August 2009 schrieb Stephan Kulow:
Am Donnerstag 27 August 2009 schrieb Vincent Untz:
Le jeudi 27 août 2009, à 16:31 +0200, Vincent Untz a écrit :
Le jeudi 27 août 2009, à 15:03 +0200, Stephan Kulow a écrit :
Take e.g. python-cairo, a prime example ;(
The problem here is that the devel project was changed to devel:languages:python while it was GNOME:Factory before. And so what is in G:F never went anywhere...
(will fix it with my next push to oS:F)
Actually, we pushed the update to d:l:p too; so someone from the project should push it to oS:F, I guess.
Well, there is no maintainer/bugowner for that package - before the maintainer was gnome-maintainers@ and now it's in the garbage bin d:l:p and that's a huge problem ;(
BTW: the better alternative for this very package is reverting the change from G:F to d:l:p because obviously the people in G:F are those that care for python-cairo and that's what should define the devel projects.
Opinion from some d:l:p maintainer? That's certainly fine for the GNOME team; note that we'd probably want to move back a few other GNOME-related python packages... Alternatively, if someone gives me maintainership of the relevant packages in d:l:p, and if this is enough for me receiving hermes mails for this and me being able to push those packages to oS:F, then I'm fine with such a solution. FWIW, a rough list of python packages that we had in G:F (or in which I was interested for other reasons) is: python-cairo, python-cups, python-gdata, python-gnome-extras, python-gobject2, python-goocanvas, python-gstreamer-0_10, python-gtk, python-gtkglext, python-gtksourceview, python-notify, python-orbit, python-smbc, python-xdg, python-xlib Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Dne 27.8.2009 19:16, Vincent Untz napsal(a):
Le jeudi 27 août 2009, à 17:05 +0200, Stephan Kulow a écrit :
Am Donnerstag 27 August 2009 schrieb Stephan Kulow:
Am Donnerstag 27 August 2009 schrieb Vincent Untz:
Le jeudi 27 août 2009, à 16:31 +0200, Vincent Untz a écrit :
Le jeudi 27 août 2009, à 15:03 +0200, Stephan Kulow a écrit :
Take e.g. python-cairo, a prime example ;(
The problem here is that the devel project was changed to devel:languages:python while it was GNOME:Factory before. And so what is in G:F never went anywhere...
(will fix it with my next push to oS:F)
Actually, we pushed the update to d:l:p too; so someone from the project should push it to oS:F, I guess.
Well, there is no maintainer/bugowner for that package - before the maintainer was gnome-maintainers@ and now it's in the garbage bin d:l:p and that's a huge problem ;(
BTW: the better alternative for this very package is reverting the change from G:F to d:l:p because obviously the people in G:F are those that care for python-cairo and that's what should define the devel projects.
Opinion from some d:l:p maintainer? That's certainly fine for the GNOME team; note that we'd probably want to move back a few other GNOME-related python packages...
fine with me at least, i see no reason to keep everything pythonic in d:l:py - it's not a "project" in the original sense, it's more of a "collection", while GNOME definitely is a "project". but you must promise to watch opensuse-packaging for python-related announcements and act on them ;)
Alternatively, if someone gives me maintainership of the relevant packages in d:l:p, and if this is enough for me receiving hermes mails for this and me being able to push those packages to oS:F, then I'm fine with such a solution.
FWIW, a rough list of python packages that we had in G:F (or in which I was interested for other reasons) is: python-cairo, python-cups, python-gdata, python-gnome-extras, python-gobject2, python-goocanvas, python-gstreamer-0_10, python-gtk, python-gtkglext, python-gtksourceview, python-notify, python-orbit, python-smbc, python-xdg, python-xlib
adding you as a maintainer for all those, plus python-gnome (which i think you missed) as of now, python-orbit, python-gnome and python-gtk are mine, but i'll be happy to hand them over to the GNOME folk.
Vincent
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (3)
-
Jan Matejek -
Stephan Kulow -
Vincent Untz