From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bth@kamstrup.com>, Mircea Ciocan <m.ciocan@ppc-ag.de>
Subject: Re: [ptxdist] Clash between busybox bc and GNU bc
Date: Mon, 06 Jul 2020 15:19:06 +0200 [thread overview]
Message-ID: <99644846.PknQacu39s@ada> (raw)
In-Reply-To: <AM0PR04MB697703A645750DD0A843BF1CDC690@AM0PR04MB6977.eurprd04.prod.outlook.com>
Hei hei,
Am Montag, 6. Juli 2020, 15:13:04 CEST schrieb Bruno Thomsen:
> > compiling a a firmware with the latest (2020.07.0) ptxdist I've got the
> >
> > following package clash error:
> > * check_data_file_clashes: Package busybox wants to install file
> >./platform-MCIMX6ULL-EVK/build-target/image-root-tgz/usr/bin/bc
> > But that file is already provided by package * bc
> > * opkg_solver_install: Cannot install package busybox.
>
> Remove selection from BUSYBOX_BC as it conflicts with bc package.
>
> I just hit the same issue ;)
Would one of you care to send a patch? There are numerous other packages with
the same problem which come with some kind of guard. See e.g. 'less' or 'tar'.
Greets
Alex
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2020-07-06 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 13:09 Mircea Ciocan
2020-07-06 13:13 ` Bruno Thomsen
2020-07-06 13:19 ` Alexander Dahl [this message]
2020-07-06 13:21 ` [ptxdist] [PATCH] bc: prevent file name clash with busybox' bc Roland Hieber
2020-07-06 13:26 ` [ptxdist] [PATCH v2] " Roland Hieber
2020-07-07 5:45 ` [ptxdist] [APPLIED] " Michael Olbrich
2020-07-06 13:33 ` [ptxdist] [PATCH] " Alexander Dahl
2020-07-06 13:50 ` Roland Hieber
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=99644846.PknQacu39s@ada \
--to=ada@thorsis.com \
--cc=bth@kamstrup.com \
--cc=m.ciocan@ppc-ag.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