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

Processed: [bts-link] source package kdepim



Processing commands for control@bugs.debian.org:

> #
> # bts-link upstream status pull for source package kdepim
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
> #
> user bts-link-upstream@lists.alioth.debian.org
Setting user to bts-link-upstream@lists.alioth.debian.org (was bts-link-devel@lists.alioth.debian.org).
> # remote status report for #172610
> #  * http://bugs.kde.org/show_bug.cgi?id=59069
> #  * remote status changed: UNCONFIRMED -> NEW
> usertags 172610 - status-UNCONFIRMED
Bug#172610: KMail and large e-mails
Usertags were: status-UNCONFIRMED.
Usertags are now: .
> usertags 172610 + status-NEW
Bug#172610: KMail and large e-mails
There were no usertags set.
Usertags are now: status-NEW.
> # remote status report for #347478
> #  * http://bugs.kde.org/show_bug.cgi?id=133159
> #  * remote status changed: UNCONFIRMED -> NEW
> usertags 347478 - status-UNCONFIRMED
Bug#347478: [Fwd: Log for successful build of kdepim_4:3.5.0-4 (dist=unstable)]
Usertags were: status-UNCONFIRMED.
Usertags are now: .
> usertags 347478 + status-NEW
Bug#347478: [Fwd: Log for successful build of kdepim_4:3.5.0-4 (dist=unstable)]
There were no usertags set.
Usertags are now: status-NEW.
> # remote status report for #356142
> #  * http://bugs.kde.org/show_bug.cgi?id=125115
> #  * remote status changed: UNCONFIRMED -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 356142 + fixed-upstream
Bug#356142: knode: Fatal IO error: client killed
Tags were: upstream moreinfo
Tags added: fixed-upstream

> usertags 356142 - status-UNCONFIRMED
Bug#356142: knode: Fatal IO error: client killed
Usertags were: status-UNCONFIRMED.
Usertags are now: .
> usertags 356142 + status-RESOLVED resolution-FIXED
Bug#356142: knode: Fatal IO error: client killed
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #365689
> #  * http://bugs.kde.org/show_bug.cgi?id=126122
> #  * remote status changed: UNCONFIRMED -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 365689 + fixed-upstream
Bug#365689: korganizer: Crashes on add-event; unable to add new calendar events
There were no tags set.
Tags added: fixed-upstream

> usertags 365689 - status-UNCONFIRMED
Bug#365689: korganizer: Crashes on add-event; unable to add new calendar events
Usertags were: status-UNCONFIRMED.
Usertags are now: .
> usertags 365689 + status-RESOLVED resolution-FIXED
Bug#365689: korganizer: Crashes on add-event; unable to add new calendar events
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #384862
> #  * http://bugs.kde.org/show_bug.cgi?id=93199
> #  * remote status changed: UNCONFIRMED -> REOPENED
> forwarded 384862 http://bugs.kde.org/show_bug.cgi?id=107836, merged-upstream: http://bugs.kde.org/show_bug.cgi?id=93199
Bug#384862: kmail: asks for the password for 5 times even if I hit "cancel"
Forwarded-to-address changed from http://bugs.kde.org/show_bug.cgi?id=107836 to http://bugs.kde.org/show_bug.cgi?id=107836, merged-upstream: http://bugs.kde.org/show_bug.cgi?id=93199.

> usertags 384862 - status-UNCONFIRMED
Bug#384862: kmail: asks for the password for 5 times even if I hit "cancel"
Usertags were: status-UNCONFIRMED.
Usertags are now: .
> usertags 384862 + status-REOPENED
Bug#384862: kmail: asks for the password for 5 times even if I hit "cancel"
There were no usertags set.
Usertags are now: status-REOPENED.
> # remote status report for #394719
> #  * http://bugs.kde.org/show_bug.cgi?id=102681
> #  * remote status changed: (?) -> NEW
> usertags 394719 + status-NEW
Bug#394719: kmail: spacing problem for automatically added filter buttons
There were no usertags set.
Usertags are now: status-NEW.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



Reply to: