all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] applied: [PATCH bullseye kernel 0/6] debug package and packaging/build cleanups
Date: Tue, 15 Jun 2021 14:34:47 +0200	[thread overview]
Message-ID: <c6a20324-4f24-9e91-a205-0b1e49cdc29a@proxmox.com> (raw)
In-Reply-To: <20210615112729.1099797-1-f.gruenbichler@proxmox.com>

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...




      parent reply	other threads:[~2021-06-15 12:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 11:27 [pve-devel] " Fabian Grünbichler
2021-06-15 11:27 ` [pve-devel] [PATCH kernel 1/6] build: keep unstripped kernel and module files Fabian Grünbichler
2021-06-15 11:27 ` [pve-devel] [PATCH kernel 2/6] d/rules: build perf with python3 Fabian Grünbichler
2021-06-15 11:27 ` [pve-devel] [PATCH kernel 3/6] d/control: provide linux-libc-dev with version Fabian Grünbichler
2021-06-15 11:27 ` [pve-devel] [PATCH kernel 4/6] d/control: remove references to 2.6 kernel Fabian Grünbichler
2021-06-15 11:27 ` [pve-devel] [PATCH kernel 5/6] d/control: wrap-and-sort Fabian Grünbichler
2021-06-15 11:27 ` [pve-devel] [RFC kernel 6/6] d/rules: close race between 'cp' and module handling Fabian Grünbichler
2021-06-15 12:34 ` Thomas Lamprecht [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c6a20324-4f24-9e91-a205-0b1e49cdc29a@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.gruenbichler@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal