From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] buildchroot: Allow downgrades when installing packages
Date: Tue, 19 Mar 2019 19:46:36 +0100 [thread overview]
Message-ID: <440e11fa-538a-2388-052b-f31c5b4d8389@siemens.com> (raw)
In-Reply-To: <d629c173-b74f-e236-5dd2-22041370fdf8@ilbers.de>
On 19.03.19 18:33, Maxim Yu. Osipov wrote:
> Hi Jan,
>
> Tried to apply the patch - CI build failed.
>
> See for details:
> http://isar-build.org:8080/job/isar_mosipov_next/164/console
There are multiple errors, most of them seem unrelated to my change because they
are affecting the bootstrap step, and I'm patching the package build:
| debconf: delaying package configuration, since apt-utils is not installed
| Fetched 380 kB in 1s (340 kB/s)
| E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
| (Reading database ... 6945 files and directories currently installed.)
| Preparing to unpack .../libsystemd0_232-25+deb9u9_armhf.deb ...
| Unpacking libsystemd0:armhf (232-25+deb9u9) over (232-25+deb9u8) ...
| Setting up libsystemd0:armhf (232-25+deb9u9) ...
| (Reading database ... 6945 files and directories currently installed.)
| Preparing to unpack .../libudev1_232-25+deb9u9_armhf.deb ...
| Unpacking libudev1:armhf (232-25+deb9u9) over (232-25+deb9u8) ...
| Setting up libudev1:armhf (232-25+deb9u9) ...
| Processing triggers for libc-bin (2.24-11+deb9u4) ...
| umount:
/workspace/build/isar_mosipov_next/164/build/tmp/work/debian-stretch-armhf/isar-bootstrap-target/rootfs/dev:
not mounted
| WARNING: exit code 32 from a shell command.
| ERROR: Function failed: do_bootstrap (log file is located at
/workspace/build/isar_mosipov_next/164/build/tmp/work/debian-stretch-armhf/isar-bootstrap-target/temp/log.do_bootstrap.9153)
You should examine that separately.
The one I'm causing is, sight, once again related to legacy jessie:
| Unpacking libhello-build-deps (0.1) ...
| E: Command line option --allow-downgrades is not understood
| (Reading database ... 16093 files and directories currently installed.)
| Removing libhello-build-deps (0.1) ...
| mk-build-deps: apt-get install call failed
| WARNING: exit code 29 from a shell command.
| ERROR: Function failed: do_install_builddeps (log file is located at
/workspace/build/isar_mosipov_next/164/build/tmp/work/debian-jessie-i386/libhello-0.1-98f2e41-r0/temp/log.do_install_builddeps.481)
This needs apt 1.1, and while strech is on 1.4, jessie was only on 1.0.
OK, as you plan to keep jessor for this release, I would postpone this patch
after 0.7 and the final removal of that old Debian version.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-03-19 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 10:44 Jan Kiszka
2019-02-25 9:39 ` Henning Schild
2019-02-25 9:57 ` Jan Kiszka
2019-02-25 10:15 ` Henning Schild
2019-02-25 11:08 ` Jan Kiszka
2019-03-19 10:10 ` Baurzhan Ismagulov
2019-03-19 10:31 ` Jan Kiszka
2019-03-19 17:33 ` Maxim Yu. Osipov
2019-03-19 18:46 ` Jan Kiszka [this message]
2019-03-04 9:04 ` Claudius Heine
2019-03-04 9:08 ` Jan Kiszka
2019-03-28 12:42 ` 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=440e11fa-538a-2388-052b-f31c5b4d8389@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@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