public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v3 0/1] deb-dl-dir: Use dpkg-deb --field in debsrc_download
Date: Tue, 22 Feb 2022 09:38:15 +0300	[thread overview]
Message-ID: <57b47cac-0c42-7bc7-c938-58b849e112ab@ilbers.de> (raw)
In-Reply-To: <20220213073606.27476-1-ubely@ilbers.de>

13.02.22 10:36, Uladzimir Bely wrote:
> Debian `control` file inside .deb package may not contain `Source` field.
> So, this field is virtual and the simplest way to request it - using
> ${source:Package} and ${source:Version} on "dpkg-deb --show --showformat".
>
> While in bullseye this is currently broken, the patch simply emulates
> the same logic using dpkg-deb --field. Initially, we try to get source
> package name and version using from `Source` field and if it fails, we
> just use `Package` and `Version` values.
>
> Changes since v2:
> - Replaced if/then/fi by one-line alternative
> - Added comments in the code about reverting the patch when bug #1004372
> in Debian is fixed
>
> Changes since v1:
> - Fixed commit message (should be BASE_REPO_FEATURES ?= "cache-deb-src",
> but not ISAR_USE_CACHED_BASE_REPO)
>
> Uladzimir Bely (1):
>    deb-dl-dir: Use dpkg-deb --field in debsrc_download
>
>   meta/classes/deb-dl-dir.bbclass | 11 +++++++++--
>   1 file changed, 9 insertions(+), 2 deletions(-)
>
Applied to next, thanks.


      parent reply	other threads:[~2022-02-22  6:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-13  7:36 Uladzimir Bely
2022-02-13  7:36 ` [PATCH v3 1/1] " Uladzimir Bely
2022-02-16  5:23   ` vijaikumar....@gmail.com
2022-02-22  6:38 ` Anton Mikanovich [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=57b47cac-0c42-7bc7-c938-58b849e112ab@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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