public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
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] Fwd: [RESEND PATCH pve-manager v2] d/control: change binary package architecture from `any` to `all`
Date: Mon, 23 Sep 2024 12:29:08 +0900	[thread overview]
Message-ID: <mailman.150.1727769306.332.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <20240913110157.1454303-2-jing@jing.rocks>

[-- Attachment #1: Type: message/rfc822, Size: 6985 bytes --]

From: Jing Luo <jing@jing.rocks>
To: pve-devel@lists.proxmox.com
Subject: Fwd: [RESEND PATCH pve-manager v2] d/control: change binary package architecture from `any` to `all`
Date: Mon, 23 Sep 2024 12:29:08 +0900
Message-ID: <dfa2a29663df56db02d24ed35f55fdb8@jing.rocks>

Resend, without a link to the mailing list archive

-------- Original Message --------
Subject: [PATCH pve-manager v2] d/control: change binary package 
architecture from `any` to `all`
Date: 2024-09-13 19:55
 From: Jing Luo <jing@jing.rocks>
To: pve-devel@lists.proxmox.com
Cc: Jing Luo <jing@jing.rocks>, Fabian Grünbichler 
<f.gruenbichler@proxmox.com>

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>
Reviewed-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
Changes since v1:
Change the $(DEB) in Makefile too, forgot to add it in v1 somehow.
---
  Makefile       | 2 +-
  debian/control | 3 +--
  2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/Makefile b/Makefile
index 337682b3..fbd75f51 100644
--- a/Makefile
+++ b/Makefile
@@ -7,7 +7,7 @@ export VERSION = $(DEB_VERSION_UPSTREAM_REVISION)
  BUILDDIR = $(PACKAGE)-$(DEB_VERSION_UPSTREAM)

  DSC=$(PACKAGE)_$(DEB_VERSION).dsc
-DEB=$(PACKAGE)_$(DEB_VERSION)_$(DEB_HOST_ARCH).deb
+DEB=$(PACKAGE)_$(DEB_VERSION)_all.deb

  DESTDIR=
  SUBDIRS = aplinfo PVE bin www services configs network-hooks test 
templates
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

      parent reply	other threads:[~2024-10-01  7:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 14:25 [pve-devel] [PATCH pve-manager] " Jing Luo via pve-devel
2024-09-13 10:09 ` Fabian Grünbichler
2024-09-13 10:55 ` [pve-devel] [PATCH pve-manager v2] " Jing Luo via pve-devel
     [not found] ` <20240913110157.1454303-2-jing@jing.rocks>
2024-09-23  3:29   ` Jing Luo via pve-devel [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=mailman.150.1727769306.332.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal