network-manager is broken in dapper

can you please try the latest version from

http://bootlab.org/~j/NetworkManager-breezy/

to see if that works.

this package I build seems to work better. maybe should it be pushed to Universe. No?

On Sat, 2005-11-05 at 20:12 +0000, Hubert Figuiere wrote:
> this package I build seems to work better. maybe should it be pushed to
> Universe. No?

yes, please.

i also have a patched version of bind9 on my site,
you can find more on the dbus patch at
http://bugzilla.gnome.org/show_bug.cgi?id=313086

just saw the clip of your network magick talk.
[ http://video.ubuntu.com/ubz/hub-lightning-3110.ogg ]

some things to add:
 - NetworkManager supports static ip addresses if
   configured in /etc/network/interfaces (without auto stanca);
   however there is currently no way to reload these
   settings without restarting NetworkManager, which is broken.
 - since 0.5, the version that is on my site, NetworkManager
   no longer directly depends on bind9, but on a dbus aware
   dns resolver. it should be rather easy to add dbus functionality
   to i.e. dnsmasq, i even thing there was a patch for it at some
   point.

j

ps: right now upstream started to use libnl, which is not in ubuntu,
    you can find some fast packages at http://bootlab.org/~j/libnl/

wrong url for the bind9-dbus patch, that should have been:
http://bugzilla.ubuntu.com/show_bug.cgi?id=13491

I ran into this problem in dapper also. ~j's package nm-applet runs, except now it seems to think that my open access point is using WEP and it keeps prompting me for a WEP passphrase.

Disregard my last message, I had some self-inflicted dbus issues. Everything is working fine with the packages from bootlab.org

tested that package and solves the problem of asking for a wep key and works beautifully.

Tried to rebuild the packages from bootlab.org for ppc and run into some problems.

1. For bind9-doc.docs, doc/README.DBUS doesn't exist, only doc/misc/README.DBUS

2. I can't compile the nm-applet. I got following output
powerpc-linux-gnu-gcc -Wall -g -O2 -o nm-applet nm_applet-main.o nm_applet-applet.o nm_applet-applet-dbus.o nm_applet-applet-dbus-devices.o nm_applet-applet-dbus-vpn.o nm_applet-applet-dbus-info.o nm_applet-wireless-network.o nm_applet-nm-device.o nm_applet-other-network-dialog.o nm_applet-passphrase-dialog.o nm_applet-menu-items.o nm_applet-eggtrayicon.o nm_applet-vpn-password-dialog.o nm_applet-vpn-connection.o -pthread -Wl,--export-dynamic -pthread -Wl,--export-dynamic -pthread -Wl,--export-dynamic -pthread -ldbus-glib-1 /usr/lib/libhal.so -ldbus-1 /usr/lib/libpanel-applet-2.so -L/usr/lib /usr/lib/libglade-2.0.so /usr/lib/libpangoxft-1.0.so /usr/lib/libpangox-1.0.so /usr/lib/libgnomeui-2.so /usr/lib/libjpeg.so /usr/lib/libbonoboui-2.so -lSM -lICE /usr/lib/libgnomecanvas-2.so /usr/lib/libgnome-2.so /usr/lib/libesd.so /usr/lib/libaudiofile.so /usr/lib/libart_lgpl_2.so /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libgdk_pixbuf-2.0.so /usr/lib/libpangocairo-1.0.so /usr/lib/libpangoft2-1.0.so -lXinerama -lXi -lXrandr -lXext -lXcursor -lXfixes /usr/lib/libpango-1.0.so /usr/lib/libcairo.so -lpng12 -lfontconfig /usr/lib/libfreetype.so -lXrender -lX11 /usr/lib/libgnomevfs-2.so /usr/lib/libxml2.so /usr/lib/libgnutls.so /usr/lib/libtasn1.so /usr/lib/libgcrypt.so -lnsl /usr/lib/libgpg-error.so -lz -lresolv -lrt /usr/lib/libbonobo-2.so /usr/lib/libgconf-2.so /usr/lib/libbonobo-activation.so /usr/lib/libORBitCosNaming-2.so /usr/lib/libORBit-2.so /usr/lib/libpopt.so /usr/lib/libgobject-2.0.so -lm /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libgthread-2.0.so -lpthread /usr/lib/libgnome-keyring.so /usr/lib/libglib-2.0.so ../../utils/.libs/libnmutils.a
/usr/lib/libcairo.so: undefined reference to `FT_GlyphSlot_Embolden'
collect2: ld returned 1 exit status
make[4]: *** [nm-applet] Fehler 1

Okay, after I updated the packages the compilation problem went away. Seems to work fine so far.

When do we can expect the packages in the archives?

Packages based on those on bootlab.org have been in dapper for a while now. Closing this bug.

This is not an upstream bug.

This has been fixed for a while now.

as per comment, not an upstream bug