[SERVER-35315] Upgrade to latest timelib Created: 31/May/18  Updated: 29/Oct/23  Resolved: 16/Jan/19

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 4.1.7

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: Henrik Edin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-38005 Upgrade timelib to at least 2018.01al... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0
Sprint: Dev Tools 2019-01-14, Dev Tools 2019-01-28
Participants:

 Description   

At the very least we should pull in https://github.com/derickr/timelib/commit/157caf3f66da49f4df55c532a7d82a5d0aa4be11 since it fixes a warning in our build.

 

CC derick



 Comments   
Comment by Githook User [ 16/Jan/19 ]

Author:

{'username': 'henrikedin', 'email': 'henrik.edin@mongodb.com', 'name': 'Henrik Edin'}

Message: SERVER-35315 Upgrade timelib to version 2018.01
Branch: master
https://github.com/mongodb/mongo/commit/61141cf224a06fd1e820dc7a6882148382fa0e12

Comment by Derick Rethans [ 20/Dec/18 ]

Yes. 0.15.3 is the only one guaranteed to work.

Comment by Andrew Morrow (Inactive) [ 22/Jun/18 ]

Makes sense to me. We will update the metadata in the next triage meeting.

Comment by Ian Whalen (Inactive) [ 22/Jun/18 ]

acm we don't think there's any specific reason to do this now, so probably makes sense to include this in the 'upgrade 3rd party libs' work in 4.2?

Generated at Thu Feb 08 04:39:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.