We've switched over to using the final rhel7 content finally.
Sorry for the delay.
As you can see from the epel7 build tag in koji: http://koji.fedoraproject.org/koji/taginfo?tagID=259
we have the following rhel7 channels that we are building against and will not conflict with:
rhel7-server rhel7-rhel-extras rhel7-server-ha rhel7-server-optional
Hopefully we can get the wiki page with package contents updated soon.
Thanks,
kevin
On Wed, Jun 25, 2014 at 8:18 AM, Kevin Fenzi kevin@scrye.com wrote:
We've switched over to using the final rhel7 content finally.
Sorry for the delay.
As you can see from the epel7 build tag in koji: http://koji.fedoraproject.org/koji/taginfo?tagID=259
we have the following rhel7 channels that we are building against and will not conflict with:
rhel7-server rhel7-rhel-extras rhel7-server-ha rhel7-server-optional
Hopefully we can get the wiki page with package contents updated soon.
Thanks,
kevin
Awesome, thanks!
Is there a plan/schedule for getting epel-7 builds into the normal git/koji/bodhi workflow? Is that waiting on a CentOS release, or are there other issues?
-Jeff
On Wed, 25 Jun 2014 08:23:24 -0700 Jeff Sheltren jeff@tag1consulting.com wrote:
Awesome, thanks!
Is there a plan/schedule for getting epel-7 builds into the normal git/koji/bodhi workflow? Is that waiting on a CentOS release, or are there other issues?
Well, at least centos release... but additionally:
* We should decide what to do with packages in the beta that have broken deps. I'm thinking we untag them so they don't go out at all and maintainers need to retag them or rebuild them when deps are met and push them via bodhi.
* Are there any other larger stacks of packages that maintainers are planning on landing? Those would be good to do before leaving beta, but I don't know of any off hand. (well, aside the xfce packages that are branched and I need to find time to build and test).
* We might want to write up some press around moving to normal epel7. Press release, announcement, etc.
kevin
On 25 June 2014 09:28, Kevin Fenzi kevin@scrye.com wrote:
On Wed, 25 Jun 2014 08:23:24 -0700 Jeff Sheltren jeff@tag1consulting.com wrote:
Awesome, thanks!
Is there a plan/schedule for getting epel-7 builds into the normal git/koji/bodhi workflow? Is that waiting on a CentOS release, or are there other issues?
Well, at least centos release... but additionally:
- We should decide what to do with packages in the beta that have broken deps. I'm thinking we untag them so they don't go out at all and maintainers need to retag them or rebuild them when deps are met and push them via bodhi.
I figure we would rebuild all of the EPEL beta and consider all broken deps and such FTBFS.
- Are there any other larger stacks of packages that maintainers are planning on landing? Those would be good to do before leaving beta, but I don't know of any off hand. (well, aside the xfce packages that are branched and I need to find time to build and test).
I will help on this next week. I have to rebuild a box for desktop testing of all alternative desktop stacks.
- We might want to write up some press around moving to normal epel7. Press release, announcement, etc.
kevin
epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Wed, 25 Jun 2014 09:41:32 -0600 Stephen John Smoogen smooge@gmail.com wrote:
On 25 June 2014 09:28, Kevin Fenzi kevin@scrye.com wrote:
On Wed, 25 Jun 2014 08:23:24 -0700 Jeff Sheltren jeff@tag1consulting.com wrote:
Awesome, thanks!
Is there a plan/schedule for getting epel-7 builds into the normal git/koji/bodhi workflow? Is that waiting on a CentOS release, or are there other issues?
Well, at least centos release... but additionally:
- We should decide what to do with packages in the beta that have broken deps. I'm thinking we untag them so they don't go out at
all and maintainers need to retag them or rebuild them when deps are met and push them via bodhi.
I figure we would rebuild all of the EPEL beta and consider all broken deps and such FTBFS.
I'm not sure there's any need to do a mass rebuild, but I could be wrong. Anything that has broken deps might need a rebuild, but the maintainer could just take care of those?
kevin
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 06/26/2014 11:07 AM, Kevin Fenzi wrote:
On Wed, 25 Jun 2014 09:41:32 -0600 Stephen John Smoogen smooge@gmail.com wrote:
On 25 June 2014 09:28, Kevin Fenzi kevin@scrye.com wrote:
On Wed, 25 Jun 2014 08:23:24 -0700 Jeff Sheltren jeff@tag1consulting.com wrote:
Awesome, thanks!
Is there a plan/schedule for getting epel-7 builds into the normal git/koji/bodhi workflow? Is that waiting on a CentOS release, or are there other issues?
Well, at least centos release... but additionally:
- We should decide what to do with packages in the beta that
have broken deps. I'm thinking we untag them so they don't go out at all and maintainers need to retag them or rebuild them when deps are met and push them via bodhi.
I figure we would rebuild all of the EPEL beta and consider all broken deps and such FTBFS.
I'm not sure there's any need to do a mass rebuild, but I could be wrong. Anything that has broken deps might need a rebuild, but the maintainer could just take care of those?
If packages were built against the rc, they're probably fine. There were only around 50 or so packages that changed between final and the rc I believe...
If things were built against the beta (and I believe many were) there's a fair bit of change and a mass rebuild would probably be a good idea. Does a mass rebuild cost anything more than time to execute?
- -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77
On Wed, Jun 25, 2014 at 09:18:34AM -0600, Kevin Fenzi wrote:
Hopefully we can get the wiki page with package contents updated soon.
https://fedoraproject.org/wiki/EPEL/epel7 is now updated. There is no notation yet, which tells from which channel the package is coming.
Regards Till
epel-devel@lists.fedoraproject.org
-
Jeff Sheltren -
Jim Perrin -
Kevin Fenzi -
Stephen John Smoogen -
Till Maas