Re: Removing an archive from hyperkitty
Hi,
It turns out to be a feature added in 1.3.1 [0]. I wonder if the MySQL instructions listed in this comment[1] are safe to use? I'm reluctant to upgrade because the machine is for production and using packages from Debian GNU/Linux buster is recommended.
Cheers
[0] https://gitlab.com/mailman/hyperkitty/-/issues/146 [1] https://gitlab.com/mailman/hyperkitty/-/issues/146#note_423111350
On 04/10/2020 18:16, Loïc Dachary wrote:
Hi,
I accidentally created an archive for a non existent mailing list with a command like:
python3 manage.py hyperkitty_import --list-address test2@the.re --ignore-mtime --no-sync-mailman /tmp/f.mbox
where test2@the.re does not exist. It succeeded and now the web interface shows this archive that has no associated mailing list. How can I remove it ?
Thanks in advance for any tip you may have ;-)
-- Loïc Dachary, Artisan Logiciel Libre
On 10/4/20 4:09 PM, Loïc Dachary wrote:
Hi,
It turns out to be a feature added in 1.3.1 [0]. I wonder if the MySQL instructions listed in this comment[1] are safe to use? I'm reluctant to upgrade because the machine is for production and using packages from Debian GNU/Linux buster is recommended.
Cheers
[0] https://gitlab.com/mailman/hyperkitty/-/issues/146 [1] https://gitlab.com/mailman/hyperkitty/-/issues/146#note_423111350
To be honest, they don't look like very well written queries.
-- Phil Stracchino Babylon Communications phils@caerllewys.net phil@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958
Phil Stracchino writes:
On 10/4/20 4:09 PM, Loïc Dachary wrote:
Hi,
It turns out to be a feature added in 1.3.1 [0]. I wonder if the MySQL instructions listed in this comment[1] are safe to use? I'm reluctant to upgrade because the machine is for production and using packages from Debian GNU/Linux buster is recommended.
Cheers
[0] https://gitlab.com/mailman/hyperkitty/-/issues/146 [1] https://gitlab.com/mailman/hyperkitty/-/issues/146#note_423111350
To be honest, they don't look like very well written queries.
They're not elegantly written, but they look correct to me (they're *supposed* to be a bulldozer :) and they worked for that user. If one doesn't have 1.3.1 and is unwilling to upgrade, it should be safe enough.
- For extra safety you can take a snapshot of the database.
- Make absolutely sure you have the right mailinglist_id.
And that procedure should work.
@Loïc Oerhaps you should review your policy on upgrading with respect to this particular application (choose Mailman suite or HyperKitty, depending). We're not seeing many regressions, but over time we are fixing inconveniences where documented features work as documented but are insufficient to get your work done, so you have to drop into "hack the Mailman command shell" or even "hack the backend RDBMS" mode. Ie, we're adding features that allow you to do the work with code we've written and tested, rather than some third party script.
This is something only you can decide, of course, and I'm not going to advocate one way or the other. If you're pretty comfortable with direct access to your MySQL database, that way lowers risk of regressions by not upgrading the software. If you're not, upgrading lowers the risk you face with lightly tested third party procedures.
Steve
On Sun, 2020-10-04 at 22:09 +0200, Loïc Dachary wrote:
Hi, It turns out to be a feature added in 1.3.1 [0]. I wonder if the MySQL instructionslisted in this comment[1] are safe to use? I'm reluctant to upgrade because the machine is for production and using packages from Debian GNU/Linux buster is recommended. Cheers [0] https://gitlab.com/mailman/hyperkitty/-/issues/146 [1] https://gitlab.com/mailman/hyperkitty/-/issues/146#note_423111350
They worked for me :-) I cannot promise that I caught all dependencies, and I just needed something to clear the archives so they could be recreated (the mbox I imported was not clean). i.e. There may still be something in some some table that points to the list name. It did not delete the entry in hyperkitty_mailinglist initially so I edited my comment and added that in.
It was a quick and dirty route to clear emails from the list out the archive, nothing more. All it does it get the ids of the threads and emails in the list, remove records with references to these from other tables (attachments, votes, etc), remove internal references and drop the threads and emails. It is not optimal code, but then I hope I dont have to use it too often - I am just tied to the packages shipped in debian buster, so dont have 1.3.1.
-- Alex
On 04/10/2020 18:16, Loïc Dachary wrote:
Hi, I accidentally created an archive for a non existent mailing list with a command like: python3 manage.py hyperkitty_import --list-address test2@the.re --ignore-mtime --no-sync-mailman /tmp/f.mbox where test2@the.re does not exist. It succeeded and now the web interface shows this archive that has no associated mailing list. How can I remove it ? Thanks in advance for any tip you may have ;-)
-- Loïc Dachary, Artisan Logiciel Libre _______________________________________________Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
participants (4)
-
Alex Schuilenburg -
Loïc Dachary -
Phil Stracchino -
Stephen J. Turnbull