-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New major release soon? #141
Comments
Yes it is. I am currently testing and cleaning up the sources from unused functions.Guess I'll push tomorrow, you can clone from v243-stable branch and test, too, if you like.
|
Would be much easier if there was en 9999 ebuild in Gentoo, could you push one? |
There is one in my Overlay "seden", available via Layman.I am not a Gentoo dev, just a proxy maintainer for a few packages. (not elogind)
|
I just pushed. Travis is no longer working, but that I have to sort out later. (They changed some default package in the void linux image we use.) |
I tried your elogind-243.9999 ebuild but didn't work out:
|
This little patch makes it build:
w.r.t elogind-241.1-docs.patch, could you not integrate that into the elogind src? |
Sorry for the late reply. I have just published: https://github.com/elogind/elogind/releases/tag/v243.4 The elogind-243.9999 should work just fine until the update hits the portage tree. The reason for the long time is my stupidity leading to a typo that lead to an So after restoring enough to test and get this release out, my current main project is: I hope I get my stuff back... |
Great !
Ouch, been there myself too. |
BTW, the tag, v243.4 seem to be missing. |
I had to retract the release due to some heavy issues on travis. And good it was, because some more issues popped up all of a sudden. I'll re-release when everything is ready. Hopefully tomorrow or on Wednesday. |
It should be fixed now. |
Still don't see it. |
I need a little bit more info. I am using elogind-243.9999 for a few weeks now, and everything is working well, built with gcc-9.2 against glibc-2.30. No build failures so far, so I don't know why I should add includes when they don't solve a standing problem. Do you build still fails with elogind-243.9999 ? |
umask(2) has these includes documeted:
Omitting them may work depending on glibc version which by accident pull in these Have you fixed the two Gentoo patches elogind-241.4-broken-test.patch and elogind-241.4-nodocs.patch ? |
Especially since elogind defaults to -Werror |
Still breaks form me at home: |
Now I get it.... |
|
umask(2) has these includes documeted: #include <sys/types.h> #include <sys/stat.h> mode_t umask(mode_t mask); These are no linger implicitly included and thus have to be included directly. Thanks to @joakim-tjernlund for pointing this out! Bug: #141 Closes: #141 Signed-off-by: Sven Eden <sven.eden@prydeworx.com>
@perfect7gentleman That's also my experience. That's why I need your feedback, guys, so thank you very much! |
@joakim-tjernlund Done! |
241.4 is getting old, is there a 243.x on the horizon?
The text was updated successfully, but these errors were encountered: