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

solvespace: New Package #22758

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Kreijstal
Copy link
Contributor

the 1487.patch refers to the PR, and because this patch is on release it will not exactly work for the tagged version, so the 002*.patch is a hotfix which should be removed whenever they tag a new version.

@Kreijstal Kreijstal marked this pull request as draft December 7, 2024 14:33
@Biswa96 Biswa96 added the new-package Pull request which adds new package(s) label Dec 7, 2024
@Kreijstal Kreijstal marked this pull request as ready for review December 7, 2024 15:00
Comment on lines +34 to +35
patch -N -p1 -i "${srcdir}/1487.patch" || true
patch -N -p1 -i "${srcdir}/002-not-in-msys2-temp.patch" || true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why the "|| true" ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the first patch is from PR but it's from upstream which is not the version we are packaging, the rejects are then fixed/backported in 002-not-in-msys2-temp.patch, however the second one a || true is not necessary, you're right.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd argue it doesn't make sense in both cases. It shouldn't fail, and if it does we want to know.

Copy link
Contributor Author

@Kreijstal Kreijstal Dec 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I can manually remove the reject chunks, however they might be necessary on a later version

@lazka
Copy link
Member

lazka commented Dec 8, 2024

the resulting package is empty, so something is broken in the package() phase

@Kreijstal Kreijstal marked this pull request as draft December 8, 2024 17:11
@Kreijstal
Copy link
Contributor Author

the resulting package is empty, so something is broken in the package() phase

It seems it's an upstream problem..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-package Pull request which adds new package(s)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants