GitLab

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

to harden against abuse we'll match them against a regex that should
only match what could possibly be a valid user or group name.

thanks to Wolfgang Frisch and SUSE for the suggestion

BUG: 432757
FIXED-IN: 20.12.3

by default scripty extracts using --c++ which means JS `` template
literals aren't being extracted correctly. to deal with this we first
extract the c++ strings and then join the javscript/qml strings into the
same template

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

This enables finding it via KPluginLoader, which is the recommended way.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

setFileSharingPage and showFileSharingPage were effectively no-op until
5.75. they have been repaired and so we can use them properly now.

we are already in 20.12 dependency freeze so we'll want to avoid bumping
the required version. for trivial backwards compat there's a legacy
addPage() call still

setFileSharingPage and showFileSharingPage were effectively no-op until
5.75. they have been repaired and so we can use them properly now.

we are already in 20.12 dependency freeze so we'll want to avoid bumping
the required version. for trivial backwards compat there's a legacy
addPage() call still

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

The text talks about setting a password, but then various other things
talk about creating a user. Technically a user is indeed being created
behind the scenes, but this is something that the user doesn't really
need to know about. So let's just consistently communicate the
password-setting aspect to the user.

Also right-align the button to match other dialogs.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

they spanned the entire height which looked super silly bc there'd be
large amounts of space between text and button. wrap them in an item so
they have something to center in and forward the parent width
accordingly.
this now correctly centers them.

to edit usershares the user needs to be member of the appropriate group.
detect when that is not the case (dir is not writable) and offer
automatic group management if at all viable (dir isn't group owned by
root and the group looks like something samba related).

to visualize this there's a new group page which is run after
installation and also on every start (it does a fairly cheap check;
never the less it is equipped with busy indication).

should the user not be able to write the usershare directory the user
can ask us to ask the kauth helper to make the necessary changes.

the entire backing logic is inside a groupmanager helper class that
evaluates the group status of the user

this also moves the reboot function back out of the samba installer into
the plugin. the group management also needs to reboot (or at least
re-log) to apply the changes so we need a more global way to issue
reboots

BUG: 407846
FIXED-IN: 20.12