Processed: [bts-link] source package evolution

[Debian Bug Tracking System]

Processing commands for control at bugs.debian.org:

> #
> # bts-link upstream status pull for source package evolution
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
> #
> user bts-link-upstream at lists.alioth.debian.org
Setting user to bts-link-upstream at lists.alioth.debian.org (was bts-link-devel at lists.alioth.debian.org).
> # remote status report for #213283 (http://bugs.debian.org/213283)
> # Bug title: evolution: wrong ldap handling of free/budy url and calendar
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=231967
> #  * remote status changed: NEW -> NEEDINFO
> usertags 213283 - status-NEW
Bug#213283: evolution: wrong ldap handling of free/budy url and calendar
Usertags were: status-NEW.
Usertags are now: .
> usertags 213283 + status-NEEDINFO
Bug#213283: evolution: wrong ldap handling of free/budy url and calendar
There were no usertags set.
Usertags are now: status-NEEDINFO.
> # remote status report for #386986 (http://bugs.debian.org/386986)
> # Bug title: evolution: Evolution should not allow more than one instance - or start a second instance properly
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=261169
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> OBSOLETE
> #  * closed upstream
> tags 386986 + fixed-upstream
Bug #386986 [evolution] evolution: Evolution should not allow more than one instance - or start a second instance properly
Added tag(s) fixed-upstream.
> usertags 386986 - status-NEW
Bug#386986: evolution: Evolution should not allow more than one instance - or start a second instance properly
Usertags were: status-NEW.
Usertags are now: .
> usertags 386986 + status-RESOLVED resolution-OBSOLETE
Bug#386986: evolution: Evolution should not allow more than one instance - or start a second instance properly
There were no usertags set.
Usertags are now: status-RESOLVED resolution-OBSOLETE.
> # remote status report for #421672 (http://bugs.debian.org/421672)
> # Bug title: Content-Type should handle case insensitive strings
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=523271
> #  * remote status changed: UNCONFIRMED -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> forwarded 421672 http://bugzilla.gnome.org/show_bug.cgi?id=446146, merged-upstream: http://bugzilla.gnome.org/show_bug.cgi?id=523271
Bug #421672 [evolution] Content-Type should handle case insensitive strings
Changed Bug forwarded-to-address to 'http://bugzilla.gnome.org/show_bug.cgi?id=446146, merged-upstream: http://bugzilla.gnome.org/show_bug.cgi?id=523271' from 'http://bugzilla.gnome.org/show_bug.cgi?id=446146'
> tags 421672 + fixed-upstream
Bug #421672 [evolution] Content-Type should handle case insensitive strings
Added tag(s) fixed-upstream.
> usertags 421672 - status-UNCONFIRMED
Bug#421672: Content-Type should handle case insensitive strings
Usertags were: status-UNCONFIRMED.
Usertags are now: .
> usertags 421672 + status-RESOLVED resolution-FIXED
Bug#421672: Content-Type should handle case insensitive strings
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
421672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421672
386986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386986
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems