--- Begin Message ---
Hi guys,
critics accepted.
I've tried to upgrade NetworkManager many times, first the 0.6.5 - which
worked better than 0.6.4, but always crashed for WPA2 - then 0.7 git and
often just failed with it. Major problems were caused by updating libnl and a
somehow broken glib2.
I forgot to mention what problems updating libnl can cause, as we both, Tobias
and I, know about that because of earlier experiments (first in dynamite that
also broke NM, then in my branch). But I was not even close to expect, that
the mere update of wireless-tools could cause any problems at all. From now
on, I'll always check the reverse dependencies of the respective package.
Newest status with networkmanager: Apparently the 0.7 (0.6.9) build in
dynamite does work, but we don't have any working graphical frontend for it,
so we can't use that either - even knetworkmanager 0.2 does not support it.
0.6.4 is too unstable for my taste, that's why I'm experimenting with NUT,
that should behave much better than NetworkManager (though without any
hardware detection), but for example finally add proper static IP support.
The wireless-tools update was needed for NUT, as it uses the bleeding edge
iwlib.h API.
I'd also recommend adding more strict dependency specifications to the spec
files, meaning: the exact version number (release is not needed, I think).
This way a system should not upgrade a package, unless it would not break
others.
Regards
Armin
> Hi guys,
>
> Like Tobias, I'm not interested in the personal offence at all, just to
> make things work as the better as we all together can. I have also no
> problen to sayI was the packager that upgraded libnl 3 weeks ago (4th
> august to be accure), but as far as I can remember, I talked about it with
> Tobias and Armin. The reason why I upgraded this package was because I
> tried to upgrade to NetworkManager 0.66 to fix several security and
> usability issues and then I got a series of problems in this. Unless I'm
> wrong, this hasn't caused any problem the following days since my upgrade
> and also thought that Armin (our network guru) would deal with the upgrade
> to NetworkManager 0.66 as he told many times he was interesed in it...
>
> Please, don't be afraid of letting me know whether I have broken anything
> as I would be VERY HAPPY to fix it all.
>
> Besides the above, just want to add a small comment to the other Tobias
> email too. You can add the --dry-run swith to the script Tobias mentioned
> (bump-buildreq.sh), not to bump any spec file, but simply get a list of
> affected packages. This way you can see all the work it will take an
> upgrade before doing any action.
>
> Regards! :-)
>
> > Date: Mon, 25 Aug 2008 18:44:41 +1200
> > From: [EMAIL PROTECTED]
> > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > Subject: wireless-tools & libnl version incompatibilities
> >
> > Hi ,
> >
> > Just stating facts here and looking for solution. Not interested in
> > personal offense. So, one of you updated libnl , the other one updated
> > wireless-tools. Neither of you checked the dependencies. Now is
> > NetworkManager at version 0.6.4 and does not install. Upgrading it
> > does break wpa functionality.
> >
> > I assume both of you have an agenda for the networking tools, hence
> > the version upgrade. So what do we do ?
> >
> > I'd like to continue working on the iso builds to improve their out of
> > the box quality.
> >
> >
> > cheers
> >
> > --
> > Tobias Gerschner
> > Yoper Linux - www.yoper.com
> >
> > Knowing is not enough; we must apply. Willing is not enough; we must do.
>
> _________________________________________________________________
> ¡El Mundo Messenger te espera! Entra ya en "I love Messenger" y descubre
> las últimas novedades, trucos, emoticonos…
> http://www.vivelive.com/ilovemessenger/
--- End Message ---
_______________________________________________
yoper-dev mailing list
yoper-dev@lists.yoper.com
http://lists.frank-hosting.de/cgi-bin/mailman/listinfo/yoper-dev
