Re: gbp related issues with importing new upstream release for raxml-ng

To: Debian Med Project List <debian-med@lists.debian.org>
Subject: Re: gbp related issues with importing new upstream release for raxml-ng
From: Andrius Merkys <merkys@debian.org>
Date: Tue, 26 May 2020 21:26:50 +0300
Message-id: <[🔎] CAEZpsw3N5GYdb5iYNxD-+sV9AdpDRKAyvvx2iB7dmiriROs5aQ@mail.gmail.com>
In-reply-to: <[🔎] CAEZpsw09mfqE5LTk0PNr2Z3jkmNagc_2srMFDUxEizZkqhv_zg@mail.gmail.com>
References: <[🔎] f4657d92-f7d7-9aa0-d762-4779d1df0412@shayandoust.me> <[🔎] CAEZpsw09mfqE5LTk0PNr2Z3jkmNagc_2srMFDUxEizZkqhv_zg@mail.gmail.com>

On Tue, 26 May 2020, 21:25 Andrius Merkys, <merkys@debian.org> wrote:

A quick guess: maybe topost entry of d/changelog has an version number? If so, updating it should fix this.

I meant: an old version number.

Andrius

Reply to:

Follow-Ups:
- Re: gbp related issues with importing new upstream release for raxml-ng
  - From: Shayan Doust <hello@shayandoust.me>

References:
- gbp related issues with importing new upstream release for raxml-ng
  - From: Shayan Doust <hello@shayandoust.me>
- Re: gbp related issues with importing new upstream release for raxml-ng
  - From: Andrius Merkys <merkys@debian.org>

Prev by Date: Re: gbp related issues with importing new upstream release for raxml-ng
Next by Date: Re: gbp related issues with importing new upstream release for raxml-ng
Previous by thread: Re: gbp related issues with importing new upstream release for raxml-ng
Next by thread: Re: gbp related issues with importing new upstream release for raxml-ng
Index(es):
- Date
- Thread