From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] tool 'runlevel' conflicts between busybox and systemd
Date: Fri, 15 Nov 2019 14:50:46 +0100 [thread overview]
Message-ID: <20191115135046.GB1287@pengutronix.de> (raw)
In-Reply-To: <2636306.eBN0BePIqA@ada>
Hi,
On Wed, Nov 13, 2019 at 02:03:47PM +0100, Alexander Dahl wrote:
> we got a build error with ptxdist-2019.11.0 when calling `ptxdist images`:
>
>
> Installing busybox (1.29.3) on root.
> To remove package dCollected errors:
> * check_data_file_clashes: Package busybox wants to install file /home/adahl/
> Work/bsp/***/platform-v7a/build-target/image-root-tgz/usr/sbin/runlevel
> But that file is already provided by package * systemd
> * opkg_solver_install: Cannot install package busybox.
> ebris, try `opkg remove busybox`.
> To re-attempt the install, try `opkg install busybox`.
>
>
> This is probably because BUSYBOX_RUNLEVEL and INITMETHOD_SYSTEMD are set at
> the same time. There should be a guard against that (?), but I'm not sure how
> to implement this because those busybox config options are generated, right?
>
> The build error is gone if we deactivate PTXCONF_BUSYBOX_RUNLEVEL.
It should be fixed in busybox, but that's imported. I've started some code
to run a fixup script during import to do stuff like this but I never
finished it... It's still somewhere on my todo list.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-11-15 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 13:03 Alexander Dahl
2019-11-15 13:50 ` Michael Olbrich [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=20191115135046.GB1287@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.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