Hello Andrius, > I could try to solve the issue, but I can find only -1.1 version on > Salsa (it seems that not all commits are pushed). Actually looking at it now, I am not sure why dch labelled this as -1.1. I thought this should increment to -2? Also not sure why it appended this as NMU. The reason for this (-2) is mainly due to commit d1315fd635221614093a65fe84e228293083b961. Maybe this is a changelog issue? Regards, Andrius On 12/08/2019 06:59, merkys@debian.org wrote: > Hi Shayan, > > On 2019-08-09 19:23, Shayan Doust wrote: >> Yes, mmseqs2. I also assume now the package is OK. If I recall >> correctly, it was an email with the subject >> "mmseqs2_9-d36de+ds-2_amd64.changes REJECTED" sent to Andreas, >> debian-med-packaging and I. > > Oh, now I see: Andreas and you have attempted to upload -2 version of > mmseqs2. I used to think that -2 uploads should not take place while -1 > version is still in NEW queue, but I might be wrong. > > I usually clean everything and use 'gbp buildpackage -S > --git-pristine-tar' to generate *.source.changes prior to upload. I > could try to solve the issue, but I can find only -1.1 version on Salsa > (it seems that not all commits are pushed). > > Best, > Andrius > >
Attachment:
signature.asc
Description: OpenPGP digital signature