[solved] Package 'mc' disappears in clean buildroot environment

For Developers
1

Hi,

found a very strange issue while I'm working on a package update for mc-4.8.20:

I check out the latest LEDE master and run ...

./scripts/feeds update -a
./scripts/feeds install -a

... to update the package feeds as well.
No visible errors so far, but after 'make menuconfig' there is no package 'mc' in the Utilities section.
As a workaround I bring back the mc entry with:

./scripts/feeds install -f mc

LEDE release 17.x works fine.

Any ideas?

2

There's already a flyspray ticket from another user, see here.

3

The root of the problem is that there is a package named mc in the core packages (added as part of NXP layerscape platform on Oct 16). A quick workaround here would be to change the package mc to midnight-commander. In the meantime, I'll look at what can be done to avoid the collision. As it stands now, core packages always take precedence over community packages. Personally, I think the layerscape package name should be changed.

4

Good catch.
I wonder why the new "Management Complex Firmware" package was named "mc" that already existed in the Openwrt/LEDE build system.

sounds reasonable

@dibdot
@blogic

5

Wow, many thanks Ted! :slightly_smiling_face:
I'll prepare a suitable PR.

Best regards
Dirk

6

... or wait to see if someone changes the layerscape package.

7

layerscape package should be changed to ls-mc i think

8

Layerscape packages have been renamed in latest trunk - new package builds should start showing up when the buildbots catch-up.

Ref: https://git.lede-project.org/?p=source.git;a=commit;h=b83c32511e6536112788486448864ca15300a426

9

Thank you very much!