libgit2 vs ruby-rugged regression
Bug #2059275 reported by
Julian Andres Klode
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| libgit2 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
| ruby-rugged (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
ruby-rugged/
302s -{:name=>"Random J Hacker", :email=>"<email address hidden>", :time=>2017-07-07 10:28:30 +0000}
302s +{:name=>"Random J Hacker", :email=>"<email address hidden>", :time=>2017-07-07 12:28:30.00006 +0200}
Time stamps are off .00006 seconds when built with 64-bit time_t. This is awkward because libgit2 already used an internal 64-bit time type.
| summary: |
- libgit2: ruby-rugged regression + libgit2 vs ruby-rugged regression |
| tags: | added: time-t update-excuse |
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote | #1 |
| Changed in libgit2 (Ubuntu): | |
| status: | New → Confirmed |
| Changed in ruby-rugged (Ubuntu): | |
| status: | New → Confirmed |
To post a comment you must log in.
This still seems to be a real issue. It probably requires some debugging on an armhf instance.