From: Anton Mikanovich <amikan@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH v2 0/2] RFC: Package perf from linux kernel tools
Date: Tue, 9 Feb 2021 11:58:31 +0300 [thread overview]
Message-ID: <66cc8ed1-12c0-3d06-ed7e-8981df14811d@ilbers.de> (raw)
In-Reply-To: <20210121105224.26285-1-felix.moessbauer@siemens.com>
21.01.2021 13:52, Felix Moessbauer wrote:
> Hi,
>
> thanks for your input that is reflected in the following patchsets.
>
> Changes since v1:
>
> - package as part of kernel recipe
> - put python patch in dedicated commit
> - add support for 5.4 kernels
> - enable users to provide custom patches
>
> One pain point is still that we have to copy the patches
> from upstream debian. IMO it would be better to just fetch
> them, but then we would have to somehow map to a branch on
> salsa. Any recommendations?
>
> Best regards,
> Felix
Hello, this patchset causes CI to fail on building linux-mainline-5.4.70
at mk-build-deps stage:
>11:24:13 ERROR: mc:de0-nano-soc-buster:linux-mainline-5.4.70-r0
do_install_builddeps: Execution of
'/workspace/build/isar_am_devel_fast/80/build/tmp/work/debian-buster-armhf/linux-mainline/5.4.70-r0/temp/run.do_install_builddeps.14242'
failed with exit code 1:
>...
>11:24:13 dpkg-deb: building package 'linux-mainline-cross-build-deps'
in '../linux-mainline-cross-build-deps_5.4.70+r0_armhf.deb'.
>...
>11:24:13 Correcting dependencies...Starting pkgProblemResolver with
broken count: 2
>11:24:13 Starting 2 pkgProblemResolver with broken count: 2
>11:24:13 Investigating (0) python3:amd64 < 3.7.3-1 @ii mK Ib >
>11:24:13 Broken python3:amd64 PreDepends on python3-minimal:amd64 <
3.7.3-1 @ii mR > (= 3.7.3-1)
>11:24:13 Considering python3-minimal:amd64 -1 as a solution to
python3:amd64 3
>11:24:13 Added python3-minimal:amd64 to the remove list
>...
>11:24:13 The following packages will be REMOVED:
>11:24:13 devscripts linux-mainline-cross-build-deps:armhf python3
python3-minimal
>11:24:13 python3.7 python3.7-minimal
>...
>11:24:13 0 upgraded, 21 newly installed, 6 to remove and 0 not upgraded.
>11:24:13 1 not fully installed or removed.
>...
>11:24:13 mk-build-deps: Unable to install
linux-mainline-cross-build-deps at /usr/bin/mk-build-deps line 416.
>11:24:13 mk-build-deps: Unable to install all build-dep packages
>11:24:13 mk-build-deps: Unable to install all build-dep packages
>...
>11:24:13 NOTE: recipe linux-mainline-5.4.70-r0: task
do_install_builddeps: Failed
Full log:
http://ci.isar-build.org:8080/job/isar_am_devel_fast/80/consoleFull
Did you miss python patch for 5.4 also?
--
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2021-02-09 8:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 12:41 [PATCH 0/1] " Felix Moessbauer
2021-01-19 12:41 ` [PATCH 1/1] " Felix Moessbauer
2021-01-19 16:31 ` Baurzhan Ismagulov
2021-01-20 15:23 ` Moessbauer, Felix
2021-01-20 15:26 ` Henning Schild
2021-01-21 10:52 ` [PATCH v2 0/2] " Felix Moessbauer
2021-01-21 11:56 ` Jan Kiszka
2021-01-21 15:00 ` Moessbauer, Felix
2021-01-21 16:35 ` Jan Kiszka
2021-02-09 8:58 ` Anton Mikanovich [this message]
2021-02-17 10:18 ` Baurzhan Ismagulov
2021-01-21 10:52 ` [PATCH 1/2] feat: package linux-perf-<version> in kernel recipe Felix Moessbauer
2021-02-17 10:28 ` Baurzhan Ismagulov
2021-02-18 8:01 ` Moessbauer, Felix
2021-02-18 8:28 ` Jan Kiszka
2021-04-22 9:52 ` Anton Mikanovich
2021-04-27 9:24 ` [RFC v2 0/2] " Felix Moessbauer
2021-04-27 9:24 ` [PATCH v2 1/2] RFC: Package perf from linux kernel tools Felix Moessbauer
2021-04-27 9:24 ` [PATCH v2 2/2] Add wrapper to load correct python perf module based on kernel Felix Moessbauer
2021-01-21 10:52 ` [PATCH 2/2] feat: add and package python bindings for perf Felix Moessbauer
2021-01-20 11:12 ` [PATCH 0/1] RFC: Package perf from linux kernel tools Henning Schild
2021-01-20 11:21 ` Henning Schild
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=66cc8ed1-12c0-3d06-ed7e-8981df14811d@ilbers.de \
--to=amikan@ilbers.de \
--cc=felix.moessbauer@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