Forked project

[Antonio Trande]

Hi all.

This [1] is a forked project of python3.8 [2]; inside there are all
forked packages previously built but, if i require a new build for
testing Python 3.8, are not used the packages from the project [3] (i
see Python 3.7.3 as dependency).

What am I doing wrong?

[1] https://copr.fedorainfracloud.org/coprs/sagitter/python3.8/
[2] https://copr.fedorainfracloud.org/coprs/g/python/python3.8/
[3]
https://copr-be.cloud.fedoraproject.org/results/sagitter/python3.8/fedora...

Regards.
-- 
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG key: 0x6e0331dd1699e4d7
GPG key server: https://keys.fedoraproject.org/

[Miro Hrončok]

On 10. 04. 19 12:38, Antonio Trande wrote:
>  Hi all.
>  
>  This [1] is a forked project of python3.8 [2]; inside there are all
>  forked packages previously built but, if i require a new build for
>  testing Python 3.8, are not used the packages from the project [3] (i
>  see Python 3.7.3 as dependency).
>  
>  What am I doing wrong? 
Maybe it takes time before the repo is properly generated?

As a workaround, you can (instead of forking or additionally to forking) add the 
original Copr repo as "external repository" in project settings.

https://copr-be.cloud.fedoraproject.org/results/@python/python3.8/fedora-...

-- 
Miro Hrončok
--
Phone: [phone]
IRC: mhroncok

[Robert-André Mauchin]

On Wednesday, 10 April 2019 12:38:08 CEST Antonio Trande wrote:
>  Hi all.
>  
>  This [1] is a forked project of python3.8 [2]; inside there are all
>  forked packages previously built but, if i require a new build for
>  testing Python 3.8, are not used the packages from the project [3] (i
>  see Python 3.7.3 as dependency).
>  
>  What am I doing wrong?
>  
>  [1] https://copr.fedorainfracloud.org/coprs/sagitter/python3.8/
>  [2] https://copr.fedorainfracloud.org/coprs/g/python/python3.8/
>  [3]
>  https://copr-be.cloud.fedoraproject.org/results/sagitter/python3.8/fedora-ra
>  whide-x86_64/00881156-future/
>  
>  Regards. 
All the packages are 404, for example https://copr-be.cloud.fedoraproject.org/
results/sagitter/python3.8/
I guess the forking process didn't work correctly.

[Antonio Trande]

On 10/04/19 12:51, Miro Hrončok wrote:
>  
>  Maybe it takes time before the repo is properly generated?
>  
>  As a workaround, you can (instead of forking or additionally to forking)
>  add the original Copr repo as "external repository" in project settings.
>  
>
> https://copr-be.cloud.fedoraproject.org/results/@python/python3.8/fedora-...
>  
>   
Setting external repository is working.
Thanks.

-- 
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG key: 0x6e0331dd1699e4d7
GPG key server: https://keys.fedoraproject.org/

[Pavel Raiskup]

Hi Antonio,

>  This [1] is a forked project of python3.8 [2]; inside there are all
>  forked packages previously built but, if i require a new build for
>  testing Python 3.8, are not used the packages from the project [3] (i
>  see Python 3.7.3 as dependency).
>  
>  What am I doing wrong? 
This seems to be a copr bug, I created an issue:
https://pagure.io/copr/copr/issue/652

Pavel

> [1] https://copr.fedorainfracloud.org/coprs/sagitter/python3.8/
> [2] https://copr.fedorainfracloud.org/coprs/g/python/python3.8/
> [3]
https://copr-be.cloud.fedoraproject.org/results/sagitter/python3.8/fedora...
> 
> Regards.