It seems the command to create a YUM/DNF repository on a Fedora system is not compatible with YUM/DNF on CentOS 7, so the latter can't read the repository information produced by the former.
I have now recreated the repository using CentOS 7, and it looks like it is now possible to install on CentOS 7.
On 29/12/2023 18.37, Ariel Abadi wrote:
Hi! Im trying to install the latest version of Monetdb, and seems the repo has an error.
Can anyone help!? or had an idea how to solve this?
[root@tc-mn monetdb]# yum update Loaded plugins: fastestmirror Determining fastest mirrors epel/x86_64/metalink
| 32 kB 00:00:00 * epel: mirror.de.leaseweb.net http://mirror.de.leaseweb.net base
| 3.6 kB 00:00:00 epel
| 4.7 kB 00:00:00 extras
| 2.9 kB 00:00:00 monetdb
| 1.5 kB 00:00:00 updates
| 2.9 kB 00:00:00 (1/5): epel/x86_64/group_gz
| 100 kB 00:00:00 (2/5): epel/x86_64/updateinfo
| 1.0 MB 00:00:00 (3/5): monetdb/7/x86_64/primary
| 120 kB 00:00:00 (4/5): updates/7/x86_64/primary_db
| 24 MB 00:00:00 (5/5): epel/x86_64/primary_db
| 7.0 MB 00:00:01
One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ...
4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage:
yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid>
5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise:
yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Parsing primary.xml error: Start tag expected, '<' not found
[root@tc-mn monetdb]#
users-list mailing list -- users-list@monetdb.org To unsubscribe send an email to users-list-leave@monetdb.org