[EPEL-devel] Re: 32 bit revisited
On 10/20/2016 01:17 PM, Matthew Miller wrote: > On Thu, Oct 20, 2016 at 12:55:02PM -0700, Karsten Wade wrote: >> Part of my thinking is the situation where CentOS SIGs need EPEL >> packages and (aiui currently) have to import to git.centos.org and build >> the packages on cbs.centos.org. > > Do you mean for 32-bit in specific, or in general? In that case, why > import instead of just using the packages directly? I think it's the same situation that Fedora has -- if it's not built on CentOS infra, then it can't be called "CentOS." For end users we now have the EPEL repo package available, but that doesn't help SIG dependencies. AIUI, YMMV. - Karsten -- Karsten Wade Community Infra & Platform (Mgr) Open Source and Standards, @redhatopen @quaid gpg: AD0E0C41 signature.asc Description: OpenPGP digital signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
[EPEL-devel] Re: 32 bit revisited
cOn 10/20/2016 07:06 AM, Kevin Fenzi wrote: > On Sun, 16 Oct 2016 21:54:44 -0700 > Karsten Wade <kw...@redhat.com> wrote: > >> On 10/15/2016 10:43 AM, Kevin Fenzi wrote: >>> On Sat, 15 Oct 2016 07:54:25 + (UTC) >>> john tatt <zika...@yahoo.com> wrote: >>> >>>> HiSo almost one year ago, some people asked for a 32bits EPEL 7 >>>> repo, as you can see. In last january, the goal was apparently to >>>> bring it just after fixing the ppc64 Do you think it will happen >>>> someday ? >>> >>> I hope so, but it's going to be tricky. There's no RHEL for 32bit, >>> so we would need to use CentOS, but then what do we do at the times >>> rhel updates and CentOS hasn't yet? Perhaps we build against CentOS >>> CI... >> >> I'll go out for a stretch here and ask ... what if we build not only >> against CentOS CI but in the CentOS build system? > > Well, not sure how that would work. > > You mean when you do a 'fedpkg build' it builds the normal epel arches > in the Fedora koji and also fires off a i686 build in the centos build > system? > > If so: > > * We would need to issue certs for every epel maintainer to be able to > build in centos. > * Also the centos build sys would need to allow builds from Fedora pkgs > source. > * Things could get out of sync if the centos build and epel builds one > or the other fails. > * How would maintainers push updates in the centos side? Or would that > just collect the builds and make a single repo/release ? I was mainly proposing a thought experiment, and you're right, there are a lot of bits involved that doesn't make it easy. There may simply be too much inertia until we find the eventual reason to do the work. Part of my thinking is the situation where CentOS SIGs need EPEL packages and (aiui currently) have to import to git.centos.org and build the packages on cbs.centos.org. I'm basically back to being curious on the topic of EPEL & CentOS and how best to interact. Regards, - Karsten -- Karsten Wade Community Infra & Platform (Mgr) Open Source and Standards, @redhatopen @quaid gpg: AD0E0C41 signature.asc Description: OpenPGP digital signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
[EPEL-devel] Re: 32 bit revisited
On 10/15/2016 10:43 AM, Kevin Fenzi wrote: > On Sat, 15 Oct 2016 07:54:25 + (UTC) > john tatt <zika...@yahoo.com> wrote: > >> HiSo almost one year ago, some people asked for a 32bits EPEL 7 repo, >> as you can see. In last january, the goal was apparently to bring it >> just after fixing the ppc64 Do you think it will happen someday ? > > I hope so, but it's going to be tricky. There's no RHEL for 32bit, so > we would need to use CentOS, but then what do we do at the times rhel > updates and CentOS hasn't yet? Perhaps we build against CentOS CI... I'll go out for a stretch here and ask ... what if we build not only against CentOS CI but in the CentOS build system? - Karsten -- Karsten Wade Community Infra & Platform (Mgr) Open Source and Standards, @redhatopen @quaid gpg: AD0E0C41 signature.asc Description: OpenPGP digital signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Re: [EPEL-devel] [Proposal] Converge EPEL and CBS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/23/2015 09:49 AM, Stephen John Smoogen wrote:
> On 23 September 2015 at 10:31, Matthew Miller
> <mat...@fedoraproject.org> wrote:
>> On Tue, Sep 22, 2015 at 08:45:32PM -0700, Karsten Wade wrote:
>>> AIUI, the concern is that what is labeled/supported by the
>>> CentOS Project as 'CentOS' needs to go through the CentOS
>>> Project QA system. We simply cannot blindly accept builds from
>>> outside of the CentOS builders just on say-so. (Compare to
>>> RPMfusion et al -- putting that repo in as a default for Fedora
>>> users is more than a legal issue, it's a
>>> QA/test/build/sign/release issue.)
>>
>> I can understand that with "out of the family" sources, but with
>> Red Hat now sponsoring CentOS as well as Fedora can we build
>> a better bridge of trust, here?
>>
>
> I thought what Karsten was asking for was "Trust but Verify". They
> aren't going to blindly trust RPMs for CentOS more than we are
> going to blindly trust RPMs from COPRs in the build system {I think
> Copr is a better analogy than RPMfusion as that gets covered in
> legal sauce.}. The packages need some sort of testing which would
> actually be more than what we have currently in EPEL. {h I
> didn't say this.}
>
> There are multiple ways they can trust but verify. * Rebuild the
> package in the CBS system and get their CI to run tests as part of
> that. * Run the CI against the packages which depending on how the
> CI is intertwined with Koji may be harder than it sounds. * Help
> get a similar CI stood up for EPEL and trust those results.
Thanks, yes, this is an accurate explanation of what I meant to say. :)
I also haven't talked with KB about this in a while, he's out of
pocket for the next few weeks, so it may be a bit until we can get his
input.
- - Karsten
- --
Karsten 'quaid' Wade.^\ CentOS Doer of Stuff
http://TheOpenSourceWay.org\ http://community.redhat.com
@quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlYDE7AACgkQ2ZIOBq0ODEE0ewCePKKKuRTn90ZboHQjuhBaTWE3
m84AnjnljXIkWGYwyJ1d0gjDIbFd4l6q
=Fkd4
-END PGP SIGNATURE-
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: [EPEL-devel] [Proposal] Converge EPEL and CBS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/22/2015 12:18 PM, Dennis Gilmore wrote: > Also, this would probibly be some kind of big deal to some > people who like that EPEL is built against rhel. > Personally, I don't think it matters, but it would have to > be communicated clearly. >>> >>> (I also saw Karsten reply about it) It needs to be >>> communicated, but considering CentOS good history on that >>> matter, I personally don't think it's big deal, too. > It is a much bigger deal politically than technically I agree it's a big deal, but think it's more about 'supportability', which is the crossroads for technical, end-user needs, business dynamics, community capability, and so forth. I personally *like* that Red Hat support has comfort level with pointing customers at EPEL; I don't want that to change. To me that is a core promise from the community to our end-users, wherever they are from. - - Karsten - -- Karsten 'quaid' Wade.^\ CentOS Doer of Stuff http://TheOpenSourceWay.org\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYCDJwACgkQ2ZIOBq0ODEH2QQCg1cBadVBZYMjuAorV0xzjB8gj mIYAn1yiflU1kFwJG1pVOnp3ryuqgMM7 =Ds5V -END PGP SIGNATURE- ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: [EPEL-devel] [CentOS-devel] [Proposal] Converge EPEL and CBS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/21/2015 07:12 AM, Haïkel wrote: > * EPEL will use CentOS repositories instead of mirroring RHEL > repositories Worth noting that one of the values people get (or perceive) about EPEL is that it is built against RHEL repositories. This is really important for people who use EPEL on RHEL, as it makes potential support discussions more clean. Red Hat's support team is more comfortable pointing customers at EPEL solutions knowing that it is build against RHEL rather than CentOS. - - Karsten - -- Karsten 'quaid' Wade.^\ CentOS Doer of Stuff http://TheOpenSourceWay.org\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYAQXAACgkQ2ZIOBq0ODEEOYACfejx2aARIUbAgVKD1ZRR8FNVN uncAn3gvc4n2cKG77zv4KJsu8ARlp87T =CRtU -END PGP SIGNATURE- ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: [EPEL-devel] Meeting face to face CentOS Project and EPEL
On 01/05/2015 12:39 PM, Till Maas wrote: Hi, On Fri, Jan 02, 2015 at 01:27:16AM +, Karanbir Singh wrote: we are working to arrange a meeting with the EPEL folks at Fosdem 2015, on 31st Jan at 7pm ( venue to be confirmed ), to try and workout some options on how the two efforts might best co-ordinate. A key part of the conversation would also focus on how SIGs and other contributors to downstream repos in centos.org can interface with and set expectations on the epel repos. Everyone able to make it please let me know your names so I can track attendance and make reservations accordingly. I would like to join the meeting. I've added you to the list, see you there. Regards, - Karsten -- Karsten 'quaid' Wade.^\ CentOS Doer of Stuff http://TheOpenSourceWay.org\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: [EPEL-devel] [CentOS-devel] Meeting face to face CentOS Project and EPEL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/01/2015 06:59 PM, Brian Stinson wrote: On Jan 02 01:27, Karanbir Singh wrote: hi, crossposting this to centos-devel and epel-devel we are working to arrange a meeting with the EPEL folks at Fosdem 2015, on 31st Jan at 7pm ( venue to be confirmed ), to try and workout some options on how the two efforts might best co-ordinate. A key part of the conversation would also focus on how SIGs and other contributors to downstream repos in centos.org can interface with and set expectations on the epel repos. Everyone able to make it please let me know your names so I can track attendance and make reservations accordingly. Regards, -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc ___ CentOS-devel mailing list centos-de...@centos.org http://lists.centos.org/mailman/listinfo/centos-devel Count me in. Me too! /aol Regards, - - Karsten - -- Karsten 'quaid' Wade.^\ CentOS Doer of Stuff http://TheOpenSourceWay.org\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlSp1P0ACgkQ2ZIOBq0ODEGM5gCaA24vqVeDLzYLY9IITTmPCVh4 euoAnivOxAgupFoIRgw68/PWzy5COVbP =hE/C -END PGP SIGNATURE- ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL EpSCO Email Meeting:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/04/2014 02:05 PM, Jim Perrin wrote: Perhaps this is an issue where a shorter life-cycle expectation needs to be set? For anything related to the new repo, this is an important part of the idea. We want to set a new expectation with the new brand. Maybe we can just tie it to the upstream-of-Fedora -- 13 months, rolls with each Fedora release, etc.? - - Karsten - -- Karsten 'quaid' Wade.^\ CentOS Doer of Stuff http://TheOpenSourceWay.org\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlQI3oUACgkQ2ZIOBq0ODEHT0wCdHjDZPVb5ZDIKCih0dXX6BpWS 7PYAnjviHBnGKnoB5RtgfVJAuyKKWdqI =VI0t -END PGP SIGNATURE- ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL and SCL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/20/2014 05:30 PM, Dennis Jacobfeuerborn wrote: I've never heard of this EPIC repository and google doesn't seem to know it either. Where can this be found? It doesn't exist, it's an idea that Robyn has floated semi-seriously as a way to provide a repo that moves faster than EPEL. Rather than try to jam fast-moving stuff in to EPEL, the idea was to do an Extra Packages for Infrastructure and Cloud (EPIC) that had a different, faster-moving charter. EPIC would target the *EL platform just as EPEL does. For the record, *I* think EPIC is an epic name. - - Karsten - -- Karsten 'quaid' Wade.^\ CentOS Doer of Stuff http://TheOpenSourceWay.org\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMrl2oACgkQ2ZIOBq0ODEH7kQCggq4gnXeYjG5xich1BLbkRwZh KT4An2qmT0p6XO99pMXuFCeQCgsnj/r7 =X822 -END PGP SIGNATURE- ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Summer of Code - time to do something, anything ... but not by me
Folks: For this coming year, if Fedora chooses to participate in the Google Summer of Code (and I think we should), I have decided that I am not going to be involved. This is not complete abandonment. In fact, the below blog post is the first of potentially several that can be part of a package of mentoring-the-mentors as I pass on my mantle of leadership. So if you care about the future of Fedora’s participation in Google Summer of Code (GSoC), for the love of all that you hold dear and then some beyond that, please read on. http://iquaid.org/2010/12/22/summer-of-code-time-to-do-something-anything-but-not-by-me-2/ From the above blog post, summary of what is needed soon: 1. A wiki page that lists project ideas from across the Fedora community. 2. Some folks need to read the application requirements and put a schedule together to meet the deadlines. 3. Work all the application process to completion. Work in the past has been on this list: https://groups.google.com/group/redhat-summer - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team:Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41 pgpabgkgCQ5CU.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
summer coding and you
I'm talking to you because I know some of you work at companies, organizations, foundations, consortiums, and so forth. And you may be in the perfect position to sponsor a student for Fedora Summer Coding. We're moving the schedule back an extra month to give a chance for more sponsors. The proposed schedule gives us until 21 May for sponsors to pledge funds. (Separate announcement about schedule changes coming.) We need word word about Fedora Summer Coding to get to the ears of more people. People who: * Have the desire to help students (learn to) contribute to FOSS the Fedora Project. * Want to associate their name or brand with being a sponsor of these summer coding activities. * (Optionally) care about the future of the Fedora Project; you may be funding work that happens primarily upstream, but it should somehow benefit Fedora. * Can pledge money toward funding students by 21 May 2010. * Are interested in getting in at the start of a new program associated with Fedora. We are already planning how to do a Summer Coding 2010 for the Southern Hemisphere, and entire half of the planet not covered by GSoC. This can be as big as we want to grow it. Is this you? Your company? Spread the word. People should contact me directly, unless they want to be transparent and in public about it. ;-) kw...@redhat.com https://fedoraproject.org/wiki/Summer_Coding_2010#You_are_a_sponsoring_organization Some more writing on this: http://iquaid.org/2010/04/13/sponsoring-summer-coding-get-and-give-value/ http://iquaid.org/2010/04/02/seeking-sponsors-universities-corporations-foundations-individuals-creative-ideas/ Thanks - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team:Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41 pgpaxc9D7KMkS.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
ideas for Summer Coding deadline moved to 14 April
In today's SIG meeting we finalized the Summer Coding 2010 schedule, and that included adding more time for ideas to be listed for students. The new deadline is next Wed. 14 April. We are inviting students to begin working on proposals starting today, with those due on 21 April. https://fedoraproject.org/wiki/Summer_Coding_2010_schedule https://fedoraproject.org/wiki/Summer_Coding_2010_ideas Thanks - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team:Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41 pgpu0vp3fa8hD.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Summer Coding 2010 ideas due 9 April
While we finish the Summer Coding 2010 page (http://bit.ly/FSC-2010), it is past time for you all to let us know the problems you would like to see solved by summer coding/internship students. By Friday 09 April. Idea page is here: https://fedoraproject.org/wiki/Category:Summer_Coding_2010_ideas How-to fill out an ideas page is here: https://fedoraproject.org/wiki/How_to_create_an_idea_page_for_Summer_Coding Let’s get this filled with serious ideas you are willing to mentor for or help find the mentor. Join the discussion list and be prepared to talk about your ideas or proposals. http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss If you were already a mentor and want to help with mentoring, such as proposal reviews, let us know and join the mentors list. http://lists.fedoraproject.org/mailman/listinfo/summer-coding-mentors Tracking these ideas is a PITA and in fact the lack of an ideas page lead to us not getting in the Google Summer of Code this year. This is all part of a larger issue around tracking smaller ideas for beginners and students, but for now this will have to do. Anyone want to hack on OpenHatch.org, please help. We’re hoping some of the functionality we are handling manually may be included in upcoming versions of OpenHatch. If that direction gets us fruit, we may use OpenHatch as an ongoing way to expose projects to students and other new contributors. (This email derived from my post at http://bit.ly/bofYla) - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team:Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41 pgplTQcWDAuiF.pgp Description: PGP signature ___ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
ideas for Summer Coding deadline moved to 14 April
In today's SIG meeting we finalized the Summer Coding 2010 schedule, and that included adding more time for ideas to be listed for students. The new deadline is next Wed. 14 April. We are inviting students to begin working on proposals starting today, with those due on 21 April. https://fedoraproject.org/wiki/Summer_Coding_2010_schedule https://fedoraproject.org/wiki/Summer_Coding_2010_ideas Thanks - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team:Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41 pgpSc7U0MV4zP.pgp Description: PGP signature ___ devel-announce mailing list devel-announce@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce
