public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Quirin Gylstorff <Quirin.Gylstorff@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH] libubootenv: Update to 0.3.5
Date: Wed, 3 Jan 2024 11:39:05 +0100	[thread overview]
Message-ID: <5f2b2fcc-9058-48a6-adb4-c4a8e8709cd9@siemens.com> (raw)
In-Reply-To: <20240103102305.823320-1-Quirin.Gylstorff@siemens.com>

On 03.01.24 11:19, 'Quirin Gylstorff' via isar-users wrote:
> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> 
> Update to latest version in debian salsa.
> Use dpkg as pristine-tar is no longer in use.

What features does this update bring? Should it (also/rather) be a
bookworm-backports topic?

Jan

> 
> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> ---
>  ...ootenv_0.3-3.bb => libubootenv_0.3.5-0.1.bb} | 17 ++++++++++++-----
>  1 file changed, 12 insertions(+), 5 deletions(-)
>  rename meta/recipes-bsp/libubootenv/{libubootenv_0.3-3.bb => libubootenv_0.3.5-0.1.bb} (65%)
> 
> diff --git a/meta/recipes-bsp/libubootenv/libubootenv_0.3-3.bb b/meta/recipes-bsp/libubootenv/libubootenv_0.3.5-0.1.bb
> similarity index 65%
> rename from meta/recipes-bsp/libubootenv/libubootenv_0.3-3.bb
> rename to meta/recipes-bsp/libubootenv/libubootenv_0.3.5-0.1.bb
> index dee19c0b..08eab73c 100644
> --- a/meta/recipes-bsp/libubootenv/libubootenv_0.3-3.bb
> +++ b/meta/recipes-bsp/libubootenv/libubootenv_0.3.5-0.1.bb
> @@ -12,11 +12,18 @@ LIC_FILES_CHKSUM = "file://${LAYERDIR_isar}/licenses/COPYING.GPLv2;md5=751419260
>  
>  PROVIDES = "libubootenv-tool libubootenv-dev libubootenv-doc libubootenv0.1"
>  
> -inherit dpkg-gbp
> +inherit dpkg
>  
> -SRC_URI = "git://salsa.debian.org/debian/libubootenv.git;protocol=https;branch=master"
> -SRCREV = "a1a3504e5cda1883928a8747a0bedc56afff6910"
> -
> -S = "${WORKDIR}/git"
> +SRC_URI = "git://salsa.debian.org/debian/libubootenv.git;protocol=https;branch=master;destsuffix=${P}"
> +SRCREV = "32dcabeea9ed5342a2d1bb254bb4839e2e68ee5e"
>  
>  DEB_BUILD_OPTIONS += "nocheck"
> +
> +
> +CHANGELOG_V ?= "${PV}+isar-${SRCREV}"
> +
> +do_prepare_build() {
> +    deb_add_changelog
> +    cd ${WORKDIR}
> +    tar cJf ${PN}_${PV}+isar.orig.tar.xz --exclude=.git --exclude=debian ${P}
> +}

-- 
Siemens AG, Technology
Linux Expert Center


  reply	other threads:[~2024-01-03 10:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 10:19 Quirin Gylstorff
2024-01-03 10:39 ` Jan Kiszka [this message]
2024-01-03 14:09   ` Gylstorff Quirin
2024-01-04  8:46   ` Michael Adler
2024-01-04  9:10     ` Jan Kiszka

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=5f2b2fcc-9058-48a6-adb4-c4a8e8709cd9@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Quirin.Gylstorff@siemens.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