Package Base Details: med-openmpi

Git Clone URL: (read-only, click to copy)
Submitter: mortbauer
Maintainer: Nim65s
Last Packager: Nim65s
Votes: 3
Popularity: 0.000012
First Submitted: 2014-05-06 15:15
Last Updated: 2021-01-01 10:17

Latest Comments

1 2 3 Next › Last »

Rhinoceros commented on 2021-01-02 23:03

Ah that might be it. Thanks @Nim65s!

Nim65s commented on 2021-01-02 09:09

I just upgraded from 4.0.0 to 4.1.0, following community/med. So I guess that fix was upstream :)

Rhinoceros commented on 2021-01-01 23:25

Thanks @frankspace. I just rebuilt to check and this time it created all three files. Previously it just created the other two. Not sure what's going on, but it seems fine now. Sorry for the noise!

frankspace commented on 2021-01-01 17:35

For whatever it's worth, I just compiled the latest version of this (med-openmpi 4.1.0-1), and for me at least, it does actually install /usr/lib/, /usr/lib/, and /usr/lib/

Rhinoceros commented on 2021-01-01 10:18

Yeah apparently not @Nim65s. import Meshpart complained about missing specifically. I can get the precise error message if you want, but I installed med instead, and the absence of that file was one difference I noticed.

Nim65s commented on 2021-01-01 10:08

There is /usr/lib/ and /usr/lib/ Isn't it enough ?

By the way, I handed over the med package to @xyproto so that he could include it in community, so there are no reason for me to keep maintaining med-openmpi. If anybody wants to adopt it, don't hesitate to ask :)

Rhinoceros commented on 2021-01-01 04:39

I had some problems with freecad and this package. med correctly installs /usr/lib/, but this package med-openmpi does not. Without this file, I cannot import MeshPart.

potatoe commented on 2020-08-30 15:50

Is replaces=('med') correct for this package? Or would just conflicts and provides be enough (e.g. this is an alternative and either med or med-openmpi can be chosen but not both together)? My understanding is replaces means the med package is obsolete (and presumably should be removed from AUR now that this exists as a replacement), and the replaces flags is there to ensure everybody is automatically updated to this new replacement package med-openmpi. The wiki describes it as being "An array of obsolete packages that are replaced by the package" and points out pacman "will immediately replace an installed package upon encountering another package with the matching replaces", and suggests using only conflicts and provides if it's just an alternate version.

One of the unofficial user repositories, andontie-aur, includes prebuilt packages for both med and med-openmpi now and as such my pacman wants to automatically replace med with med-openmpi. Is that intended / the correct approach with med-openmpi vs med?

Nim65s commented on 2020-04-28 08:16

Thanks @jedbrown. I applied that to med & med-openmpi.

jedbrown commented on 2020-04-28 05:07

This is currently broken with hdf5-1.12 from community. This gist applies the patch I developed for PETSc, which has been using it for the past several weeks.