Michael Paoli via BALUG-Test3 wrote on 2024-07-19 01:51:
hyperkitty_import -lbalug-test3@lists.balug.org import.single.mbox)
That... should've been obvious as it's how one imports lists after all.
$ (unset LC_ALL && LANG=en_US.UTF-8 export LANG &&
/usr/share/mailman3-web/manage.py
I set up user mailman's .bashrc file so I can just `sudo -u mailman bash` and have everything set up so I can run mailman and mailman-web commands.
Anyway, have you fully migrated the lists?
I'm still in a "I've migrated everything but not made MM3 live yet" some number of months after starting.
Dunno why.
rb
admin@bclug.ca wrote:
Anyway, have you fully migrated the lists?
Nope, not yet.
Still more testing/investigation/prep etc. to do. Likely will do the cutover on all the lists ... probably not this coming weekend, but the following weekend (first weekend in August).
I do also have a bit of monthly processing, see, e.g.: https://lists.balug.org/pipermail/balug-admin/2024-July/001199.html Which runs around top of the month. Do have the script updates pretty much done and mostly tested ... but they're staged and set for Mailman 3, not really worth the bother/complexity to rewrite 'em to be dual purpose to handle both Mailman 2 and Mailman 3. Simpler just to cutover the lists and the scripts, and avoid any such additional complexity.
And want to have things sufficiently well tested and staged, etc. before cutover. So, though far along, don't think I'll likely be ready to do cutover this coming weekend ... so much more likely the following. In any case, almost certainly over/around an August weekend. And then also probably fairly soon after that (hour(s), day(s), week(ish?), then OS upgrades, Debian oldoldstable (unsupported, past EOL of LTS) --> oldstable --> stable. With likely moderate gap (hours/day(s)/week(ish) between the first and second upgrades. But I prefer not to be on oldstable too long ... notably as I don't (think I) have anything else on oldstable, so that'd be the "odd man out". And ... oldoldstable --> oldstable and oldstable --> stable upgrades are pretty similar/comparable ... and probably also more efficient to do that second upgrade not too long after the first ... closer in proximity, the easier to leverage relative commonalities between their upgrades - most notably a lot of the same customized configuration files in each will need similar bits of hand editing to get everything right - typically matter of merging my customizations onto whatever the latest and greatest default configuration would otherwise be.
I'm still in a "I've migrated everything but not made MM3 live yet" some number of months after starting. Dunno why.
Well, at least somewhat interestingly, I do keep running into a whole lot 'o lists out there on The Internet that are still using Mailman 2. E.g.: https://lists.isc.org/ https://lists.gnu.org/mailman/listinfo/ I think I'm still more often running into Mailman 2 lists than Mailman 3. So ... maybe that says something ... heck, especially for GNU.org itself - authors of Mailman 3 - to themselves still be using Mailman 2. Well, peeking bit further ... looks like thus far they're using both Mailman 2 and Mailman 3. Not sure how much of which at this point. But, e.g., at least one of their lists for Mailman 3: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ is using Mailman 3. So, perhaps like many others, they're not (yet) in a huge rush to migrate. Hmmm, and ... totally different domains for (at least) web so ... I wonder what their migration strategy is, or will be. Uhm, ... and peeking wee bit more ... yeah, mostly Mailman 2. Compare the number of (non-hidden) lists on each ... Mailman 3 has only 2 lists: https://lists.mailman3.org/mailman3/lists/ Mailman 2 has 795 lists: https://lists.gnu.org/mailman/listinfo/