Univention Bugzilla – Bug 33496
Call join scripts after app installation
Last modified: 2013-12-30 09:39:36 CET
It can be confusing that join scripts need to be executed after the installation of an app. The execution of univention-run-join-scripts could at least be tried with the given user credentials. If that fails, a proper hint (maybe with a link to the join module) could help to understand that join scripts need to be executed.
*** Bug 33462 has been marked as a duplicate of this bug. ***
Or asking for credentials (if the permissions aren't enough) like it is done in system-setup and join module.
If it is done this way, all pending join scripts will be called. A similar situation is considered problematic: All errata updates are installed when updating an app.
(In reply to Dirk Wiesenthal from comment #3) > If it is done this way, all pending join scripts will be called. > > A similar situation is considered problematic: All errata updates are > installed when updating an app. No, you can give the joinscripts you want to execute as parameter to univention-run-join-scripts.
(In reply to Florian Best from comment #4) > No, you can give the joinscripts you want to execute as parameter to > univention-run-join-scripts. And how do I know which joinscripts are to be run? Everything that starts with ${appid}?
dpkg knows which files are installed by a package. Just look what was placed in /usr/lib/univention-install/ dpkg-query -L <packagename>
(In reply to Erik Damrose from comment #6) > dpkg knows which files are installed by a package. Just look what was placed > in /usr/lib/univention-install/ > > dpkg-query -L <packagename> Maybe this works (I would need python bindings for that, though). But still I need to know which packages are newly installed (plus all dependencies). But not all packages that apt tells me: I still have to differentiate between those that are actually installed and those that are only updated. ... Except an updated version of that package brings a new join script, of course... Maybe I monitor the whole directory? Then I need to parse "VERSION=x"... Sounds feasible. Smells hacky.
Best approach in my opinion: If new modules show up without relogin (see Bug#33202), there would be no "Restart required" dialogue after app installation -> Issue a "join/check_join_status" command, show result as dialog.notify() (just like after login). Alternatively: Run check-join-status before app installation! If everything run: check-join-status after app installation! If something is missing: run-join-scripts with user credentials And even this is not really correct (join status changed due to other reasons)
I would prefer WONTFIX. After the App has been installed the admin gets the notification about the missing join script. Once the restart popup has been removed, it gets straightforward. I think we should improve the domain join module, for example Bug #33528.
(In reply to Stefan Gohmann from comment #9) > I would prefer WONTFIX. After the App has been installed the admin gets the > notification about the missing join script. Once the restart popup has been > removed, it gets straightforward. > > I think we should improve the domain join module, for example Bug #33528. → WONTFIX