From: Oguz Bektas <o.bektas@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [RFC proxmox-ve/proxmox-archive-keyring 0/3] split out archive keyring into separate
Date: Mon, 10 Aug 2020 11:51:54 +0200 [thread overview]
Message-ID: <20200810095154.GA336803@gaia.proxmox.com> (raw)
In-Reply-To: <20200806151750.1460435-1-f.gruenbichler@proxmox.com>
On Thu, Aug 06, 2020 at 05:17:47PM +0200, Fabian Grünbichler wrote:
> with proxmox-ve as proof of concept - the other meta packages shipping
> keys should be updated in the fashion if we go down this route.
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
hi,
thanks for the patch
i've just tested it and it seems to work as expected.
------------------------------------------------------------------------------------------
root@pmx:~/pkgs# dpkg -i proxmox-archive-keyring_1.0_all.deb
Selecting previously unselected package proxmox-archive-keyring.
(Reading database ... 57272 files and directories currently installed.)
Preparing to unpack proxmox-archive-keyring_1.0_all.deb ...
Unpacking proxmox-archive-keyring (1.0) ...
Setting up proxmox-archive-keyring (1.0) ...
root@pmx:~/pkgs# dpkg ^C
root@pmx:~/pkgs# dpkg -i proxmox-ve_6.2-2_all.deb
(Reading database ... 57278 files and directories currently installed.)
Preparing to unpack proxmox-ve_6.2-2_all.deb ...
Unpacking proxmox-ve (6.2-2) over (6.2-2) ...
Setting up proxmox-ve (6.2-2) ...
Removing obsolete conffile /etc/apt/trusted.gpg.d/proxmox-ve-release-5.x.gpg ...
Removing obsolete conffile /etc/apt/trusted.gpg.d/proxmox-ve-release-6.x.gpg ...
root@pmx:~/pkgs# ls -alr /etc/apt/trusted.gpg.d/proxmox-release-*
-rw-r--r-- 1 root root 1181 Aug 6 16:33 /etc/apt/trusted.gpg.d/proxmox-release-stretch.gpg
-rw-r--r-- 1 root root 1202 Aug 6 16:33 /etc/apt/trusted.gpg.d/proxmox-release-buster.gpg
------------------------------------------------------------------------------------------
next prev parent reply other threads:[~2020-08-10 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 15:17 Fabian Grünbichler
2020-08-06 15:17 ` [pve-devel] [PATCH proxmox-archive-keyring] initial commit Fabian Grünbichler
2020-09-17 9:55 ` [pve-devel] applied: " Thomas Lamprecht
2020-08-06 15:17 ` [pve-devel] [PATCH proxmox-ve 1/2] remove archive keys from proxmox-ve Fabian Grünbichler
2020-08-06 15:17 ` [pve-devel] [PATCH proxmox-ve 2/2] bump version to 6.2-2 Fabian Grünbichler
2020-08-10 9:51 ` Oguz Bektas [this message]
2020-09-03 16:28 ` [pve-devel] ACK: [RFC proxmox-ve/proxmox-archive-keyring 0/3] split out archive keyring into separate Thomas Lamprecht
2020-09-17 15:28 ` [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=20200810095154.GA336803@gaia.proxmox.com \
--to=o.bektas@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