Opened 20 months ago

Closed 19 months ago

Last modified 15 months ago

#13154 closed enhancement (fixed)

elogind-243.7

Reported by: Bruce Dubbs Owned by: Pierre Labastie
Priority: normal Milestone: 10.0
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

New point version.

Change History (15)

comment:1 by Pierre Labastie, 19 months ago

Owner: changed from blfs-book to Pierre Labastie
Status: newassigned

comment:2 by Pierre Labastie, 19 months ago

This is the second release of the current version 243 series.
We started with 243.4 to be in sync with upstream systemd tagging,.

The latest upstream commit this version is synced to is
systemd-stable/v243-stable:f8dd0f2
Changes and Additions

    Some unnecessary sources and tools have been removed.
    Add VARRUN_IS_SYMLINK guard for DEFAULT_SYSTEM_BUS_ADDRESS in bus-internal.h. This brings it in line with src/basic/def.h. - @mbakke (PR #153)
    Change elogind mask else format to make the upstream commit migration tools more efficient.
    From hereon the format for masking blocks is:

    #if 0 /// reason with the keyword 'elogind' in it
    (...)masked block(...)
    #else // 0
    (...)alternative block for elogind(...)
    #endif // 0

Fixed Bugs

    Re-enable credential check on suspend/hibernate (#149)
    The reasons why this check was removed, are long gone.
    Fix compilation with -Defi=false (#150)
    Add a list item about RemoveIPC to the elogind man page (#151)
    This setting has caused some stormy waves on the Debian bug tracker, so the information is now easier to find.
    Fix system-sleep and -shutdown hook script handling (#154)
    Hook scripts should work just fine again.

comment:3 by Pierre Labastie, 19 months ago

I have a problem. At each login (in a virtual console), I get:

elogind-daemon[837]: Assertion 's' failed at src/login/logind-session.c:1267,
function session_get_state(). Aborting.

with of course the pid changing. I need to try to downgrade to 243.4.

comment:4 by Bruce Dubbs, 19 months ago

I updated yesterday but didn't test. This morning I get the same error. It does not prevent logging on, but I didn't try starting xorg yet. Let us know what you can figure out.

comment:5 by Pierre Labastie, 19 months ago

It's been reported upstream actually: https://github.com/elogind/elogind/issues/156

Do you have figures? I'm amazed the SBU was decreased by a factor of two, and the disk space increased by almost 50 %. I wonder whether NINJAJOBS is efficient (does not explain the disk space increase, though).

comment:6 by Bruce Dubbs, 19 months ago

These are my stats using 'ninja -j4':

18.2 Elapsed Time -  elogind-243.7
SBU=.175
1408 /usr/src/elogind/elogind-243.7.tar.gz SIZE (1.375 MB)
51272 kilobytes BUILD SIZE (50.070 MB)
md5sum : eeaa5cca63c60371656ab5fd88fc5d9b  /usr/src/elogind/elogind-243.7.tar.gz

comment:7 by Pierre Labastie, 19 months ago

Hmm, I have 63 MB for build size. I'll try with ninja -j1: I have the same SBU as you, while I have export NINJAJOBS=1. I do not know what may have happened for explaining such a difference in build size. Tests are only 2 MB.

comment:8 by Pierre Labastie, 19 months ago

Resolution: fixed
Status: assignedclosed

Fixed at r22804

comment:9 by Pierre Labastie, 19 months ago

Resolution: fixed
Status: closedreopened

The maintainer of elogind has not tagged and released what he intended to for this version! See https://github.com/elogind/elogind/issues/155#issuecomment-598069313

I guess we need to revert, but maybe wait for maintianer action first (what we have seems to be working).

comment:10 by Pierre Labastie, 19 months ago

Status: reopenednew

comment:11 by Pierre Labastie, 19 months ago

Status: newassigned

comment:12 by Pierre Labastie, 19 months ago

Upstream just made a stealth update. Hope it is the last one...

comment:13 by Pierre Labastie, 19 months ago

Resolution: fixed
Status: assignedclosed

Fixed (?) at r22838

comment:14 by Bruce Dubbs, 15 months ago

Milestone: 9.210,0

Milestone renamed

comment:15 by Bruce Dubbs, 15 months ago

Milestone: 10,010.0

Milestone renamed

Note: See TracTickets for help on using tickets.