| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Célestin Matte <celestin(dot)matte(at)cmatte(dot)me> |
| Cc: | pgsql-www(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [Patch] pglister: Bugfix: wrong dependency in eximintegration |
| Date: | 2023-07-31 14:31:04 |
| Message-ID: | CABUevEznq_WFJuzoqXT1RXi5SGNq2=KeWaG6=4+DOYFSVxZ70Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Mon, Jul 31, 2023 at 11:02 AM Célestin Matte
<celestin(dot)matte(at)cmatte(dot)me> wrote:
>
> Migrations added in 1527758e as a synchronization with latest version of pgweb auth plugin cause migration to crash with the following error:
> CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0001_initial, 0002_queue_idx in eximintegration).
Oh crap. Those were clearly not supposed to be included in that commit
as they're completely unrelated to the auth plugin...
> As far as I understand the situation, the second migration in eximintegration depends on lists' 0001_initial instead of eximintegration's 0001_initial. Changing this dependency fixes the issue and allow django to migrate.
Yup, that's correct. Applied and pushed, thanks!
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2023-08-02 06:46:41 | Re: pgarchive's search frontend |
| Previous Message | Célestin Matte | 2023-07-31 09:55:28 | pgarchive's search frontend |