Failing to sync external repos for some chroots

[Guilherme Cardoso]

Hi!
I'm trying to build a new version with external repositories for nodejs. Depending on
the chroot the connectivity fails.

For example, successful build:
https://copr.fedorainfracloud.org/coprs/luminoso/Signal-Desktop/build/741...

Unsuccessful build, no matter how many times I submit:
https://copr.fedorainfracloud.org/coprs/luminoso/Signal-Desktop/build/741...

builder-live shows the following:
Failed to synchronize cache for repo
'https_rpm_nodesource_com_pub_8_x_el_releasever_basearch', disabling.
Failed to synchronize cache for repo
'https_rpm_nodesource_com_pub_8_x_fc_releasever_basearch', disabling.
Failed to synchronize cache for repo
'https_rpm_nodesource_com_pub_8_x_el_27_basearch', disabling.

which makes the build to fail afterward.  Any ideas what's going on?

[Michal Novotny]

Hello Guilherme,

e.g. this repo source:

https://rpm.nodesource.com/pub_8.x/el/
(https_rpm_nodesource_com_pub_8_x_el_releasever_basearch)

is only valid for epel chroots and should be only added for those (see
'Edit' link for individual chroots in project settings).

The repo with id https_rpm_nodesource_com_pub_8_x_el_27_basearch uses
https://rpm.nodesource.com/pub_8.x/el/27/$basearch link
but https://rpm.nodesource.com/pub_8.x/el/27/ gives 404.

So there are some problems with the repo setup.

An important repo is https://rpm.nodesource.com/pub_8.x/fc/, which provides
nodejs for Fedora with npm bundled but only up to f27. f28 and rawhide
builds will therefore fail. Also fedora-27-i386 is failing because dnf, for
some reason, prefers (probably because of the Arch field):

Name         : nodejs
Epoch        : 1
Version      : 8.11.0
Release      : 1.fc27
Arch         : i686

over:

Name         : nodejs
Epoch        : 2
Version      : 8.11.1
Release      : 1nodesource
Arch         : i386

I would suggest to use npm from official Fedora repositories or you can ask
maintainers of rpm.nodesource.com to
provide updated rpms (for f28 and f29).

Best Regards!
clime

On Sat, Apr 14, 2018 at 7:27 PM, Guilherme Cardoso <gjc(a)ua.pt&gt; wrote:

>  Hi!
>  I'm trying to build a new version with external repositories for nodejs.
>  Depending on the chroot the connectivity fails.
>
>  For example, successful build:
>  https://copr.fedorainfracloud.org/coprs/luminoso/Signal-
>  Desktop/build/741053/
>
>  Unsuccessful build, no matter how many times I submit:
>  https://copr.fedorainfracloud.org/coprs/luminoso/Signal-
>  Desktop/build/741061/
>
>  builder-live shows the following:
>  Failed to synchronize cache for repo
> 'https_rpm_nodesource_com_pub_8_x_el_releasever_basearch',
>  disabling.
>  Failed to synchronize cache for repo
> 'https_rpm_nodesource_com_pub_8_x_fc_releasever_basearch',
>  disabling.
>  Failed to synchronize cache for repo
> 'https_rpm_nodesource_com_pub_8_x_el_27_basearch',
>  disabling.
>
>  which makes the build to fail afterward.  Any ideas what's going on?
>  _______________________________________________
>  copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
>  To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org
>

[Guilherme Cardoso]

Thank you for the fast reply.

Having those external repositories should be a problem because:

1)
epel, uses the repo
"https://rpm.nodesource.com/pub_8.x/el/$releasever/$basearch" and the other ones
will fail.
works as expected

2)
fedora-27-i386 --> has a nodejs repo, still fails and disables it. It should have used
"https://rpm.nodesource.com/pub_8.x/fc/$releasever/$basearch" repo
does not work as expected. this is the particular case where the repo should have been
downloaded but fails like it was offline

3)
fedora-28 and rawhide --> does not have a repo, but hits on the fc/27/ repo



I can, indeed, configure repo for fedora epel 7 and fedora 26 and use fedora own's
version of npm/nodejs for fedora 27 up to rawhide.
Nevertheless, I'm taking your suggestion and have two rpm specs for different
chroots.
Thank you.