[Pkg-utopia-maintainers] Bug#612291: Bug#612291: Bug#612291: Acknowledgement (network-manager and network-manager-gnome must be of the same version)

[Michael Biebl]

Am 07.02.2011 17:09, schrieb Michael Biebl:
> On 07.02.2011 14:32, Pierre Habouzit wrote:
>> Btw, the bug is on nm because it has /at least/ to be updated with a
>>
>>     Breaks: network-manager-gnome << 0.8.2
>>
>> To be compatible with what is in squeeze.
> 
> That is one possibility. Ideally 0.8.1 nm-applet should continue to work with nm
> 0.8.2, though.
> 
> I'll try to reproduce the problem locally and see what' going on.

Here are my test results so far:

Today I've setup a squeeze installation with nm 0.8.1 and nm-applet 0.8.1.
I created a VPN (PPTP) connection, a DHCP, DHCP (addresses only) and static
configuration for my wireless interface.
Then I upgraded network-manager to 0.8.2 and kept nm-applet at 0.8.1.
Everything continued to work fine.

I went back to nm 0.8.1 and created a connection for my ethernet interface.
I then upgraded nm to 0.8.2 I indeed got a failure.
NetworkManager --log-level=debug does not output anything interesting.
I noticed though, that when starting nm-applet 0.8.1, I get the following output:

** (nm-applet:24735): WARNING **: Unhandled setting property type (read):
'802-3-ethernet/s390-subchannels' : 'GPtrArray_gchararray_'
** (nm-applet:24735): WARNING **: Invalid connection
/system/networking/connections/5: 'NMSettingWired' / 's390-options' invalid: 1

And as a result the wireless connection I created is not shown in the context
menu of nm-applet and no connection is activated.

If I upgrade nm-applet to 0.8.2 and restart it, the two warnings are gone and
nm-applet successfully establishes the connection via ethernet.

Afaics, the s390 options for ethernet were indeed added between 0.8.1 and 0.8.2.

I don't quite understand the mechanisms here.
Dan, are those s390 options now mandatory and need to be passed from the client
to NetworkManager? Why does nm-applet fail here? Are new API additions / options
supposed to create problems on the client side?
Is this maybe actually a client / nm-applet problem?

Dan, are nm-applet and nm really supposed to be of the exact same version or do
you try to keep them compatible during "stable" revisions?

FWIW, as I need to get a few fixes into testing I'll add the Breaks: to
network-manager for now, so the package can migrate.
Hopefully we can find a different solution, which doesn't impose such strict
version requirements and I'd lift the Breaks later again.

Cheers,
Michael



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-utopia-maintainers/attachments/20110306/10ac43c7/attachment.pgp>