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

Please upgrade frontier_client to 2.10.1 #8446

Closed
cvuosalo opened this issue Apr 18, 2023 · 5 comments · Fixed by #8447
Closed

Please upgrade frontier_client to 2.10.1 #8446

cvuosalo opened this issue Apr 18, 2023 · 5 comments · Fixed by #8447
Assignees

Comments

@cvuosalo
Copy link

Please update frontier_client to version 2.10.1. Here are the release notes.
This new version includes the Python bindings and patch that are added by CMSSW. These additions by CMSSW are no longer needed, since they are now included in frontier_client 2.10.1 itself

@cmsbuild
Copy link
Contributor

A new Issue was created by @cvuosalo Carl Vuosalo.

@Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

@iarspider iarspider self-assigned this Apr 18, 2023
@iarspider iarspider linked a pull request Apr 18, 2023 that will close this issue
@iarspider
Copy link
Contributor

@cvuosalo could you please also incorporate this fix and tag a new version? Thanks!

@cvuosalo
Copy link
Author

@iarspider I don't understand the requested change. It is not compatible with the version of pacparser.h that we are using.

@iarspider
Copy link
Contributor

@cvuosalo understood. We will apply the fix on our side then. Out of curiosity, is there any particular reason why you are using old (<= 1.3.8) version of pacparser?

@DrDaveD
Copy link

DrDaveD commented Apr 24, 2023

We just hadn't gotten around to updating it. We could include it in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants