NetworkManager-0.9.95 update in rawhide
dcbw at redhat.com
Tue Jun 17 14:40:54 UTC 2014
On Wed, 2014-06-11 at 12:00 +0400, Igor Gnatenko wrote:
> On Tue, Jun 10, 2014 at 11:19 PM, Dan Williams <dcbw at redhat.com> wrote:
> > On Tue, 2014-06-10 at 21:37 +0400, Igor Gnatenko wrote:
> >> On Tue, Jun 10, 2014 at 9:34 PM, Thomas Haller <thaller at redhat.com> wrote:
> >> > On Tue, 2014-06-10 at 21:25 +0400, Igor Gnatenko wrote:
> >> >> Hi,
> >> >>
> >> >> After latest update i can't use my wifi in NM. Probably this bug not
> >> >> in NM, but I don't know how to debug this :(
> >> >
> >> > Do you have the package NetworkManager-wifi installed?
> >> no. Interesting.
> >> >
> >> > Check with
> >> > $ yum list NetworkManager-wifi
> >> >
> >> >
> >> > and you certainly need it. Actually, you should have gotten it
> >> > automatically...
> >> What's happens? Checking dnf logs.
> > As Igor and I discussed on IRC, the new NetworkManager package and
> > sub-packages include "Obsoletes: NetworkManager < 1:0.9.9.95-1" which
> > should cause *all* the subpackages (including NetworkManager-wifi) to
> > replace the previous packages, and thus NM-wifi should be installed.
> > We're checking with dnf people to figure out why this doesn't seem to be
> > the case. I tested with 'yum' and a local repo before building the F21
> > update and this worked correctly, so at the moment the issue seems to be
> > with dnf.
No response yet about what the expected procedure for package splitting
is with DNF, since it obviously does it differently than yum. I think
before we switch over to DNF, we should solve this question. Either:
1) DNF should use the same algorithm for obsoletes as yum did, so that
package splitting works the same way as yum
2) Somebody should update the packaging guidelines to explain exactly
how DNF expects package splitting to work, and then I'll update the NM
RPMS to use this method
More information about the devel