From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, aderumier@odiso.com
Subject: Re: [pve-devel] [PATCH v7 qemu-server 10/10] debian : control : add a break on pve-manager <= 7.2.4
Date: Thu, 23 Jun 2022 09:22:18 +0200 [thread overview]
Message-ID: <302f24e2-ca2e-01ec-db68-b7d0ceff8021@proxmox.com> (raw)
In-Reply-To: <20220622115206.3295425-11-aderumier@odiso.com>
Am 22.06.22 um 13:52 schrieb Alexandre Derumier:
> Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
> ---
> debian/control | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/debian/control b/debian/control
> index af258db..eff8165 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -54,6 +54,6 @@ Depends: dbus,
> ${perl:Depends},
> ${shlibs:Depends},
> Recommends: proxmox-backup-file-restore (>= 2.1.9-2)
> -Breaks: pve-ha-manager (<= 3.0-4), pve-manager (<= 6.0-13)
> +Breaks: pve-ha-manager (<= 3.0-4), pve-manager (<= 7.2-4)
Is there any special reason for this? What exactly breaks?
What's important is that new pve-manager on the target (which is what
the migration patch tests for - needs to be adapted to the proper
version when applying of course) implies new qemu-server on the target
(so it can parse the new section correctly). And that is done via a
normal dependency bump pve-manger -> qemu-server.
> Description: Qemu Server Tools
> This package contains the Qemu Server tools used by Proxmox VE
next prev parent reply other threads:[~2022-06-23 7:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 11:51 [pve-devel] [PATCH v7 qemu-server 00/10] cloudinit pending behaviour change Alexandre Derumier
2022-06-22 11:51 ` [pve-devel] [PATCH v7 qemu-server 01/10] qemuconfig: load_current_config : delete cloudinit value Alexandre Derumier
2022-06-22 11:51 ` [pve-devel] [PATCH v7 qemu-server 02/10] vzdump : skip special:cloudinit section Alexandre Derumier
2022-06-22 11:51 ` [pve-devel] [PATCH v7 qemu-server 03/10] migration: test targetnode min version for cloudinit section Alexandre Derumier
2022-06-22 11:52 ` [pve-devel] [PATCH v7 qemu-server 04/10] cloudinit: add cloudinit section for current generated config Alexandre Derumier
2022-06-22 11:52 ` [pve-devel] [PATCH v7 qemu-server 05/10] generate cloudinit drive on offline plug Alexandre Derumier
2022-06-22 11:52 ` [pve-devel] [PATCH v7 qemu-server 06/10] cloudinit: make cloudnit options fastplug Alexandre Derumier
2022-06-22 11:52 ` [pve-devel] [PATCH v7 qemu-server 07/10] api2: add cloudinit config api Alexandre Derumier
2022-06-22 11:52 ` [pve-devel] [PATCH v7 qemu-server 08/10] api2: add cloudinit_update Alexandre Derumier
2022-06-22 11:52 ` [pve-devel] [PATCH v7 qemu-server 09/10] add cloudinit hotplug Alexandre Derumier
2022-06-22 11:52 ` [pve-devel] [PATCH v7 qemu-server 10/10] debian : control : add a break on pve-manager <= 7.2.4 Alexandre Derumier
2022-06-23 7:22 ` Fabian Ebner [this message]
2022-06-23 7:59 ` DERUMIER, Alexandre
2022-07-27 11:19 ` [pve-devel] [PATCH v7 qemu-server 00/10] cloudinit pending behaviour change Fiona Ebner
2022-08-31 9:40 ` DERUMIER, Alexandre
2022-09-02 12:54 ` Fiona Ebner
2022-09-02 16:42 ` DERUMIER, Alexandre
[not found] ` <mailman.41.1662364805.354.pve-devel@lists.proxmox.com>
2022-09-06 7:24 ` DERUMIER, Alexandre
2022-11-08 16:44 ` [pve-devel] applied-series: " Thomas Lamprecht
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=302f24e2-ca2e-01ec-db68-b7d0ceff8021@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=aderumier@odiso.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox