From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Cc: Cedric Hombourger <Cedric_Hombourger@mentor.com>,
Henning Schild <henning.schild@siemens.com>
Subject: [PATCH 2/3] debianize: prepend changelog entries
Date: Mon, 6 Sep 2021 10:34:02 +0200 [thread overview]
Message-ID: <20210906083403.25163-2-henning.schild@siemens.com> (raw)
In-Reply-To: <20210906083403.25163-1-henning.schild@siemens.com>
Make sure to include the upstream changelog and prepend our entry.
Before that change i.e. hello would end up with a changelog containing
only our entry. After that we will get the full upstream changelog and
our prepended entry.
Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
meta/classes/debianize.bbclass | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/meta/classes/debianize.bbclass b/meta/classes/debianize.bbclass
index e6a300700a5f..386c34149b5b 100644
--- a/meta/classes/debianize.bbclass
+++ b/meta/classes/debianize.bbclass
@@ -34,6 +34,12 @@ ${PN} (${changelog_v}) UNRELEASED; urgency=low
-- ${MAINTAINER} ${date}
EOF
+ if [ -f ${WORKDIR}/changelog.orig ]; then
+ # prepend our entry to the original changelog
+ echo >> ${S}/debian/changelog
+ cat ${WORKDIR}/changelog.orig >> ${S}/debian/changelog
+ fi
+
if [ -f ${WORKDIR}/changelog ]; then
latest_version=$(dpkg-parsechangelog -l ${WORKDIR}/changelog -S Version)
if [ "${latest_version}" = "${changelog_v}" ]; then
--
2.32.0
next prev parent reply other threads:[~2021-09-06 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 8:34 [PATCH 1/3] debianize: make changelog date reproducible Henning Schild
2021-09-06 8:34 ` Henning Schild [this message]
2021-09-06 8:34 ` [PATCH 3/3] isar-exclude-docs: include "native" package changelogs Henning Schild
2021-09-21 7:24 ` Henning Schild
2021-09-07 12:55 ` [PATCH 1/3] debianize: make changelog date reproducible Anton Mikanovich
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=20210906083403.25163-2-henning.schild@siemens.com \
--to=henning.schild@siemens.com \
--cc=Cedric_Hombourger@mentor.com \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox