Hi all,
find below the list of topics that are planed for the next EPEL SIG meeting which is scheduled for tomorrow, Wednesday at 17:00 UTC in #fedora-extras on irc.freenode.org.
/topic EPEL Meeting – broken deps – Jeff_S /topic EPEL Meeting – spam o magic script – mmcgrath /topic EPEL Meeting – branch for EPEL if Fedora maintainer does not react – knurd /topic EPEL Meeting – push new packages to testing after EPEL annoucement – dgilmore /topic EPEL Meeting – EPEL announcement – qua8d /topic EPEL Meeting – new meeting time? – all (see also http://fedoraproject.org/wiki/EPEL/NewMeetingTime ) /topic EPEL Meeting – how about packges that part of EL5Client, but not part of EL5Server (aka python-imaging-issue)
You want something to be discussed? Send a note to the list in reply to this mail and I'll add it to the schedule (I can't promise we will get to it tomorrow, but we'll most likely will if we don't run out of time). You can also propose topics at the end of the meeting itself.
If your name/nick is on above list please give a update. That way all the interested parties know what up ahead of the meeting; that will avoid long delays and "status update monologues in the meeting.
Thanks!
CU knurd
Hi!
On 17.07.2007 19:03, Thorsten Leemhuis wrote:
find below the list of topics that are planed for the next EPEL SIG meeting which is scheduled for tomorrow, Wednesday at 17:00 UTC in #fedora-extras on irc.freenode.org.
As I mentioned earlier already, I'll miss tomorrows meeting. Sorry.
/topic EPEL Meeting – broken deps – Jeff_S
dgilmore, could you push newly build packages once in the next 24 hours? And can somebody after that tun a script to check what deps are still broken? We have only 8 days left and I don't want to go into a
if (broken deps); then delay_epel_annoucement by one week; fi
loop that might never end.
To avoid that I'd say we should on Sunday try to move all packages with broken deps to testing that can be moved there without introducing new broken deps (I'm willing to help with that if I get the neccessary permissions to the repo and the spam-o-epel script).
Could you guys discuss this please tomorrow?
/topic EPEL Meeting – spam o magic script – mmcgrath
Only ran until EL5Server afaics which lead to "interesting" results. And progress here?
/topic EPEL Meeting – branch for EPEL if Fedora maintainer does not react – knurd
See https://www.redhat.com/archives/epel-devel-list/2007-July/msg00104.html and https://www.redhat.com/archives/epel-devel-list/2007-July/msg00105.html
Please get this ratified; gets a +1 from me.
/topic EPEL Meeting – push new packages to testing after EPEL annoucement – dgilmore
We should adjust this one or two days before the final announcement and make sure no new broken deps hit the repo.
/topic EPEL Meeting – EPEL announcement – quaid
Everything else ready?
/topic EPEL Meeting – new meeting time? – all (see also http://fedoraproject.org/wiki/EPEL/NewMeetingTime )
Can wait
/topic EPEL Meeting – how about packges that part of EL5Client, but not part of EL5Server (aka python-imaging-issue)
Discussed on the list currently, but should get attention in the meeting likely as well.
Cu knurd
On Jul 17, 2007, at 1:11 PM, Thorsten Leemhuis wrote:
/topic EPEL Meeting – broken deps – Jeff_S
dgilmore, could you push newly build packages once in the next 24 hours? And can somebody after that tun a script to check what deps are still broken? We have only 8 days left and I don't want to go into a
I can run repoclosure against CentOS 4 & 5 trees, but it would be nice if someone could also run against the RHEL packages we are building against. For example, can the spam-o-lot script be run without emailing out notices simply to come up with a list of broken deps? Or can someone run repoclosure against the RHEL sources we are building against?
Thanks, Jeff
Jeff Sheltren wrote:
On Jul 17, 2007, at 1:11 PM, Thorsten Leemhuis wrote:
/topic EPEL Meeting – broken deps – Jeff_S
dgilmore, could you push newly build packages once in the next 24 hours? And can somebody after that tun a script to check what deps are still broken? We have only 8 days left and I don't want to go into a
I can run repoclosure against CentOS 4 & 5 trees, but it would be nice if someone could also run against the RHEL packages we are building against. For example, can the spam-o-lot script be run without emailing out notices simply to come up with a list of broken deps? Or can someone run repoclosure against the RHEL sources we are building against?
Already done, just waiting for the meeting today to enable it completely.
-Mike
On Jul 18, 2007, at 9:22 AM, Mike McGrath wrote:
Jeff Sheltren wrote:
I can run repoclosure against CentOS 4 & 5 trees, but it would be nice if someone could also run against the RHEL packages we are building against. For example, can the spam-o-lot script be run without emailing out notices simply to come up with a list of broken deps? Or can someone run repoclosure against the RHEL sources we are building against?
Already done, just waiting for the meeting today to enable it completely.
-Mike
Cool, thanks. I just ran repoclosure against EPEL 4/5 and CentOS 4/5, and put the results here: http://www.sheltren.com/epel/repoclosure/2007-07-18/
It looks like we've still got a bunch of broken dependencies...
-Jeff
epel-devel@lists.fedoraproject.org