On 09. 10. 19 0:27, Stephen John Smoogen wrote:
On Tue, 8 Oct 2019 at 15:49, Irina Boverman
<iboverma(a)redhat.com> wrote:
>
> Ok, how will I know what test results are?
>
> On Tue, Oct 8, 2019 at 2:56 PM Kevin Fenzi <kevin(a)scrye.com> wrote:
>>
>> On Tue, Oct 08, 2019 at 07:54:37PM +0200, Miro Hrončok wrote:
>>> On 08. 10. 19 18:48, Irina Boverman wrote:
>>>> My build (qpid-proton package) cannot find pythin36-devel package, I
>>>> also tried python3-devel (also not found). It appears python36 was
>>>> removed from EPEL 7 recently.
>>>
>>> Yes it was, as it was added to RHEL 7.7.
>>>
>>> The error is:
>>>
https://koji.fedoraproject.org/koji/taskinfo?taskID=38143406
>>> No matching package to install: 'python36-devel'
>>>
>>> It only happens on aarch64. I have no idea what's wrong. EPEL people,
could
>>> you please help?
>>
>> With 7.7 RHEL dropped support for aarch64, so while all the other arches
>> have moved on, aarch64 is stuck at 7.6.
>>
>> We are trying to see if we can keep support for it in epel by using the
>> CentOS 7.7 aarch64 repo. We have just finished syncing those bits over
>> and now we have to try and test it.
>>
>> So, options:
>>
>> 1) wait and let us test and see what the outcome is.
>>
>> 2) ExcludeArch: aarch64 for now and then pay attention to how the
>> testing comes out, if it works, drop your ExcludeArch.
>>
>> kevin
The test results were that we can keep running aarch64 in EPEL-7. Koji
assumes that same name packages are the same in every repository and
will fail if they aren't. Trying to do any build failed with the
CentOS-7 packages because the filesystem (and every other noarch RPM)
had different hashes. [I am pretty sure Dennis Gilmore will be saying
'yes and I told you this would happen when you wanted to do this 5
years ago'] At this point we will be disabling aarch64 from EPEL-7 and
freezing those repositories.
So should the python36 package had stayed in the frozen repo? Are we going to
unretire it once again?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok