public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Cc: Henning Schild <henning.schild@siemens.com>
Subject: [PATCH] dpkg-base: apt-get "update" before "source"
Date: Mon, 11 Feb 2019 10:33:24 +0100	[thread overview]
Message-ID: <20190211093324.1444-1-henning.schild@siemens.com> (raw)

From: Henning Schild <henning.schild@siemens.com>

When rebuilding we can run into an inconsistent view where buildchroot
assumes it could download the sources of a modified upstream package.
After a "reprepro ... remove" we always need to "apt-get update" to not
operate on an old version of the metadata.

Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
 meta/classes/dpkg-base.bbclass | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/meta/classes/dpkg-base.bbclass b/meta/classes/dpkg-base.bbclass
index 175dc80..5425df8 100644
--- a/meta/classes/dpkg-base.bbclass
+++ b/meta/classes/dpkg-base.bbclass
@@ -31,6 +31,10 @@ do_apt_fetch() {
 	fi
 	dpkg_do_mounts
 	E="${@ bb.utils.export_proxies(d)}"
+	sudo -E chroot ${BUILDCHROOT_DIR} /usr/bin/apt-get update \
+		-o Dir::Etc::sourcelist="sources.list.d/isar-apt.list" \
+		-o Dir::Etc::sourceparts="-" \
+		-o APT::Get::List-Cleanup="0"
 	sudo -E chroot --userspec=$( id -u ):$( id -g ) ${BUILDCHROOT_DIR} \
 		sh -c 'cd ${PP} && apt-get -y source ${SRC_APT}'
 	dpkg_undo_mounts
-- 
2.19.2


             reply	other threads:[~2019-02-11  9:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11  9:33 Henning Schild [this message]
2019-02-11  9:35 ` Henning Schild
2019-02-11 10:50   ` chombourger
2019-02-11 12:53   ` Jan Kiszka
2019-02-11 13:33     ` chombourger
2019-02-18 14:16       ` Maxim Yu. Osipov
2019-02-11 18:08     ` Henning Schild
2019-02-26 15:00     ` Henning Schild
2019-02-26 15:03       ` Jan Kiszka
2019-03-05 10:11         ` Henning Schild
2019-02-18 22:01 ` Maxim Yu. Osipov

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=20190211093324.1444-1-henning.schild@siemens.com \
    --to=henning.schild@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