New version?

[markhindley]

Sven,

I completely understand that keeping in sync with systemd updates is time consuming. However, Debian bug #968379 appears to be caused by a breakage in the libelogind0/libsystemd0 compatibility with wireshark now using libsystemd0 symbols only present in version 246.

Are you working on a new version of elogind?

Many thanks

Mark

[Salz]

New versions in systemd 246 compared to elogind 243.7 are (sorted by version)

A LIBSYSTEMD_245
T sd_bus_enqueue_for_read@@LIBSYSTEMD_245
T sd_bus_message_dump@@LIBSYSTEMD_245
T sd_bus_message_sensitive@@LIBSYSTEMD_245
T sd_event_add_child_pidfd@@LIBSYSTEMD_245
T sd_event_source_get_child_pidfd@@LIBSYSTEMD_245
T sd_event_source_get_child_pidfd_own@@LIBSYSTEMD_245
T sd_event_source_get_child_process_own@@LIBSYSTEMD_245
T sd_event_source_send_child_signal@@LIBSYSTEMD_245
T sd_event_source_set_child_pidfd_own@@LIBSYSTEMD_245
T sd_event_source_set_child_process_own@@LIBSYSTEMD_245
T sd_journal_open_namespace@@LIBSYSTEMD_245

T sd_bus_call_method_asyncv@@LIBSYSTEMD_246
T sd_bus_call_methodv@@LIBSYSTEMD_246
T sd_bus_emit_signalv@@LIBSYSTEMD_246
T sd_bus_interface_name_is_valid@@LIBSYSTEMD_246
T sd_bus_member_name_is_valid@@LIBSYSTEMD_246
T sd_bus_object_path_is_valid@@LIBSYSTEMD_246
T sd_bus_reply_method_errnofv@@LIBSYSTEMD_246
T sd_bus_reply_method_errorfv@@LIBSYSTEMD_246
T sd_bus_reply_method_returnv@@LIBSYSTEMD_246
T sd_bus_service_name_is_valid@@LIBSYSTEMD_246
T sd_bus_set_propertyv@@LIBSYSTEMD_246
T sd_journal_enumerate_available_data@@LIBSYSTEMD_246
T sd_journal_enumerate_available_unique@@LIBSYSTEMD_246
T sd_notify_barrier@@LIBSYSTEMD_246
T sd_path_lookup@@LIBSYSTEMD_246
T sd_path_lookup_strv@@LIBSYSTEMD_246

Do you think it is enough to just return -ENOTSUP on all of these and see what breaks? I'll start looking into providing such mockup patch.

[Yamakuzure]

Hey @markhindley and @Salz !
Thank you very much for this information.

Originally I wanted to upgrade to v245, but then read that there are people sticking to v244 of systemd due to stability reasons.
But now that v246 is out, I guess it is time to upgrade to that one.
The debian bug you mentioned is a good reason for that, too.

However, I have to plea for some patience. Although elogind is on top of my todo list, it is number 1 in fact, Corona Killed My Spare Time.

At least I finally got my new laptop, and it is almost fully operational now.
(Feelds good when the laptop goes to sleep in less than a second instead of freezing up like the old one did.)

Hopefully I can get through upgrading elogind during the next week.

And sorry for the long wait!

[mirabilos]

Sven Eden dixit:

However, I have to plea for some patience. Although elogind is on top of my todo list, it is number 1 in fact, [Corona Killed My Spare Time](https://forums.prydeworx.com/showthread.php?tid=103).

OT, but that page doesn’t show. Screenshot: # PrydeWorX Forums - Password Required #[1]Latest Threads (RSS 2.0) [2]Latest Threads (Atom 1.0) [3]____________________ [4]____________________ [5][X] [6]Login [7]Lost Password? [8]Register Or login with a social network below [9]Login with GitHub [10]Login with GitLab [11]PrydeWorX Forums * [12]Forum * [13]Portal * [14]Members * [15]Calendar * [16]Help * [17]Search * PrydeWorX Forums Password Required The administrator has required it so that a password is required for access to this forum. Please enter the password below: [18]______________________________________________ [19]Verify Forum Password [20]Contact Us | [21]PrydeWorX | [22]Return to Top | [23]Lite (Archive) Mode | [24]RSS Syndication | [25][(3)__ English (American)______] [26]Go [27][(1)__Default_____] [28]Go Designed by [29]Joseahfer. Powered By [30]MyBB, © 2002-2020 [31]MyBB Group.

[Yamakuzure]

Strange... Only banned users aren't allowed to view the forum.
However, you can always log in with your gitlab or github account. No registration needed.
I just tried and viewing requires a password. That is not right, hang on...

@mirabilos : Found it. Whenever I edit a forum, my brwoser thinks the "password" field is something to log into the admin area and writes my password into it. So I must not forget to remove that whenever I edit something, or boards end up fully password protected. 🙄

[mirabilos]

Sven Eden dixit:

Strange... Only banned users aren't allowed to view the forum.

I’ve never seen the site before… but it wouldn’t surprise me if they considered the standard webbrowser lynx “banned” as many idiots do… bye, //mirabilos --

> Why don't you use JavaScript? I also don't like enabling JavaScript in Because I use lynx as browser.

+1 -- Octavio Alvarez, me and ⡍⠁⠗⠊⠕ (Mario Lang) on debian-devel

[Yamakuzure]

@mirabilos Thanks for the hatred. Users get banned, not browsers.
Besides, the thread on my forum is perfectly readably with lynx, w3m and elinks. Thanks.

[Yamakuzure]

Just to add some feedback, elogind master is now at the level of systemd-v245. It compiles fine, but I neither checked Travis nor tested it in action, as we need v246 anyway.

[Yamakuzure]

Folks, I am at systemd/systemd Tag v246 now. I have not pushed to elogind/master, yet, because there is plenty of stuff to do until that compiles. The systemd devs have (again) shuffled many functions around, adding new source files and renaming/moving others.
But I am at it and hope to get a compiling version soon, which then can be used to branch of v246-stable to go for a first release candidate.

[Yamakuzure]

Hey all, the master branch is now at level with systemd-v246

However, this is only the "it compiles" status, there is a lot of testing and cleaning up to do. Someone really bold could try it out, but I wouldn't advise it, as I haven't even run the test suite, which too needs a good look at it.

If anybody wants to help, you could do either of the following tasks while I am working on cleaning up the sources:

1. Go through the XML files in man/ and check whether they are
   a. complete in content and files, and
   b. not telling people about stuff that isn't even in elogind
2. Compare test/ with systemd-v246 to see whether tests are missing that we have to add.

Here's the plan:

• Once I have cleaned up the sources, and the man pages and test programs are checked, I will branch out v246-stable and sync it with systemd-stable/v246-stable.
• When the v246-stable sync is done, it is time for a v246.x-rc1 pre-realease, so wider testing can take place
• I have reactivated quite a few issues, that seem to have resurfaced, so we'll go through them. Also there are a few new ones
• When these issues are dealt with, it is time for rc2
• There are some feature requests that will be very helpful, so now is the time to get them done
• Testing, fixing, and eventually full release of v246.x
• Eventually backport fixes and additions in v246-stable to master

This is a bit more work than in previous releases. But there have been quite some changes under the hood, and I'd like to be careful about those.

[Yamakuzure]

A v246-rc1 is almost done. I am mainly battling with travis, it failed on stuff systemd upstream has forgotten. The last issue seem to be some c-ansi errors in testing.

[Yamakuzure]

https://travis-ci.org/github/elogind/elogind/branches starts looking good again, so with any luck I'll push out the v246-rc1 pre-release in a few hours.

[Yamakuzure]

https://github.com/elogind/elogind/releases/tag/v246.0-rc1 can be tested now! 🥳

[Lahvuun]

I tried doing a simple revbump:

11c11
<       SRC_URI="https://github.com/${PN}/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
---
>       SRC_URI="https://github.com/${PN}/${PN}/archive/v246.0-rc1.tar.gz -> ${P}.tar.gz"
51c51
<       "${FILESDIR}/${P}-nodocs.patch"
---
>       "${FILESDIR}/elogind-246_rc1-nodocs.patch"
53a54,55
>
> S="${WORKDIR}/elogind-246.0-rc1"

and it builds fine, but doesn't seem to work.

After a reboot rc-service status elogind just returns status: crashed and I can't run bspwm or sway. Doesn't look like there are any logs so I'm kind of at a loss here. Any way I can debug this?