Make error - Cannot install packages (busybox dnsmasq ...)

[JW0914]

@toper

* check_data_file_clashes: Package dropbear wants to install file /home/toper/owrt_lede/lede/build_dir/target-mipsel_mips32_musl/root-rb532/usr/bin/scp
            But that file is already provided by package  * openssh-client
     * check_data_file_clashes: Package dropbear wants to install file /home/toper/owrt_lede/lede/build_dir/target-mipsel_mips32_musl/root-rb532/usr/bin/ssh
            But that file is already provided by package  * openssh-client
     * opkg_install_cmd: Cannot install package dropbear.

If you have more than 8MB of ROM, ditch dropbear and install openssh-server

• OpenSSH has the scp binary, hence why you're getting that error, per @hnyman's explanation
  
  

@toper

  * check_data_file_clashes: Package busybox wants to install file /home/toper/owrt_lede/lede/build_dir/target-mipsel_mips32_musl/root-rb532/usr/sbin/brctl
         But that file is already provided by package  * bridge
  * opkg_install_cmd: Cannot install package busybox.

Same reasoning as before... busybox's binary brctl was marked Y, therefore the same binary cannot be installed by bridge

I've found that it's easier if you customize BusyBox either last, or first, depending on whether image size is an issue.

• If size is an issue due to ROM constraints, customize BusyBox first, as BusyBox's binaries are smaller in size than the full binaries.
  
  
• If size is not an issue, customize BusyBox last
  • Go through and select all the packages you want, then build the image without any BusyBox customization
    • This ensures there's no errors, as you don't want to have to troubleshoot regular make errors for packages and make errors for BusyBox at the same time.
      
      
  • Once your image compiles successfully, go back in to menuconfig and customize BusyBox, run make V=s, then go back through and de-select whatever options are causing errors.
    • When I first began compiling my own images, I found it easier to customize BusyBox by it's categories, and once done with one category, I'd run make. This allowed me to specifically know where I needed to look if a compiling error occurred.

Whichever way you choose to do it, I recommend using Build Environments, as it makes reverting much easier.