This bug was fixed in the package connectivity-api -
0.0.1+15.04.20141215-0ubuntu1
---
connectivity-api (0.0.1+15.04.20141215-0ubuntu1) vivid; urgency=low
[ Antti Kaijanmäki ]
* debian/control: only Recommend indicator-network. (LP: #1400502)
[ Albert Astals ]
* Remove unused
This bug was fixed in the package indicator-network -
0.5.1+15.04.20141215-0ubuntu1
---
indicator-network (0.5.1+15.04.20141215-0ubuntu1) vivid; urgency=low
[ Antti Kaijanmäki ]
* debian/control: add Multi-Arch: foreign (LP: #1400502)
-- Ubuntu daily releaseMon, 15 Dec 2014
** Branch linked: lp:~unity-api-team/connectivity-api/packaging-
modifications.15.04
** Branch linked: lp:~unity-api-team/indicator-network/packaging-
modifications-15.04
** Changed in: connectivity-api (Ubuntu)
Status: Confirmed => In Progress
** Changed in: indicator-network (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-network (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400502
T
shouldn't indicator-network be Multi-Arch: foreign instead?
that would cause libconnectivity-qt1's dependency on it to be
fulfilled by the native architecture
(https://wiki.ubuntu.com/MultiarchSpec#Dependencies_involving_Architecture:_all_packages)
It depends on the kinds of technical interfa
Easily reproducible by, on a amd64 system, going:
$ LANG=C sudo apt-get install libconnectivity-qt1:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situati
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: connectivity-api (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400502
Ti
