On Thu, 16 May 2013 11:27:44 -0400 Ralph Bean <rbean@xxxxxxxxxx> wrote: > This is a second freeze break request for Fedora Tagger. I haven't > actually carried out the first one yet, but Kevin's mention of the > broken bodhi sqlitebuildtags url took us down a rabbit hole. > > This is the traceback that tagger logs when the bodhi masher tries to > pull down its sqlitebuildtags: ...snip... > The problem is that the schema upgrade from tagger1 to tagger2 didn't > go smoothly in production, and we didn't notice. There is supposed to > be a DB constraint that disallows duplicate tags on packages, but it > is absent. > > We can't just apply that new constraint, because there are now two > duplicate tags in the DB. > > We need to: > > 1) Remove the duplicates > 2) Apply the constraint so it doesn't happen again Can we test this in stg first? Then if all goes well do it in prod? +1 if we can do that to make sure there's no thinkos in the script, etc. (we should be able to dump/restore the db over to stg from prod so it has the same data too, right?) kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
