Re: Multiple head revisions after git pull (2.0rc1 --> 2.0)

From: Willy-Bas Loos <willybas(at)gmail(dot)com>
To: pgAdmin Support <pgadmin-support(at)postgresql(dot)org>
Subject: Re: Multiple head revisions after git pull (2.0rc1 --> 2.0)
Date: 2017-11-02 10:07:27
Message-ID: CAHnozTj2GmrqmXYuBorEVzvNjp_zHO9_HtON7b3EPBH6P-V9hw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Just to clarify, this is not a git question

Op 1 nov. 2017 12:19 p.m. schreef "Willy-Bas Loos" <willybas(at)gmail(dot)com>:

> Hi,
>
> After my stash & pull to upgrade from 2.0rc1 to 2.0, these commands both
> end in the error below.
>
> - ../web$ FLASK_APP=pgAdmin4.py flask db revision
> - ../web$ python pgAdmin4.py
>
>
> File "/home/wbloos/.virtualenvs/pgadmin4/lib/python3.5/site-
> packages/alembic/script/revision.py", line 270, in get_current_head
> "%s(at)head" % branch_label if branch_label else "head")
> alembic.util.exc.CommandError: Multiple head revisions are present for
> given argument 'head'; please specify a specific target revision,
> '<branchname>@head' to narrow to a specific head, or 'heads' for all heads
>
> I use Version: webpack 3.6.0
>
> Any tips?
>
> Cheers,
> --
> Willy-Bas Loos
>

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Murtuza Zabuawala 2017-11-02 11:07:43 Re: Multiple head revisions after git pull (2.0rc1 --> 2.0)
Previous Message Dave Page 2017-11-02 09:44:27 Re: F5 - irritating behaviour