Hi!
I am new... maybe renew to Fedora.
As I am not 'yet' a packager... I find COPR nice for developing my packaging skills.
I began to use copr-cli to submit my 7kaa.spec file... Hope I will be able to use it even if I have patchs too...
I have worked on upgrading the orphaned 7kaa game to latest version.
While testing some architectures I don't know much, I am surprised that my build did succeed, but I see no rpm generated.
See: https://copr.fedorainfracloud.org/coprs/pauld/7kaa/build/1323133/ https://copr.fedorainfracloud.org/coprs/pauld/7kaa/build/1323138/
Is there something I don't get?
With more traditional architectures, the rpm was generated: Example, on: https://copr.fedorainfracloud.org/coprs/pauld/7kaa/build/1322733/ I see the rpms in: https://download.copr.fedorainfracloud.org/results/pauld/7kaa/fedora-32-x86_...
Hi Paul,
I'm not sure what you mean, I see rpms in both of the builds you mentioned:
https://download.copr.fedorainfracloud.org/results/pauld/7kaa/fedora-32-aarc... https://download.copr.fedorainfracloud.org/results/pauld/7kaa/fedora-32-armh...
Is there anything wrong with the rpms? Can you elaborate more on what's wrong?
Thanks, Dominik
On Sun, Mar 29, 2020 at 6:46 PM Paul Dufresne dufresnep@zoho.com wrote:
Hi!
I am new... maybe renew to Fedora.
As I am not 'yet' a packager... I find COPR nice for developing my packaging skills.
I began to use copr-cli to submit my 7kaa.spec file... Hope I will be able to use it even if I have patchs too...
I have worked on upgrading the orphaned 7kaa game to latest version.
While testing some architectures I don't know much, I am surprised that my build did succeed, but I see no rpm generated.
See: https://copr.fedorainfracloud.org/coprs/pauld/7kaa/build/1323133/ https://copr.fedorainfracloud.org/coprs/pauld/7kaa/build/1323138/
Is there something I don't get?
With more traditional architectures, the rpm was generated: Example, on: https://copr.fedorainfracloud.org/coprs/pauld/7kaa/build/1322733/ I see the rpms in:
https://download.copr.fedorainfracloud.org/results/pauld/7kaa/fedora-32-x86_... _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.o...
Le 20-04-01 à 13 h 00, Dominik Turecek a écrit :
Hi Paul,
I'm not sure what you mean, I see rpms in both of the builds you mentioned:
Oh! Yes indeed they are there ... now. I guess they where not showing just after the build was reported successful.
Sorry for the disturbance.
No problem, I'm glad it works now.
Dominik
On Wed, Apr 1, 2020 at 8:07 PM Paul Dufresne dufresnep@zoho.com wrote:
Le 20-04-01 à 13 h 00, Dominik Turecek a écrit :
Hi Paul,
I'm not sure what you mean, I see rpms in both of the builds you mentioned:
Oh! Yes indeed they are there ... now. I guess they where not showing just after the build was reported successful.
Sorry for the disturbance.
On Wednesday, April 1, 2020 8:05:02 PM CEST Paul Dufresne wrote:
Le 20-04-01 à 13 h 00, Dominik Turecek a écrit :
Hi Paul,
I'm not sure what you mean, I see rpms in both of the builds you mentioned:
Oh! Yes indeed they are there ... now. I guess they where not showing just after the build was reported successful.
That's possible indeed; we use the AWS cloudfronts for caching the http directories, including directory listing ... which causes a confusion.
DNF/YUM doesn't read the directory listing, they read 'repomd.xml' which references other metadata files which reference the RPMs. So the repositories aren't broken.
Pavel
copr-devel@lists.fedorahosted.org