Hi all,
find below the list of topics that are likely to come up in the next EPEL SIG meeting that's scheduled for tomorrow, Wednesday at 17:00 UTC in #fedora-extras on irc.freenode.org.
/topic EPEL Meeting -- repotags -- all /topic EPEL Meeting -- EPEL mock configs in Fedora's mock package -- /topic EPEL Meeting -- comps.xml for EPEL -- dglimore nirik and Jeff_S /topic EPEL Meeting -- bodhi/testing repo/final repo layout -- nirik/lmacken /topic EPEL Meeting -- finish the wiki docs and remove the warnings by end of may -- quaid /topic EPEL Meeting -- Communication plan for enterprise customers/ISVs/IHVs -- stahnma, quaid /topic EPEL Meeting -- Free discussion around EPEL
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 thl
P.S.: I'm on vacation ATM, but I should be there tomorrow
On Jun 12, 2007, at 12:38 PM, Thorsten Leemhuis wrote:
/topic EPEL Meeting -- EPEL mock configs in Fedora's mock package --
I have tested out the configs you sent to the list: https://www.redhat.com/archives/epel-devel-list/2007-May/msg00081.html
And they are working fine for me.
-Jeff
On Jun 12, 2007, at 1:29 PM, Jeff Sheltren wrote:
On Jun 12, 2007, at 12:38 PM, Thorsten Leemhuis wrote:
/topic EPEL Meeting -- EPEL mock configs in Fedora's mock package --
I have tested out the configs you sent to the list: https://www.redhat.com/archives/epel-devel-list/2007-May/msg00081.html
At one point a while back I was building something for el5 x86_64, and I ran into a problem of yum pulling in i386 packages (from the x86_64 core repo). Talking to people in #centos-devel, I got the following exclude line from Johnny Hughes (slightly modified) for the mock config: exclude=[a-zA-Z]*.i?86 g[^l]*.i?86 glib2*.i?86 glib-*.i?86 glib.i?86
Is this something that we should include in the x86_64 config for EL5? I see that the fedora x86_64 config has something similar.
-Jeff
Jeff Sheltren wrote:
At one point a while back I was building something for el5 x86_64, and I ran into a problem of yum pulling in i386 packages (from the x86_64 core repo). Talking to people in #centos-devel, I got the following exclude line from Johnny Hughes (slightly modified) for the mock config: exclude=[a-zA-Z]*.i?86 g[^l]*.i?86 glib2*.i?86 glib-*.i?86 glib.i?86
I've always used simply, exclude=*.i?86 why the extra fuss and complexity?
-- Rex
On 13.06.2007 14:21, Rex Dieter wrote:
Jeff Sheltren wrote:
At one point a while back I was building something for el5 x86_64, and I ran into a problem of yum pulling in i386 packages (from the x86_64 core repo). Talking to people in #centos-devel, I got the following exclude line from Johnny Hughes (slightly modified) for the mock config: exclude=[a-zA-Z]*.i?86 g[^l]*.i?86 glib2*.i?86 glib-*.i?86 glib.i?86
I've always used simply, exclude=*.i?86 why the extra fuss and complexity?
Can't remember, but there is a reason; that's why
/etc/mock/fedora-6-x86_64-core.cfg
also has
exclude=[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefhijklmnopqrstuvwxyz]*.i*86 g[abcdefghijkmnopqrstuvwxyz]*.i?86 glib2.i?86 glib.i?86 *-devel.i? 86
CU thl
On Jun 13, 2007, at 8:21 AM, Rex Dieter wrote:
Jeff Sheltren wrote:
At one point a while back I was building something for el5 x86_64, and I ran into a problem of yum pulling in i386 packages (from the x86_64 core repo). Talking to people in #centos-devel, I got the following exclude line from Johnny Hughes (slightly modified) for the mock config: exclude=[a-zA-Z]*.i?86 g[^l]*.i?86 glib2*.i?86 glib-*.i?86 glib.i?86
I've always used simply, exclude=*.i?86 why the extra fuss and complexity?
-- Rex
I'm really not sure. What I got from Johnny seems to be what is used in the Fedora configs: exclude=[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefhijklmnopqrstuvwxyz]*.i*86 g [abcdefghijkmnopqrstuvwxyz]*.i?86 glib2.i?86 glib.i?86 *-devel.i?86
I simplified the regexes a bit to get what I pasted in my previous mail, but honestly I don't know why not just exclude all i?86 packages. Are there possibly packages that we need that are not excluded by that line?
Either way, I think we need to have some sort of exclude for the x86_64 config or we end up with yum errors due to conflicting x86_64/ i?86 packages.
-Jeff
On Wed, Jun 13, 2007 at 08:41:36AM -0400, Jeff Sheltren wrote:
I simplified the regexes a bit to get what I pasted in my previous mail, but honestly I don't know why not just exclude all i?86 packages. Are there possibly packages that we need that are not excluded by that line?
Either way, I think we need to have some sort of exclude for the x86_64 config or we end up with yum errors due to conflicting x86_64/ i?86 packages.
The current EPEL 5 mock config has no exclude list. Can you please send me what you would like to see? -- Michael
On Jun 13, 2007, at 10:18 AM, Michael E Brown wrote:
On Wed, Jun 13, 2007 at 08:41:36AM -0400, Jeff Sheltren wrote:
I simplified the regexes a bit to get what I pasted in my previous mail, but honestly I don't know why not just exclude all i?86 packages. Are there possibly packages that we need that are not excluded by that line?
Either way, I think we need to have some sort of exclude for the x86_64 config or we end up with yum errors due to conflicting x86_64/ i?86 packages.
The current EPEL 5 mock config has no exclude list. Can you please send me what you would like to see? -- Michael
Hi Michael, maybe we can get this decided in the meeting today. I'll send an updated EL5 mock config to you and the list once we determine exactly what we need to exclude :)
By the way, can you tell from git/cvs who added the exclude lines initially to the Fedora config(s)?
Thanks, Jeff
On Wed, Jun 13, 2007 at 10:29:31AM -0400, Jeff Sheltren wrote:
On Jun 13, 2007, at 10:18 AM, Michael E Brown wrote:
On Wed, Jun 13, 2007 at 08:41:36AM -0400, Jeff Sheltren wrote:
I simplified the regexes a bit to get what I pasted in my previous mail, but honestly I don't know why not just exclude all i?86 packages. Are there possibly packages that we need that are not excluded by that line?
Either way, I think we need to have some sort of exclude for the x86_64 config or we end up with yum errors due to conflicting x86_64/ i?86 packages.
The current EPEL 5 mock config has no exclude list. Can you please send me what you would like to see? -- Michael
Hi Michael, maybe we can get this decided in the meeting today. I'll send an updated EL5 mock config to you and the list once we determine exactly what we need to exclude :)
Quickly. I have 0.7.1 ready to go as we hit a bug in 0.7.0. We will be releaseing 0.7.1 sometime today in the next couple hours.
Current configs that were posted a couple weeks ago (sans exclude=) are current staged for 0.7.1.
By the way, can you tell from git/cvs who added the exclude lines initially to the Fedora config(s)?
That would require more git-fu than I currently possess.
-- Michael
On 13.06.2007 17:45, Michael E Brown wrote:
On Wed, Jun 13, 2007 at 10:29:31AM -0400, Jeff Sheltren wrote:
On Jun 13, 2007, at 10:18 AM, Michael E Brown wrote:
Hi Michael, maybe we can get this decided in the meeting today. I'll send an updated EL5 mock config to you and the list once we determine exactly what we need to exclude :)
Quickly. I have 0.7.1 ready to go as we hit a bug in 0.7.0. We will be releaseing 0.7.1 sometime today in the next couple hours.
Current configs that were posted a couple weeks ago (sans exclude=) are current staged for 0.7.1.
Please just add the exclude line as it is found in /etc/mock/fedora-6-x86_64-core.cfg to the x86_64 config files for EPEL-4 and EPEL5 ; e.g. this line
exclude=[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefhijklmnopqrstuvwxyz]*.i*86 g[abcdefghijkmnopqrstuvwxyz]*.i?86 glib2.i?86 glib.i?86 *-devel.i?86
Thanks!
Cu thl
On Wed, Jun 13, 2007 at 05:55:46PM +0200, Thorsten Leemhuis wrote:
On 13.06.2007 17:45, Michael E Brown wrote:
On Wed, Jun 13, 2007 at 10:29:31AM -0400, Jeff Sheltren wrote:
On Jun 13, 2007, at 10:18 AM, Michael E Brown wrote:
Hi Michael, maybe we can get this decided in the meeting today. I'll send an updated EL5 mock config to you and the list once we determine exactly what we need to exclude :)
Quickly. I have 0.7.1 ready to go as we hit a bug in 0.7.0. We will be releaseing 0.7.1 sometime today in the next couple hours.
Current configs that were posted a couple weeks ago (sans exclude=) are current staged for 0.7.1.
Please just add the exclude line as it is found in /etc/mock/fedora-6-x86_64-core.cfg to the x86_64 config files for EPEL-4 and EPEL5 ; e.g. this line
exclude=[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefhijklmnopqrstuvwxyz]*.i*86 g[abcdefghijkmnopqrstuvwxyz]*.i?86 glib2.i?86 glib.i?86 *-devel.i?86
In fedora-6-x86_64-core.cfg, there is another exclude as well:
[local] name=local baseurl=http://buildsys.fedoraproject.org/plague-results/fedora-6-extras/ exclude=*.i386 *.ppc
I added the same to the epel configs. (Are you guys even using plague for EPEL 5?)
Pushed and will be in 0.7.1. -- Michael
On Jun 13, 2007, at 12:10 PM, Michael E Brown wrote:
In fedora-6-x86_64-core.cfg, there is another exclude as well:
[local] name=local baseurl=http://buildsys.fedoraproject.org/plague-results/fedora-6-extras/ exclude=*.i386 *.ppc
I added the same to the epel configs. (Are you guys even using plague for EPEL 5?)
Pushed and will be in 0.7.1.
Michael
Great, thanks for your help. The plague exclude *should* work, but we'll see what happens!
Yes, we're using plague for the time being, but planning to move over to koji once some other stuff gets worked out...
-Jeff
On Jun 13, 2007, at 11:45 AM, Michael E Brown wrote:
Hi Michael, maybe we can get this decided in the meeting today. I'll send an updated EL5 mock config to you and the list once we determine exactly what we need to exclude :)
Quickly. I have 0.7.1 ready to go as we hit a bug in 0.7.0. We will be releaseing 0.7.1 sometime today in the next couple hours.
Current configs that were posted a couple weeks ago (sans exclude=) are current staged for 0.7.1.
Hi Michael, if you have to push a 0.7.1 today, I'd lean towards simply copying the exclude line from a fedora x86_64 mock config and re-using that in the EL5 x86_64 config. That "works for me", and it's an improvement over the behavior without having an exclude line.
If anyone sees any problem with this, please respond soon so Michael can get the update pushed :)
-Jeff
On Wed, Jun 13, 2007 at 11:56:46AM -0400, Jeff Sheltren wrote:
On Jun 13, 2007, at 11:45 AM, Michael E Brown wrote:
Hi Michael, maybe we can get this decided in the meeting today. I'll send an updated EL5 mock config to you and the list once we determine exactly what we need to exclude :)
Quickly. I have 0.7.1 ready to go as we hit a bug in 0.7.0. We will be releaseing 0.7.1 sometime today in the next couple hours.
Current configs that were posted a couple weeks ago (sans exclude=) are current staged for 0.7.1.
Hi Michael, if you have to push a 0.7.1 today, I'd lean towards simply copying the exclude line from a fedora x86_64 mock config and re-using that in the EL5 x86_64 config. That "works for me", and it's an improvement over the behavior without having an exclude line.
If anyone sees any problem with this, please respond soon so Michael can get the update pushed :)
Will do.
Let me know if you guys want something different and I'll get it ready for 0.7.2. -- Michael
Once upon a time Wednesday 13 June 2007, Michael E Brown wrote:
On Wed, Jun 13, 2007 at 11:56:46AM -0400, Jeff Sheltren wrote:
On Jun 13, 2007, at 11:45 AM, Michael E Brown wrote:
Hi Michael, maybe we can get this decided in the meeting today. I'll send an updated EL5 mock config to you and the list once we determine exactly what we need to exclude :)
Quickly. I have 0.7.1 ready to go as we hit a bug in 0.7.0. We will be releaseing 0.7.1 sometime today in the next couple hours.
Current configs that were posted a couple weeks ago (sans exclude=) are current staged for 0.7.1.
Hi Michael, if you have to push a 0.7.1 today, I'd lean towards simply copying the exclude line from a fedora x86_64 mock config and re-using that in the EL5 x86_64 config. That "works for me", and it's an improvement over the behavior without having an exclude line.
If anyone sees any problem with this, please respond soon so Michael can get the update pushed :)
Will do.
Let me know if you guys want something different and I'll get it ready for 0.7.2.
the exclude is because some packages require glibc.i386 in the 64 bit chroot to build. gdb gcc and a few others
On Wed, 2007-06-13 at 21:29 -0500, Dennis Gilmore wrote:
Once upon a time Wednesday 13 June 2007, Michael E Brown wrote:
On Wed, Jun 13, 2007 at 11:56:46AM -0400, Jeff Sheltren wrote:
On Jun 13, 2007, at 11:45 AM, Michael E Brown wrote:
Hi Michael, maybe we can get this decided in the meeting today. I'll send an updated EL5 mock config to you and the list once we determine exactly what we need to exclude :)
Quickly. I have 0.7.1 ready to go as we hit a bug in 0.7.0. We will be releaseing 0.7.1 sometime today in the next couple hours.
Current configs that were posted a couple weeks ago (sans exclude=) are current staged for 0.7.1.
Hi Michael, if you have to push a 0.7.1 today, I'd lean towards simply copying the exclude line from a fedora x86_64 mock config and re-using that in the EL5 x86_64 config. That "works for me", and it's an improvement over the behavior without having an exclude line.
If anyone sees any problem with this, please respond soon so Michael can get the update pushed :)
Will do.
Let me know if you guys want something different and I'll get it ready for 0.7.2.
the exclude is because some packages require glibc.i386 in the 64 bit chroot to build. gdb gcc and a few others
Actually ... (3) i[3,4,5,6]86 things are potentially required in the x86_64 tree for building x86_64 RPMS: glibc.i386, glibc.i686, glibc-devel.i386. That exclude line does allow for all those to get called in when required, but blocks all other i386 arch content. It might not be "required" for EPEL (if you don't build any packages that need both 32 and 64 bit parts), but it is certainly required for Fedora and CentOS/RHEL base OSes if building in mock.
Also, if koji uses the same "Stage" repo functionality as plague (I am not sure how koji does its "generated" repos {or even if it does self generated repos}), you might also need to exclude x86_64 rpms in the i386 mock configs. (In plague the Staged feature {at least in our setup) does one set of repo metadata that contains all i386, x86_64, and all other arches. This means that when solving deps, all arches can be looked at and potentially called out of arch)
Again, this may or may not also be how koji does staged repos ... just food for thought.
Thanks, Johnny Hughes
epel-devel@lists.fedoraproject.org
-
Dennis Gilmore -
Jeff Sheltren -
Johnny Hughes -
Michael E Brown -
Rex Dieter -
Thorsten Leemhuis