Opened 7 years ago
Closed 7 years ago
#55636 closed update (fixed)
aff4 @2cbfe9d18ae3c244a889c393577b3f5108af6c2e_2: update to 0.26.post6
Reported by: | l2dy (Zero King) | Owned by: | ghosthound |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | haspatch | Cc: | ryandesign (Ryan Carsten Schmidt) |
Port: | aff4 |
Change History (4)
comment:1 Changed 7 years ago by l2dy (Zero King)
Description: | modified (diff) |
---|
comment:2 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign added |
---|
comment:3 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | haspatch added |
---|
The upstream aff4 project has split into two projects:
- https://github.com/Velocidex/c-aff4 (the C stuff, which is what the current aff4 port was installing)
- https://github.com/Velocidex/pyaff4 (the Python stuff)
Here's a PR to update to the latest version of c-aff4, which builds fine for me:
comment:4 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
According to that pypi link, 0.26.post6 was released 2017-12-06. The port is currently using git commit 2cbfe9d18ae3c244a889c393577b3f5108af6c2e from 2017-12-12 which is newer. So the port should not be downgraded to 0.26.post6.
The port could be updated to a newer commit and at that time its version field should be fixed; a git commit hash is not an appropriate value for a port version.
I had tried to update the port to a newer commit but it failed to build; I filed issues on their GitHub project. There have been new commits since then so I can try again and see if that fixed it.