Yep - I had a mild panic for a second.
How bad would it be if we set up a maintenance window and took the fedmsg
gateway down for the migrations?
Sent from [Nylas N1](https://link.nylas.com/link/62fktrnw4nwag1kafi1t5vn3l
cmFzdHJ1Y3R1cmVAbGlzdHMuZmVkb3JhcHJvamVjdC5vcmc=), the extensible, open source
On Sep 24 2016, at 9:52 pm, Kevin Fenzi <kevin(a)scrye.com> wrote:
Today I went and ran pgimporter ( https://pagure.io/pagure-importer
on the fedora-infrastructure trac tickets and then imported them into
Things went pretty smoothly until the import, when we found that even
though the 'fedmsg' plugin was off for the main git repo, there's
currently no way to disable it for the tickets or docs repos for a
project. This meant that the import started sending out fedmsgs to
everyone who interacted to fedora-infrastructure trac over the last 10
years or so. ;( We stopped things before too long and managed to wipe
out the messages (Thanks patrick!). Sorry for any confusion with old
We will want to sort this out before more projects migrate. There
to be a way to supress these "rewind of the past" fedmsg storms.
All that said, we are now migrated to pagure, so where you would file
tickets before on fedorahosted, you should file issues on
I will be syncing up the git repo and readme and adding docs over the
infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org