On 15.06.21 13:27, Fabian Grünbichler wrote: > patches 3,4,6 can easily be backported to buster as well. > > patch 5 is just an invocation of 'wrap-and-sort -f debian/control.in', > so trivially backportable or adaptable in case only some of this series > gets applied/context has changed. > > patch 2 is needed for building on a clean bullseye system which does not > have (EOL) python2.7 around by default. > > patch 1 only makes sense to backport if we also backport the related > tools, since the ones from buster seem to be too old for our kernel > versions (see #3464). > > Fabian Grünbichler (6): > build: keep unstripped kernel and module files > d/rules: build perf with python3 > d/control: provide linux-libc-dev with version > d/control: remove references to 2.6 kernel > d/control: wrap-and-sort > d/rules: close race between 'cp' and module handling > > debian/control.in | 37 ++++++++++++++++++++----------------- > debian/rules | 19 +++++++++++++++---- > 2 files changed, 35 insertions(+), 21 deletions(-) >
applied series, much thanks! No hard feelings either way on backporting... _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
