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 proxmox-ve-rs 1/3] d/control: correct source package name
Date: Thu, 21 Nov 2024 19:06:49 +0900 [thread overview]
Message-ID: <mailman.523.1732183833.391.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 5094 bytes --]
From: Jing Luo <jing@jing.rocks>
To: pve-devel@lists.proxmox.com
Cc: Jing Luo <jing@jing.rocks>
Subject: [PATCH proxmox-ve-rs 1/3] d/control: correct source package name
Date: Thu, 21 Nov 2024 19:06:49 +0900
Message-ID: <20241121100917.1209701-1-jing@jing.rocks>
Currently the "dsc" target fails and dpkg-buildpackage complains:
error: can't build with source format '3.0 (quilt)': no upstream tarball found at ../proxmox-ve-config_0.2.0.orig.tar.{bz2,gz,lzma,xz}
but there is a "rust-proxmox-ve-config_0.2.0.orig.tar.gz". Usually a rust
package in debian starts with "rust-" in its source package name.
Signed-off-by: Jing Luo <jing@jing.rocks>
---
proxmox-ve-config/debian/control | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/proxmox-ve-config/debian/control b/proxmox-ve-config/debian/control
index f5a9993..4be4417 100644
--- a/proxmox-ve-config/debian/control
+++ b/proxmox-ve-config/debian/control
@@ -1,4 +1,4 @@
-Source: proxmox-ve-config
+Source: rust-proxmox-ve-config
Section: rust
Priority: optional
Maintainer: Proxmox Support Team <support@proxmox.com>
--
2.47.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
reply other threads:[~2024-11-21 10:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.523.1732183833.391.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