1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
| | From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [ANNOUNCE] public-inbox 1.8.0
Date: Sat, 23 Apr 2022 08:22:59 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Message-ID: <2022-04-23-public-inbox-1.8.0-released@finally>
A minor release focused on bugfixes and minor improvements.
Upgrades should happen transparently, but downgrading back to
1.7.0 will likely cause problems for lei users (and only lei
users).
lei users may experience duplicate messages in Maildirs if attempting to
downgrade from 1.8.0 to 1.7.x. public-inbox-* tools are unaffected and
may downgrade freely.
Bugfixes:
Numerous test fixes thanks to NixOS developers.
Long-running daemons are more robust in case of corrupt blobs
or crashes of git-cat-file processes
PublicInbox::WWW: all CR are removed before LF, fixing display of
CR-CR-LF messages.
Solver supports SHA-256 code repositories (inbox and lei store support
is still pending).
Internal updates:
Reduced dependencies on Inline::C for Linux users; Linux users may
now use lei with neither Inline::C nor Socket::MsgHdr installed.
New features:
The --dangerous flag is now supported in public-inbox-index and
public-inbox-extindex to use the Xapian::DB_DANGEROUS flag for initial
indexes. This may reduce SSD/HDD wear at the expense of disallowing
concurrency and data integrity in case of an unexpected shutdown.
Please report bugs via plain-text mail to: meta@public-inbox.org
See archives at https://public-inbox.org/meta/ for all history.
See https://public-inbox.org/TODO for what the future holds.
|