From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: dpkg: error: cannot stat pathname '/tmp/apt-dpkg-install...
Date: Mon, 26 Aug 2019 22:59:52 +0200 [thread overview]
Message-ID: <20190826205952.GI6062@yssyq.m.ilbers.de> (raw)
In-Reply-To: <c3ee5275-46b1-ca26-9fdd-8e24863ff36f@siemens.com>
On Mon, Aug 26, 2019 at 10:22:21PM +0200, Jan Kiszka wrote:
> 2019-08-26 19:12:59 - ERROR - ERROR: mc:ultra96-jailhouse-demo:demo-image-1.0-r0 do_rootfs_install: Function failed: rootfs_install_pkgs_install (log file is located at /builds/ebsy/debian/build/tmp/work/jailhouse-demo-arm64/demo-image-ultra96-wic-img/1.0-r0/temp/log.do_rootfs_install.60341)
> [...]
> 2019-08-26 19:12:59 - INFO - | DEBUG: Executing shell function rootfs_install_pkgs_install
> [...]
> 2019-08-26 19:12:59 - INFO - | Get:7 file:/isar-apt isar/main arm64 u-boot-tools arm64 2019.01-atf1.6 [93.1 kB]
> [...]
> 2019-08-26 19:12:59 - INFO - | Setting up python-minimal (2.7.13-2) ...
> 2019-08-26 19:12:59 - INFO - | dpkg: error: cannot stat pathname '/tmp/apt-dpkg-install-iVLVJB/57-u-boot-tools_2019.01-atf1.6_arm64.deb': No such file or directory
> 2019-08-26 19:12:59 - INFO - | E: Sub-process /usr/bin/dpkg returned an error code (2)
Wow, I remember having seen this task failing in the past, but not such
straight ENOENT. Is this reproducible?
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-08-26 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 20:22 Jan Kiszka
2019-08-26 20:59 ` Baurzhan Ismagulov [this message]
[not found] ` <136f3300-8dc3-5f42-13fc-4c04414f7801@siemens.com>
2019-09-02 8:08 ` isar-apt locking: install_imager_deps vs rootfs_install (was: Re: dpkg: error: cannot stat pathname '/tmp/apt-dpkg-install...) Jan Kiszka
2019-09-18 13:39 ` Baurzhan Ismagulov
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=20190826205952.GI6062@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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