Skip to content
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

Move ldap initialization before the postinstall #1064

Merged
merged 2 commits into from
Jan 31, 2021

Conversation

alexAubin
Copy link
Member

The problem

Another poke for the "postinstall is too complex and lengthy". There's no necessity to run the LDAP initialization during the postinstall, and also it's complicated to properly reset and rerun the postinstall when it failed for some reason... Also initializing the LDAP database before postinstall opens up the ability to recommend people installing on arm boards to directly connect using the "admin" user instead of the confusing "root the first time but then admin user"

Solution

Init the ldap database during the .deb install

PR Status

Done, tested on my side

How to test

Theoretically it's just about running "dpkg-reconfigure yunohost" (after making sure that /etc/yunohost/installed doesnt exists yet) and running the postinstall.

But dpkg-reconfigure yunohost calls the installed .deb's postinst script ... but this PR changes it and it's not trivial to propagate it so uuuuh I just manually ran the various "bash /usr/share/.../... init" stuff that you can find in the changelog to simulate the "dpkg-reconfigure yunohost"

@alexAubin alexAubin added this to the 4.2.x milestone Jan 2, 2021
@zamentur zamentur modified the milestones: 4.3.x, 4.2.x Jan 3, 2021
@zamentur zamentur removed this from the 4.2.x milestone Jan 4, 2021
@alexAubin alexAubin merged commit d152e72 into dev Jan 31, 2021
@alexAubin alexAubin deleted the move-ldap-init-before-postinstall branch January 31, 2021 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants