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

sympa.pl: Improving --dump_users and adding --restore_users, and related fixes #267

Merged
merged 6 commits into from
Apr 23, 2018

Conversation

ikedas
Copy link
Member

@ikedas ikedas commented Apr 15, 2018

Changes:

  • If list is closed, members, owners and editors are dumped to files member.dump, owner.dump and editor.dump in EXPLDIR/list path/ directory. On previous versions, only members were dumped and file name was subscriber.closed.dump.

Improvements:

  • New and improved options for sympa.pl:
    • --dump --dump_users dumps list members/owners/editors to file under list directory.
    • --suck --restore_users restores list members/owners/editor from this file. This is the new option.
  • Note that dump files are the same as those created when list is closed. --dump--dump_users and --suck--restore_users work only on open list and closed/pending lists are omitted. On previous versions of Sympa, only members were dumped and file name was subscriber.db.dump.

Fixed bug:

  • If a list is closed once and then reopened, list members are registered as permanent (not included) members. Also, subscription suspension option are cleared and so on.

This PR may fix issue #232.


2018-04-21 Update: Renamed functions.

They dump or restore list users (members, owners or editors) in database from/to file.

[change] File for members was changed to `<list dir>/member.dump` which will replace:
  - `subscribers` (used by Sympa prior to 5.4a.1)
  - `subscribers.db.dump` (generated by dump command)
  - `subscribers.closed.dump` (backup for closed list)
[change] Additional files to dump owner or editor: `<list dir>/owner.dump`, `<list dir>/editor.dump`.
They will be used as initial (permanent) owners/editors, or as backup for closed list
[*change] owner and editor parameters in list config file are no longer sync with actual owners/editors.  They are used only at the time of installation of list.
…gistered as permanent (not included) members. Also, subscription suspension option are cleared and so on.

Fxied by dump and restore all information of subscribers in database.
  - `--dump` dumps list members/owners/editors to file under list directory.
  - `--suck` restores list members/owners/editor from this file.
@racke
Copy link
Contributor

racke commented Apr 15, 2018

Commandline option --suck sounds weird to me, what about --import-from-dump or --restore?

@ikedas
Copy link
Member Author

ikedas commented Apr 16, 2018

The word "restore" has already been used: "Restore (closed) list", "Restore (suspended) subscription". Also Sympa has already had a function named "import", and I feel this function is a bit different from function to "import".

How about "store"?

…), respectively.

Options for sympa.pl are also renamed to --dump_users and --restore_users.
@ikedas ikedas changed the title sympa.pl: Improving --dump and adding --suck, and related fixes sympa.pl: Improving --dump_users and adding --restore_users, and related fixes Apr 21, 2018
@ikedas
Copy link
Member Author

ikedas commented Apr 21, 2018

According to discussion on irc, we adopted dump_users and restore_users.

@racke
Copy link
Contributor

racke commented Apr 21, 2018

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants