bb-wl18xx-firmware depends on connman!?

jch@beaglebone:~$ apt-cache depends bb-wl18xx-firmware
bb-wl18xx-firmware
  Depends: bc
  Depends: bsdmainutils
  Depends: connman
  Depends: coreutils
  Depends: dnsmasq

So now I cannot install the wireless firmware without installing connman
and dnsmasq?

-- Juliusz

This is to support the out of box AP mode. Those two depends can be reworked in the bb-tether script.

Regards,

bb-wl18xx-firmware
  Depends: bc
  Depends: bsdmainutils
  Depends: connman
  Depends: coreutils
  Depends: dnsmasq

This is to support the out of box AP mode. Those two depends can be
reworked in the bb-tether script.

The current dependencies make it *impossible* to install the firmware
without installing connman (which in turn conflicts with resolvconf).
A low-level piece of firmware should certainly not depend on high-level
infrastructure (connman, dnsmasq).

Robert, please rework things so that your script depends on both the
firmware and connman, while the firmware itself has no dependencies.
(Make a dummy package if you wish.) The current situation makes it
impossible to upgrade the firmware for those of us who prefer just
a little bit less of black magic in our network configuration.

-- Juliusz

The git version of connman, we push out shouldn’t conflict with resolvconf. (It did up until a few months ago…)

While yes true, it grew it to ‘fix’ the 2016-11 image releases.

Regards,

bb-wl18xx-firmware
Depends: bc
Depends: bsdmainutils
Depends: connman
Depends: coreutils
Depends: dnsmasq

I've rebuilt the package without the spurious dependency. It solves my
local problem, at least until the next upgrade.

A low-level piece of firmware should certainly not depend on high-level
infrastructure (connman, dnsmasq).

While yes true, it grew it to 'fix' the 2016-11 image releases.

Robert, you could either downgrade the Depends to a Recommends (which is
basically a Depends, but can be easily overridden by the user), or, even
better, split the package into a -firmware package and a -tether, with
the latter depending on the former.

-- Juliusz

This is the change i implemented..

https://github.com/rcn-ee/repos/commit/cc43ffb0374efb0e219863621927f5bc29b12212

Of course, after landing in Portland for ELC, turns out my build farm
sbuild tar got corrupted over the weekend..

So yeah, till i rebuild the debian sbuild tar files and push it out to
the build farm can't do much.. crap

I fly back Saturday

Regards,

Okay, rebuilt the corrupted sbuild tar, and pushed out the package

Regards,

This is the change i implemented..

https://github.com/rcn-ee/repos/commit/cc43ffb0374efb0e219863621927f5bc29b12212

Perfect, thanks.

-- Juliusz