From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [PATCH proxmox-perl-rs] common: d/control: break/replace libpve-rs-perl (<< 0.6.0)
Date: Tue, 10 May 2022 07:16:23 +0200 [thread overview]
Message-ID: <a2627153-8f6c-48b8-504a-90ab294bf747@proxmox.com> (raw)
In-Reply-To: <20220509101751.1520625-1-s.ivanov@proxmox.com>
Am 5/9/22 um 12:17 schrieb Stoiko Ivanov:
> libproxmox-rs-perl ships /usr/share/perl5/PVE/RS/CalendarEvent.pm,
> which was also present in libpve-rs-perl until version 0.5.1
>
> This can lead to a (racy) issue while upgrading - depending
> on which of libproxmox-rs-perl or libpve-rs-perl gets unpacked first
> we potentially run into:
> ```
> dpkg: error processing archive \
> /tmp/apt-dpkg-install-lNBzMn/48-libproxmox-rs-perl_0.1.0_amd64.deb (--unpack):
> trying to overwrite '/usr/share/perl5/PVE/RS/CalendarEvent.pm', \
> which is also in package libpve-rs-perl 0.5.1
> ```
>
> This patch follows the debian policy manual for these situations:
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-breaks
>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> Sadly was not able to trigger this issue on any of my systems (and a VM with
> a fresh 7.1 ISO install).
>
> common/pkg/debian/control | 2 ++
> 1 file changed, 2 insertions(+)
>
>
applied, thanks!
prev parent reply other threads:[~2022-05-10 5:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 10:17 [pve-devel] " Stoiko Ivanov
2022-05-09 14:49 ` Fabian Grünbichler
2022-05-10 5:16 ` 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=a2627153-8f6c-48b8-504a-90ab294bf747@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@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