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 latest CMSSW to frontier_client 2.8.16 and pacparser 1.3.5 #2127

Closed
DrDaveD opened this issue Feb 4, 2016 · 14 comments
Closed

Comments

@DrDaveD
Copy link

DrDaveD commented Feb 4, 2016

This frontier client release has improved support for IPv6 and fixes the problems found in 2.8.14.

Get the new version from http://frontier.cern.ch/dist/

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 4, 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

@davidlange6
Copy link
Contributor

@degano- i'm not sure its the right moment to change frontier.. could we stay with what we have in 800pre6 for the moment.

@ghost
Copy link

ghost commented Feb 8, 2016

@davidlange6 Okay, no problem. I'll just finish the test. We can always port this to the next devel cycle once we'll have that.

@davidlange6
Copy link
Contributor

yes, or it can go into the devel build already.

On Feb 8, 2016, at 11:57 AM, Alessandro Degano notifications@github.com wrote:

@davidlange6 Okay, no problem. I'll just finish the test. We can always port this to the next devel cycle once we'll have that.


Reply to this email directly or view it on GitHub.

@DrDaveD
Copy link
Author

DrDaveD commented Feb 8, 2016

So then which would be the first release version it would go into?

@davidlange6
Copy link
Contributor

810pre1 for testing and then back porting

On Feb 8, 2016, at 1:31 PM, DrDaveD notifications@github.com wrote:

So then which would be the first release version it would go into?


Reply to this email directly or view it on GitHub.

@DrDaveD
Copy link
Author

DrDaveD commented Feb 8, 2016

@davidlange6 how much of a delay does that introduce? I don't even see 8_1_X on https://twiki.cern.ch/twiki/bin/viewauth/CMS/ReleaseSchedule.

@DrDaveD
Copy link
Author

DrDaveD commented Feb 16, 2016

I have released 2 more versions with minor updates that you might as well pick up when you build this. Version 2.8.18 now.

@DrDaveD
Copy link
Author

DrDaveD commented Feb 22, 2016

@davidlange6 8_0_0 is released now, can this start to be added to 8_1_X soon?

@sextonkennedy
Copy link
Member

It looks like @Degano merged the older version. I happen to know that ATLAS is moving to 2.8.18 can we move to that one as @DrDaveD requested in this thread?

@davidlange6
Copy link
Contributor

It's what happens when titles of issues are obsoleted. Yes, let's move to 2.8.18

@ghost
Copy link

ghost commented Mar 3, 2016

Okay, I'll upgrade again. This issue is no longer needed.

@ghost ghost closed this as completed Mar 3, 2016
@DrDaveD
Copy link
Author

DrDaveD commented Mar 3, 2016

@Degano is it being tracked in another issue instead?

@smuzaffar
Copy link
Contributor

@DrDaveD , @Degano have created new PR #2174 for this.

This issue was closed.
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

5 participants