This isn't bumping the version of pve-common, but the build-dependency only (why not the installation dependency too?).
The common commit subject style used for such things, as can be seen by checking git log on debian/control, is: "d/control: bump build-dependency of pve-common" Then a short sentence in the message: "we require the new <feature/behavior> for XYZ" On 27/05/2022 13:48, Matthias Heiserer wrote: > Signed-off-by: Matthias Heiserer <m.heise...@proxmox.com> > --- > > Changes from v3: > None > > Changes from v1/v2: > new patch > > > debian/control | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/debian/control b/debian/control > index af258db..2898593 100644 > --- a/debian/control > +++ b/debian/control > @@ -7,7 +7,7 @@ Build-Depends: debhelper (>= 12~), > libio-multiplex-perl, > libjson-c-dev, > libpve-cluster-perl, > - libpve-common-perl (>= 7.1-3), > + libpve-common-perl (>= 7.1-4), > libpve-guest-common-perl (>= 4.1-1), > libpve-storage-perl (>= 6.1-7), > libtest-mockmodule-perl, _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
