On Tue, 27 Nov 2018, Manuel Wolfshant wrote:
On 11/27/18 3:45 PM, me(a)tdiehl.org wrote:
> On Mon, 26 Nov 2018, Stephen John Smoogen wrote:
>
>> On Mon, 26 Nov 2018 at 11:00, Christopher <ctubbsii(a)fedoraproject.org>
>> wrote:
>>>
>>> On Mon, Nov 26, 2018 at 7:12 AM Stephen John Smoogen
<smooge(a)gmail.com>
>>> wrote:
>>>>
>>>> On Mon, 26 Nov 2018 at 01:03, Christopher
<ctubbsii(a)fedoraproject.org>
>>>> wrote:
>>>>>
>>>>> Anybody know what's going on with Centos 7.6-1810?
>>>>> Some packages in EPEL depend on it, but it is apparently not yet
>>>>> available.
>>>>> This discrepancy is breaking yum updates for me.
>>>>>
>>>>
>>>> This isn't a Fedora development issue. Please refer this to the
CentOS
>>>> or EPEL lists.
>>>>
>>>
>>> EPEL is a Fedora project. My question wasn't really about CentOS, but
>>> rather, about maintainer best practices for EPEL branches. To clarify,
>>> my question is whether package maintainers are expected to ensure
>>> their EPEL branch for their packages works against the latest CentOS
>>> release (without enabling 'cr' repo) or whether it is expected that
>>> packages will work as soon as the corresponding RHEL release is
>>> available (which is usually available about 3-4 weeks earlier). What
>>> do we use for the EPEL buildroot in koji?
>>>
>>
>> Even though EPEL is a Fedora project, the main development and work is
>> done on the epel-devel(a)lists.fedoraproject.org mailing list.
>>
>> EPEL is built from the 'current' state of Red Hat Enterprise Linux as
>> synced from 'rhn (or whatever they call it these days)' every 12
>> hours. This means that CentOS users must use CR during the
>> intermediate time.
>
> Based on the above, can you tell me if the following yum errors are
> caused by epel or the centos cr repo mising the proper deps?
>
> (tigger pts9) # yum clean metadata ; yum update
> Loaded plugins: changelog, fastestmirror, langpacks, priorities
> Cleaning repos: base cr epel extras fasttrack google-chrome nux-dextop
> updates
> 27 metadata files removed
> 9 sqlite files removed
> 0 metadata files removed
> Loaded plugins: changelog, fastestmirror, langpacks, priorities
> Loading mirror speeds from cached hostfile
> base | 3.6 kB? 00:00:00 cr | 3.4 kB? 00:00:00 epel | 3.2 kB? 00:00:00
> extras | 3.4 kB? 00:00:00 fasttrack | 3.3 kB? 00:00:00 google-chrome | 1.3
> kB? 00:00:00 nux-dextop | 2.9 kB? 00:00:00 updates | 3.4 kB? 00:00:00
> (1/14):
I notice that you did not enable the epel-testing repository. Can you please
retry after enabling it ?
AAH, that was it. I forgot about the testing repo. :-)
Thanks for the help.
Regards,
--
Tom me(a)tdiehl.org