From: Jing Luo via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Jing Luo <jing@jing.rocks>
Subject: [pve-devel] [PATCH pve-manager] d/control: change binary package architecture from `any` to `all`
Date: Thu, 12 Sep 2024 23:25:49 +0900 [thread overview]
Message-ID: <mailman.234.1726153631.414.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 5824 bytes --]
From: Jing Luo <jing@jing.rocks>
To: pve-devel@lists.proxmox.com
Cc: Jing Luo <jing@jing.rocks>
Subject: [PATCH pve-manager] d/control: change binary package architecture from `any` to `all`
Date: Thu, 12 Sep 2024 23:25:49 +0900
Message-ID: <20240912142753.1280695-1-jing@jing.rocks>
There is no architecture dependent binary files in the final deb
package. There is no shared libs either (says debhelper), so let's remove
that too.
Signed-off-by: Jing Luo <jing@jing.rocks>
---
debian/control | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/debian/control b/debian/control
index d844cc15..a3cb632f 100644
--- a/debian/control
+++ b/debian/control
@@ -34,7 +34,7 @@ Maintainer: Proxmox Support Team <support@proxmox.com>
Package: pve-manager
Section: admin
Priority: optional
-Architecture: any
+Architecture: all
Depends: apt (>= 1.5~),
ca-certificates,
cstream,
@@ -97,7 +97,6 @@ Depends: apt (>= 1.5~),
zstd,
${misc:Depends},
${perl:Depends},
- ${shlibs:Depends},
Recommends: libpve-network-perl (>= 0.9~),
proxmox-firewall,
proxmox-offline-mirror-helper,
--
2.46.0
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-09-12 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 14:25 Jing Luo via pve-devel [this message]
2024-09-13 10:09 ` Fabian Grünbichler
2024-09-13 10:55 ` [pve-devel] [PATCH pve-manager v2] " Jing Luo via pve-devel
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=mailman.234.1726153631.414.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=jing@jing.rocks \
/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