Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sci-libs/med: fix build against hdf5-1.12 #22096

Closed
wants to merge 2 commits into from

Conversation

waebbl
Copy link
Contributor

@waebbl waebbl commented Aug 24, 2021

Thanks to Alexandre Ferreira for providing the patch.

Closes: https://bugs.gentoo.org/809008
Package-Manager: Portage-3.0.20, Repoman-3.0.3
Signed-off-by: Bernd Waibel waebbl-gentoo@posteo.net

profiles/base/package.use.mask: mask mpi for sci-libs/med

Package depends on sci-libs/hdf5[mpi] which currently has test issues
and has USE=mpi masked.

Package depends on sci-libs/hdf5[mpi] which currently has test issues
and has USE=mpi masked.

Signed-off-by: Bernd Waibel <waebbl-gentoo@posteo.net>
Thanks to Alexandre Ferreira for providing the patch.

Closes: https://bugs.gentoo.org/809008
Package-Manager: Portage-3.0.20, Repoman-3.0.3
Signed-off-by: Bernd Waibel <waebbl-gentoo@posteo.net>
@gentoo-bot
Copy link

Pull Request assignment

Submitter: @waebbl
Areas affected: ebuilds, profiles
Packages affected: sci-libs/med

sci-libs/med: @tamiko, @waebbl, @gentoo/sci, @gentoo/proxy-maint

Linked bugs

Bugs linked: 809008


In order to force reassignment and/or bug reference scan, please append [please reassign] to the pull request title.

Docs: Code of ConductCopyright policy (expl.) ● DevmanualGitHub PRsProxy-maint guide

@gentoo-bot gentoo-bot added self-maintained The PR changes only packages that are maintained by the submitter (i.e. no need to ask anybody else) assigned PR successfully assigned to the package maintainer(s). bug linked Bug/Closes found in footer, and cross-linked with the PR. labels Aug 24, 2021
@gentoo-repo-qa-bot
Copy link
Collaborator

Pull request CI report

Report generated at: 2021-08-24 21:14 UTC
Newest commit scanned: 0007742
Status: ✅ good

There are existing issues already. Please look into the report to make sure none of them affect the packages in question:
https://qa-reports.gentoo.org/output/gentoo-ci/1ebce39953/output.html

@AndrewAmmerlaan
Copy link
Member

Thanks 👍

@waebbl waebbl deleted the med-hdf5-cmake-fix branch August 25, 2021 06:21
@waebbl
Copy link
Contributor Author

waebbl commented Aug 25, 2021

@AndrewAmmerlaan Andrew, can you revert this? I just got an email that the mask breaks gmsh. Haven't tested the revdeps on this.

@waebbl waebbl restored the med-hdf5-cmake-fix branch August 25, 2021 06:45
@AndrewAmmerlaan
Copy link
Member

@AndrewAmmerlaan Andrew, can you revert this? I just got an email that the mask breaks gmsh. Haven't tested the revdeps on this.

Reverted, I'm slightly confused though, because the qa-bot said it was fine

@waebbl
Copy link
Contributor Author

waebbl commented Aug 25, 2021

@AndrewAmmerlaan Andrew, can you revert this? I just got an email that the mask breaks gmsh. Haven't tested the revdeps on this.

Reverted, I'm slightly confused though, because the qa-bot said it was fine

Does it check for revdeps? Just looked up latest gmsh and noticed it depends on med[mpi] unconditionally and has a REQUIRED_USE=med? ( mpi ) constraint. Looks, like we need to mask the med USE flag on gmsh as well.

Need to figure out how to re-track the branch again. Already deleted it locally :/

@AndrewAmmerlaan
Copy link
Member

Does it check for revdeps? Just looked up latest gmsh and noticed it depends on med[mpi] unconditionally and has a REQUIRED_USE=med? ( mpi ) constraint. Looks, like we need to mask the med USE flag on gmsh as well.

It should, it checks the whole tree. Possibly your local tree was significantly behind the main tree?

@waebbl
Copy link
Contributor Author

waebbl commented Aug 25, 2021

It should, it checks the whole tree. Possibly your local tree was significantly behind the main tree?

No, I don't think so. I always rebase before pushing, so the local tree was up to date.

@waebbl
Copy link
Contributor Author

waebbl commented Aug 25, 2021

Just checked the gmsh-4.8.4 build file. From my understanding the packages doesn't need to have mpi support for med enabled unconditionally. So instead of masking gmsh[med] as well, I suggest to change the dependency on sci-libs/med of all gmsh versions starting 4.6.0 and above from sci-libs/med[mpi] to sci-libs/med[mpi=] which should resolve the break.

@waebbl
Copy link
Contributor Author

waebbl commented Aug 26, 2021

@AndrewAmmerlaan I noticed, that med will silently downgrade hdf5 to v1.10 whenever USE=mpi is passed to the ebuild. So we don't even need the mask and everything is fine. What do you think? Is this ok, the way it is?

@AndrewAmmerlaan
Copy link
Member

@AndrewAmmerlaan I noticed, that med will silently downgrade hdf5 to v1.10 whenever USE=mpi is passed to the ebuild. So we don't even need the mask and everything is fine. What do you think? Is this ok, the way it is?

The issue with mpi is only present in >=1.12? In that case, can we not just mask the mpi flag for only 1.12+?

@waebbl
Copy link
Contributor Author

waebbl commented Aug 26, 2021

The issue with mpi is only present in >=1.12? In that case, can we not just mask the mpi flag for only 1.12+?

The mask is already for >=hdf5-.1.12.1 only.

@AndrewAmmerlaan
Copy link
Member

The issue with mpi is only present in >=1.12? In that case, can we not just mask the mpi flag for only 1.12+?

The mask is already for >=hdf5-.1.12.1 only.

Sorry, I'm a bit confused, if the mask is only on 1.12 then why do we need to mask mpi on med in the first place? We could just use the older version of hdf5 with mpi enabled to satisfy the dependency right?

@waebbl
Copy link
Contributor Author

waebbl commented Aug 26, 2021

The issue with mpi is only present in >=1.12? In that case, can we not just mask the mpi flag for only 1.12+?

The mask is already for >=hdf5-.1.12.1 only.

Sorry, I'm a bit confused, if the mask is only on 1.12 then why do we need to mask mpi on med in the first place? We could just use the older version of hdf5 with mpi enabled to satisfy the dependency right?

Yeah that's what I wanted to say in this comment.

@AndrewAmmerlaan I noticed, that med will silently downgrade hdf5 to v1.10 whenever USE=mpi is passed to the ebuild. So we don't even need the mask and everything is fine. What do you think? Is this ok, the way it is?

Guess I didn't realize this in the first place.

@waebbl waebbl deleted the med-hdf5-cmake-fix branch August 26, 2021 18:27
@AndrewAmmerlaan
Copy link
Member

The issue with mpi is only present in >=1.12? In that case, can we not just mask the mpi flag for only 1.12+?

The mask is already for >=hdf5-.1.12.1 only.

Sorry, I'm a bit confused, if the mask is only on 1.12 then why do we need to mask mpi on med in the first place? We could just use the older version of hdf5 with mpi enabled to satisfy the dependency right?

Yeah that's what I wanted to say in this comment.

Aaah right, now I get it :P

I think it is fine as is in that case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
assigned PR successfully assigned to the package maintainer(s). bug linked Bug/Closes found in footer, and cross-linked with the PR. self-maintained The PR changes only packages that are maintained by the submitter (i.e. no need to ask anybody else)
Projects
None yet
4 participants