Opened 6 months ago
Closed 5 months ago
#5518 closed enhancement (fixed)
systemd-256.4
| Reported by: | Bruce Dubbs | Owned by: | lfs-book |
|---|---|---|---|
| Priority: | normal | Milestone: | 12.2 |
| Component: | Book | Version: | git |
| Severity: | normal | Keywords: | |
| Cc: |
Description
New minor version.
Should we update at all minor changes?
The NEWS file only seems to be updated for major versions, but there seems to be a lot of commits: https://github.com/systemd/systemd/compare/v256.1...v256.2
Change History (6)
comment:1 by , 6 months ago
comment:2 by , 5 months ago
| Summary: | systemd-256.2 → systemd-256.2 (wait for 257 or an important fix) |
|---|
Per renodr's reply in blfs:#19967.
comment:3 by , 5 months ago
| Milestone: | 12.2 → Future |
|---|
comment:4 by , 5 months ago
| Milestone: | Future → 12.2 |
|---|---|
| Summary: | systemd-256.2 (wait for 257 or an important fix) → systemd-256.4 |
Now 256.4. I plan to do an update to fix https://github.com/systemd/systemd/issues/33411 which can be triggered by enabling some units in BLFS and produce stupid messages (that we don't want to explain in the book).
comment:5 by , 5 months ago
Note:
See TracTickets
for help on using tickets.
Maybe only update for security fixes, and also do an update just before package freeze.