delete old mailing list so we can make a new one

An admin with access to the private project can purge the list with the puge button, then delete the archive from the filesystem.

Hrm. Purging the list on the -private is being blocked.
https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1661EA37
&
https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1661EC547

I *believe* the problem is very much self inflicted as we renamed these teams directly. And muggins here didn't check to see if they had a list attached.
Am chasing.

On Mon, 2010-07-19 at 07:53 +0000, Steve McInerney wrote:
> Question #117954 on Launchpad Registry changed:
> https://answers.edge.launchpad.net/launchpad-registry/+question/117954
>
> Steve McInerney posted a new comment:
> Hrm. Purging the list on the -private is being blocked.
> https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1661EA37
> &
> https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1661EC547
>
> I *believe* the problem is very much self inflicted as we renamed
> these teams directly. And muggins here didn't check to see if they had
> a list attached.
> Am chasing.

:(.

Be warned that what follows is the writings of a tired and ill man.

This is going to be hard to fix. I expect a few passes of sql and shell
to fix this. I see the new team (named swift) is stuck creating a
mailing list that already exists by that name.

1. I think the goal is to tell Lp to purge the team (which apparently
means set the status so that the list can never be reused, but it will
remain for referential integrity? /me think purge means delete unneeded
data and artefacts.)

-- set the status of the list of PURGED (12).
update mailinglist
set status = 12
where mailinglist.team in (
select id from person where name = 'swift-private')
;

^ This is what the purge step does in the code, and it can only be done
after deactivation, which ensures the list is not the team preferred
email address. I can see in staging that <email address hidden> does
not exist.

2. The mailing list server and file system need purging too. I believe
mailman thinks the list name is still 'swift'.

If there is mailman UI, remove swift for the lists
rm the archive on the file system.

^ I think these two steps must happen in quick succession because Lp is
polling to mailman to create the the new list for the new swift team.

--
__Curtis C. Hovey_________
http://launchpad.net/

Hrm. one step forward and all I guess.
Have done as suggested:
* the -private team no longer shows as having a list
* the various related parts on forster have all been mv'd in a single one liner to *.broken
* alas the new swift team is still showing as having a pending maillist wanting to be built
The obvious select query for the team vs mailinglist returns:

  id | team | registrant | date_registered | reviewer | date_reviewed | date_activated | status | welcome_message
------+---------+------------+----------------------------+----------+---------------+----------------+--------+-----------------
 1819 | 3367816 | 6270 | 2010-07-19 04:25:29.907407 | | | | 4 |

??

still open

The oopses report the swift cannot be created because mailman says that the list still exists. I do not know if mailman needs to be restarted. I assume there was configuration files that needed to be edited to remove swift, and the swift subscribers.

This is still in a broken state... is there anything I can do to help here? (I'm assuming no)

There is nothing you can do. I do not see how to fix the database. The applications screems every hour that there is an impossible list in existence :(

Curtis was able to coordinate the fixing of the issues with the old mailing list, and this should be resolved now.

Thank you for your patience.

- Stefan