Sourceware and patchwork 2.0

[Siddhesh Poyarekar]

On 13/03/20 20:21, Siddhesh Poyarekar wrote:
> [hides face in shame for having forgotten about it]
> 
> On 13/03/20 19:45, Carlos O'Donell wrote:
>> Sourceware is up and we can start in on patchwork 2.0 at this point.
>> The existing patchwork 1.0 is there, but because it's python2 it's not
>> wired up to the frontend yet (IIUC).
>>
>> Would you be able to help get patchwork 2.0 running?
> 
> Right now it looks like the instance is down.  A quick look suggests it
> is probably something that will get fixed with a newish patchwork (1.0).
>  I'll look at it tonight.  I was able to get it all the way up to 1.1 on
> the OSCI server, so I'm optimistic about getting it at least that far.

OK, so there's good news and bad news.  The bad news first:
patchwork.sourceware.org is still unavailable because patchwork is
barfing with an error that I haven't yet understood.

The good news though is that this is happening only through apache.
That is, when I run the patchwork instance locally (using manage.py),
the instance seems to work just fine.

Bonus: the even better news is that I've managed to upgrade django to
the 1.11.x branch, which seems to be supported for another month or so.
 It's still not recent enough for us to get to present day, but it's
quite a way forward.  I was able to migrate patchwork to 2.0 as well and
all the data is intact.

Almost.

For some reason all of the migration SQL scripts were failing to create
foreign key constraints.  I ended up with a migration that does not have
foreign key constraints, so no cascading deletes.  I don't know if it's
due to some setup issues or buggy scripts, it's probably the former.  In
any case, I'll have to fix up those foreign keys manually.  There aren't
too many, less than 20.

It's almost morning here (I got a bit carried away...), which means I
should get some sleep.  I'll try to find some time to hack at it again
tomorrow.

Siddhesh