Hello Bastian,
> You have not made the suggested fixes in git. What you have done is adding
> 0.13.0 in upstream branch misnomed as 0.11.0
> and adding two commits that claim to import 0.13.0... Please try again.
The changes were made, but there was a problem with my gbp import via uscan and
sk
Control: tags -1 moreinfo
Am 26.09.22 um 16:25 schrieb Lance Lin:
Hello Bastian,
Let me guess: You have not built the package once with a clean chroot.
The meson build dependency from 0.11.0 is lost somehow.
I wanted to check the git for the matching commit but found no 0.11.0 version
there.
Hello Bastian,
> Let me guess: You have not built the package once with a clean chroot.
> The meson build dependency from 0.11.0 is lost somehow.
> I wanted to check the git for the matching commit but found no 0.11.0 version
> there. Please add this before adding
> 0.13.0, i.e., rebase 0.13.0 on
Hello Bastian,
> Let me guess: You have not built the package once with a clean chroot.
> The meson build dependency from 0.11.0 is lost somehow.
> I wanted to check the git for the matching commit but found no 0.11.0 version
> there. Please add this before adding
> 0.13.0, i.e., rebase 0.13.0 on
Control: tags -1 moreinfo
On Wed, 07 Sep 2022 12:37:52 + Lance Lin wrote:
Changes since the last upload:
usbredir (0.13.0-1) unstable; urgency=medium
.
* New upstream version 0.13.0
* debian/watch: Update regex with new release format
dh_auto_configure
cd obj-x86_64-linux-gnu
Please have the same (case-sensitivity!) email address in your changelog that
is in the Maintainer's field.
6 matches
Mail list logo
