From: Rakesh Kumar <kumar.rakesh@siemens.com>
To: cip-dev@lists.cip-project.org
Cc: Rakesh Kumar <kumar.rakesh@siemens.com>
Subject: [isar-cip-core][PATCH v2 0/1] recipes-devtools/secure-boot-secrets: Resolve duplicate Provides in debian/control
Date: Fri, 19 Apr 2024 09:20:00 +0530 [thread overview]
Message-ID: <20240419035001.594631-1-kumar.rakesh@siemens.com> (raw)
Previously, the debian/control file contained a duplicate Provides line,
which caused a build failure ad below
| DEBUG: Executing shell function do_dpkg_source
| dpkg-source: error: syntax error in secure-boot-custmpk-0.1/debian/control at line 16:
| duplicate field Provides found
Use DEBIAN_PROVIDES to resolve the duplicate Provides problem to ensure
that the build process completes successfully.
Rakesh Kumar (1):
recipes-devtools/secure-boot-secrets: Resolve duplicate Provides in
debian/control
recipes-devtools/secure-boot-secrets/secure-boot-secrets.inc | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
--
2.39.2
next reply other threads:[~2024-04-19 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 3:50 Rakesh Kumar [this message]
2024-04-19 3:50 ` [isar-cip-core][PATCH v2 1/1] recipes-devtools/secure-boot-secrets: Resolve duplicate Provides in debian/control Rakesh Kumar
2024-04-19 15:04 ` [cip-dev] " Gylstorff Quirin
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=20240419035001.594631-1-kumar.rakesh@siemens.com \
--to=kumar.rakesh@siemens.com \
--cc=cip-dev@lists.cip-project.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).