View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000359 | file | General | public | 2022-06-14 17:02 | 2022-07-04 20:08 |
| Reporter | darose | Assigned To | christos | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| OS | Linux | OS Version | 5.18.3 | ||
| Product Version | 5.42 | ||||
| Fixed in Version | 5.43 | ||||
| Summary | 0000359: v5.42 not correctly identifying JSON Lines files | ||||
| Description | v5.41 would correctly identify a JSON Lines file (see https://jsonlines.org/ and http://ndjson.org/) as json. v5.42 now only identifies it as ascii text. (This is breaking functionality in a project of mine which requires the ability to detect json files.) | ||||
| Steps To Reproduce | 1. Upgrade "file" to v5.42 2. Run "file" on a valid JSON Lines file. 3. "file" will not identify it as json; only ascii text. | ||||
| Additional Information | See the following output for an example: $ cat /tmp/test.json {} {} $ pacman -Q file file 5.41-1 $ file /tmp/test.json /tmp/test.json: JSON data $ sudo pacman -S file ... Packages (1) file-5.42-1 ... $ pacman -Q file file 5.42-1 $ file /tmp/test.json /tmp/test.json: ASCII text | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-06-14 17:02 | darose | New Issue | |
| 2022-07-04 20:08 | christos | Assigned To | => christos |
| 2022-07-04 20:08 | christos | Status | new => assigned |
| 2022-07-04 20:08 | christos | Status | assigned => resolved |
| 2022-07-04 20:08 | christos | Resolution | open => fixed |
| 2022-07-04 20:08 | christos | Fixed in Version | => 5.43 |
| 2022-07-04 20:08 | christos | Note Added: 0003781 |
