[CentOS-devel] Community build services and EPEL8

Neal Gompa ngompa13 at gmail.com
Wed Jul 24 21:14:40 UTC 2019


On Wed, Jul 24, 2019 at 4:59 PM Stephen John Smoogen <smooge at gmail.com> wrote:
>
>
>
> On Wed, 24 Jul 2019 at 16:51, Phil Perry <pperry at elrepo.org> wrote:
>>
>> On 24/07/2019 19:53, Matthew Miller wrote:
>> > On Fri, Jul 12, 2019 at 11:35:39AM -0500, Johnny Hughes wrote:
>> >> The issue is .. they change the versions out and you then lose that
>> >> package.  next build it fails with the new one .. what do you do?  The
>> >> old package is no longer available anywhere.
>> >
>> > One thing that can help here is to not treat the EPEL maintainers as an
>> > opaque "they". It's actually people you can talk directly to, and who should
>> > have your concerns as a consumer in mind. You could even become a
>> > comaintainer of the package.
>> >
>> >
>>
>> The issue here is not related to maintainers of a given package, but
>> rather one of EPEL policy whereby only the latest release of each
>
>
> s/policy/buildsystem/
>
> There isn't a policy about this beyond we use the tools we have, and those tools are built around composing a release.
>

Specifically, Bodhi pulls all the latest updates marked for stable or
are stable and sucks them in to produce a repository. It doesn't work
like dist-repos where you can tag in multiple EVRs of a package to
push out. Maybe one day this will be fixed, but I'm not sure that's
anytime soon...



-- 
真実はいつも一つ!/ Always, there's only one truth!


More information about the CentOS-devel mailing list