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 backport frontier_client 2.8.14 and pacparser 1.3.5 to older CMSSW release lines #1952

Closed
DrDaveD opened this issue Nov 11, 2015 · 12 comments

Comments

@DrDaveD
Copy link

DrDaveD commented Nov 11, 2015

frontier_client 2.8.14 adds IPv6 support. It has been available for a while now in CMSSW_7_6_x without any problems shown. I would like to request that this now get backported to older release lines that are expected to be in active use and supported for at least the next year. I make this request because it seems likely to me that over the next year people will start to want to be using IPv6-only configurations, and not only for the latest CMSSW release line or later. The earlier we start to have the support built in to CMSSW, the easier it will be when someone is ready to start using it.

@ghost
Copy link

ghost commented Nov 12, 2015

I've created a PR for every relevant 7*X release here: #1956 #1957 #1958.
@davidlange6 For which of those do we want to include it? All?

@DrDaveD DrDaveD changed the title Please backport frontier_client 2.8.14 to older CMSSW release lines Please backport frontier_client 2.8.14 and pacparser 1.3.5 to older CMSSW release lines Nov 13, 2015
@DrDaveD
Copy link
Author

DrDaveD commented Nov 13, 2015

I am very sorry I had forgotten to say originally that frontier_client 2.8.14 also should be paired with pacparser 1.3.5. Fortunately you had remembered anyway.

@ghost
Copy link

ghost commented Nov 16, 2015

I've merged those PR, I'm closing this issue.

@ghost ghost closed this as completed Nov 16, 2015
@DrDaveD
Copy link
Author

DrDaveD commented Nov 16, 2015

What about release lines older than CMSSW_7_X_X? Are none of them going to be in active use and supported for more than a year?

@davidlange6
Copy link
Contributor

53x likely will be used a year from now.

On Nov 16, 2015, at 1:27 PM, DrDaveD notifications@github.com wrote:

What about release lines older than CMSSW_7_X_X? Are none of them going to be in active use and supported for more than a year?


Reply to this email directly or view it on GitHub.

@DrDaveD
Copy link
Author

DrDaveD commented Nov 16, 2015

So shall we/can we reopen this issue to include 53x, or should I create a new issue?

@smuzaffar
Copy link
Contributor

@DrDaveD , looks like we need to apply the following patches in order to build it (I guess it was picking up openssl/md5.h from system https://cmssdt.cern.ch/jenkins/job/build-any-ib/15146/console )

can these be included in next version?

@ghost ghost reopened this Nov 16, 2015
@DrDaveD
Copy link
Author

DrDaveD commented Nov 16, 2015

@smuzaffar, sure I can include the 2.8.14-include-fix. patch in the next version. I don't much like the "export" hack but I'll do something equivalent. The 2.8.5 patch should be necessary though, unistd.h is already included in test-req.cc higher up. Are you saying that the include order matters?

@smuzaffar
Copy link
Contributor

@DrDaveD , I did not notice that unistd.h us now included. This patch was there for a long time so may be it is not needed any more.

@DrDaveD
Copy link
Author

DrDaveD commented Nov 20, 2015

Now a problem has been found with 2.8.14, and I am working on a new release. The problem has shown up at the HLT, where they use proxies at localhost.

@smuzaffar
Copy link
Contributor

@DrDaveD , I am closing this issue, please create a new one when needed

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 2, 2016

A new Issue was created by @DrDaveD .

@davidlange6, @smuzaffar, @Degano, @davidlt, @Dr15Jones can you please review it and eventually sign/assign? Thanks.

cms-bot commands are list here cms-sw/cmssw#13029

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

No branches or pull requests

4 participants