Hi Bjarne,
Just the other day I was again looking at atlas. I still cannot
build it. I was however planning on a different solution than your
proposal below. I thought to build atlas from RSEL7 and include
that in RSEL8.
The version in RSEL7 is 3.10.1, while the RH8 version is 3.10.3. I am not aware of any security issues or major changes between those versions, so I expect this to work (This is how numpy was build to start with ...)
Would this suit your case also?
Of course, I can patch openblas anyway, although I don't have many items depending on it (only opencv and that one is also missing 3 other packages)
I'll try to get old atlas on the mirrors by midnight.
Jacco
--
You received this message because you are subscribed to the Google Groups "redsleeve-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redsleeve-use...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/AM0PR05MB58890B10AE8CAE07030A6C14C2A80%40AM0PR05MB5889.eurprd05.prod.outlook.com.
I'm getting more puzzled by atlas: atlas from RSEL7 does not
build on RSEL8. If interested, I put the buildlog also in the
FTBFS directory.
So now I'm trying to build the new atlas on RSEL7. Let's see if
that works.
Normally I would also try to build something on x86, but I still
don't have a decent x86 test machine with either rhel8 or C8
(epel8 is also still largely missing)
For good measure: openblas is now also building.
to be continued.
Jacco
To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/AM0PR05MB5889BF80297851B0B980A45CC2A80%40AM0PR05MB5889.eurprd05.prod.outlook.com.
Hi Bjarne,
openblas and numpy are in place as you requested (sync to mirrors expected around 08:00 UTC)
I knew that there were a couple of packets requiring atlas. For that reason I preferred keeping atlas around. However I did not know that most of these requirements were actually through numpy and that numpy had atlas listed as a second choice.
I am now in favor of ditching atlas all together. It has always been difficult to build and the latest version keeps giving errors building, both on RSEL7 and RSEL8. The only thing I can see that natively depends on atlas is suitesparse. And suitesparse is apparently only needed by gegl and gegl04. Nothing depends on those.
My proposal is to also drop the items listed above. If we really need them, we can adjust suitesparse to build against openblas, this has been done by fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1506933
Jacco
To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/23bda804-b234-2d24-0e90-9e773b30c937%40redsleeve.org.
Sendt fra Outlook
Oops.
fixed and awaiting sync to mirrors.
Jacco
To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/AM0PR05MB58894ABD9E67FC33BCC112E8C2A50%40AM0PR05MB5889.eurprd05.prod.outlook.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/AM0PR05MB58899A254B1B8E73CCD603DAC28A0%40AM0PR05MB5889.eurprd05.prod.outlook.com.
> To unsubscribe from this group and stop receiving emails from it, send an emailtoredsleeve-us...@googlegroups.com<mailto:redsleeve-use...@googlegroups.com>.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/AM0PR05MB58890B10AE8CAE07030A6C14C2A80%40AM0PR05MB5889.eurprd05.prod.outlook.com<https://groups.google.com/d/msgid/redsleeve-users/AM0PR05MB58890B10AE8CAE07030A6C14C2A80%40AM0PR05MB5889.eurprd05.prod.outlook.com?utm_medium=email&utm_source=footer>.
> --
> You received this message because you are subscribed to the Google Groups "redsleeve-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an emailtoredsleeve-us...@googlegroups.com<mailto:redsleeve-use...@googlegroups.com>.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/21c7a94e-827e-bd1a-aa05-c7eaf06180ea%40redsleeve.org<https://groups.google.com/d/msgid/redsleeve-users/21c7a94e-827e-bd1a-aa05-c7eaf06180ea%40redsleeve.org?utm_medium=email&utm_source=footer>.
> --
> You received this message because you are subscribed to the Google Groups "redsleeve-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email toredsleeve-use...@googlegroups.com<mailto:redsleeve-use...@googlegroups.com>.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/AM0PR05MB5889BF80297851B0B980A45CC2A80%40AM0PR05MB5889.eurprd05.prod.outlook.com<https://groups.google.com/d/msgid/redsleeve-users/AM0PR05MB5889BF80297851B0B980A45CC2A80%40AM0PR05MB5889.eurprd05.prod.outlook.com?utm_medium=email&utm_source=footer>.
> --
> You received this message because you are subscribed to the Google Groups "redsleeve-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email toredsleeve-use...@googlegroups.com<mailto:redsleeve-use...@googlegroups.com>.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/23bda804-b234-2d24-0e90-9e773b30c937%40redsleeve.org<https://groups.google.com/d/msgid/redsleeve-users/23bda804-b234-2d24-0e90-9e773b30c937%40redsleeve.org?utm_medium=email&utm_source=footer>.
>
> --
> You received this message because you are subscribed to the Google Groups "redsleeve-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email toredsleeve-use...@googlegroups.com<mailto:redsleeve-use...@googlegroups.com>.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/9a39d6ad-dc85-7ef2-4371-42308369737f%40redsleeve.org<https://groups.google.com/d/msgid/redsleeve-users/9a39d6ad-dc85-7ef2-4371-42308369737f%40redsleeve.org?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "redsleeve-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email toredsleeve-use...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/redsleeve-users/74c2-5d5bf680-9-5a738500%40160459977.
Hi Gordan.
I am not sure what you mean. Can you are a config example?
And koji is a little funky. It generate its own mock config for each build it does. And its a combination of a merge of the build servers /etc/mock/site-default.cfg, config from koji and hardcoded config in koji’s python code.I had to ad aaaalot of debug logging to figure out what came from where :(