[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#605911: marked as done ((future) unblock: network-manager/0.8.1-6)



Your message dated Mon, 06 Dec 2010 23:54:01 +0100
with message-id <4CFD6989.4010208@dogguy.org>
and subject line Re: Bug#605911: (future) unblock: network-manager/0.8.1-6
has caused the Debian Bug report #605911,
regarding (future) unblock: network-manager/0.8.1-6
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
605911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605911
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: freeze-exception

I just uploaded network-manager 0.8.1-6 to DELAYED/1 so the current package has
a chance to migrate to testing.

Hopefully this is the last upload for network-manager.

It fixes two bugs in the ifupdown plugin, especially #569215 has several
duplicates, so it would be nice to see those fixes in squeeze.

Changelog:

network-manager (0.8.1-6) unstable; urgency=low

  * debian/patches/40-umanaged-interfaces.patch
    - For devices to be marked unmanaged, do not require a valid connection
      configuration. (Closes: #569215)
  * debian/patches/50-bridge-interfaces.patch
    - Parse bridge configurations in /etc/network/interfaces and add
      interfaces defined via bridge_ports to well_known_interfaces. This
      allows to mark those interfaces as unmanaged if managed=false.
      The "all" keyword and regexes are not supported and simply skipped.
      (Closes: #530335)

 -- Michael Biebl <biebl@debian.org>  Sat, 04 Dec 2010 17:11:13 +0100

Debdiff is attached.


Thanks,
Michael

unblock network-manager/0.8.1-6

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
On 12/06/2010 11:43 PM, Michael Biebl wrote:
> Am 06.12.2010 23:00, schrieb Mehdi Dogguy:
>> On 12/04/2010 05:26 PM, Michael Biebl wrote:
>>>
>>> network-manager (0.8.1-6) unstable; urgency=low
>>>
>>>   * debian/patches/40-umanaged-interfaces.patch
>>>     - For devices to be marked unmanaged, do not require a valid connection
>>>       configuration. (Closes: #569215)
> 
> An example here is:
> 
> iface wlan0 inet wlan0
> 	wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
> 
> This is configuration that is incomplete/not understood by
> network-manager. We still want to mark the interface as unmanaged though
> if managed=false.
> 
> 
>>>   * debian/patches/50-bridge-interfaces.patch
>>>     - Parse bridge configurations in /etc/network/interfaces and add
>>>       interfaces defined via bridge_ports to well_known_interfaces. This
>>>       allows to mark those interfaces as unmanaged if managed=false.
>>>       The "all" keyword and regexes are not supported and simply skipped.
>>>       (Closes: #530335)
>>>
>>
>> I'm sure that I misunderstood something but I'll ask question anyway :)
>>
>> I read the following lines in the diff:
>>
>> + /* Skip crazy stuff like regex or all */
>> + if (!strcmp ("all", token)) {
>> +         continue;
>> + }
>> + /* Small SM to skip everything inside regex */
>> + if (!strcmp ("regex", token)) {
>> +         state++;
>> +         continue;
>> + }
>>
>> It doesn't look like "regex" is skipped here (not like "all" at least).
> 
> If we find "regex" ,the start of a regular expression, we increment the
> counter, and skip the token via continue. If we find "noregex", the end
> of the regular expression, we decrement the counter and also skip the
> token via continue.
> As long as we are inside a regular expression (counter > 0), we skip any
> tokens.
> 

Gah. Stupid me. Unblocked.

Regards,

-- 
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/


--- End Message ---

Reply to: