[opensuse-gnome] Request for help: updating NetworkManager
I've found some problems in our NetworkManager that affect all clients. Most importantly, GSM mobile broadband seems to be broken NM-side. Any attempt to connect using factory NM and nm-applet hangs with: NetworkManager: real_connection_secrets_updated: assertion `caller == SECRETS_CALLER_GSM' failed OpenVPN connections fail too. These problems are common to both the gnome and KDE applets and I would hate 11.2 to go out broken. I would like to update the package (in a OBS branch) to git master to see if this solves it and is a net benefit. Raymond Wooninck and I have updated NetworkManager itself to 0.7.1 branch, but the assert remains, because it's in the use-modem-manager patch. Updating the patch to modem-manager master and making it fit NM 0.7 branch is possible but would probably be hard work and a maintenance burden. Fedora and Ubuntu are both shipping master in their autumn releases. What do you think? If this is not a Terrible Idea, I could really use gnome-packaging expertise here. There is some part of the NM/GNOME release process that I don't understand - git archive tarballs don't build, I took Ubuntu's package apart and stuffed its sources in our specfile but that doesn't build either due to a missing po/configure.in.in. How do I get a packageable tarball? Will -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
Le mardi 18 août 2009, à 10:20 +0200, Will Stephenson a écrit :
If this is not a Terrible Idea, I could really use gnome-packaging expertise here. There is some part of the NM/GNOME release process that I don't understand - git archive tarballs don't build, I took Ubuntu's package apart and stuffed its sources in our specfile but that doesn't build either due to a missing po/configure.in.in. How do I get a packageable tarball?
No idea what's in the tarball, but there could be various reasons for this. Maybe you just need to run the autogen.sh script. If you publish the tarball you have, I can take a look :-) Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Tuesday 18 August 2009 10:30:00 you wrote:
Le mardi 18 août 2009, à 10:20 +0200, Will Stephenson a écrit :
If this is not a Terrible Idea, I could really use gnome-packaging expertise here. There is some part of the NM/GNOME release process that I don't understand - git archive tarballs don't build, I took Ubuntu's package apart and stuffed its sources in our specfile but that doesn't build either due to a missing po/configure.in.in. How do I get a packageable tarball?
No idea what's in the tarball, but there could be various reasons for this. Maybe you just need to run the autogen.sh script. If you publish the tarball you have, I can take a look :-)
osc co home:wstephenson:branches:GNOME:Factory NetworkManager I had to add a "gtkdocize" - does this mean that normally this is run before the release tarball is made? Will -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
Le mardi 18 août 2009, à 10:55 +0200, Will Stephenson a écrit :
I had to add a "gtkdocize" - does this mean that normally this is run before the release tarball is made?
Yes. You can use gnome-autogen.sh from gnome-common to setup all the right things. See http://en.opensuse.org/GNOME/Packaging/Quirks#autoreconf_vs_gnome-common (which should be updated to mentioned git tarballs) Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
Le mardi 18 août 2009, à 11:08 +0200, Vincent Untz a écrit :
Le mardi 18 août 2009, à 10:55 +0200, Will Stephenson a écrit :
I had to add a "gtkdocize" - does this mean that normally this is run before the release tarball is made?
Yes. You can use gnome-autogen.sh from gnome-common to setup all the right things. See http://en.opensuse.org/GNOME/Packaging/Quirks#autoreconf_vs_gnome-common (which should be updated to mentioned git tarballs)
(although in this specific case, you have an autogen.sh script and no configure, so you should really just call autogen.sh) Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Tuesday 18 August 2009 11:08:40 Vincent Untz wrote:
Le mardi 18 août 2009, à 10:55 +0200, Will Stephenson a écrit :
I had to add a "gtkdocize" - does this mean that normally this is run before the release tarball is made?
Yes. You can use gnome-autogen.sh from gnome-common to setup all the right things. See http://en.opensuse.org/GNOME/Packaging/Quirks#autoreconf_vs_gnome-common (which should be updated to mentioned git tarballs)
I think for NM itself I should not drag gnome-common into it or the build team will skin me. With gtkdocize it still breaks on missing po/Makefile.in.in (not configure.in.in as stated before). Will -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
participants (2)
-
Vincent Untz -
Will Stephenson