#13439 closed defect (fixed)
Fix cryptsetup breakage from json-c-0.14
| Reported by: | Douglas R. Reno | Owned by: | Douglas R. Reno |
|---|---|---|---|
| Priority: | normal | Milestone: | 10.0 |
| Component: | BOOK | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description ¶
As mentioned in this email:
http://lists.linuxfromscratch.org/pipermail/blfs-dev/2020-April/037382.html
The JSON-C API changes break Cryptsetup. These API changes include changing TRUE/FALSE To 1/0, and bringing in a couple API calls that used to be part of cryptsetup itself.
Here is a link to the relevant commit:
We should probably check libmypaint as well.
Change History (9)
comment:1 by , 5 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 5 years ago
comment:5 by , 5 years ago
volume_key is unaffected. This is only a cryptsetup problem then. Volume_key has cryptsetup as a required dependency, so I don't think it's necessary to add a required one on json-c to it.
Note:
See TracTickets
for help on using tickets.
This list of packages didn't seem right to me, so I ran "grep -r json-c /usr/src/logs" and found that volume_key, bind, libmypaint, and cryptsetup could all be affected. I'll check those