Processing commands for [email protected]:

> #
> # bts-link upstream status pull for source package samba
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
> #
> user [email protected]
Setting user to [email protected] (was 
[email protected]).
> # remote status report for #574468 (http://bugs.debian.org/574468)
> #  * https://bugzilla.samba.org/show_bug.cgi?id=7684
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> forwarded 574468 https://bugzilla.samba.org/show_bug.cgi?id=7265, 
> merged-upstream: https://bugzilla.samba.org/show_bug.cgi?id=7684
Bug #574468 [winbind] samba: pam_winbind leaks file descriptors
Bug #606350 [winbind] Possible file descriptor leak in pam_winbind
Changed Bug forwarded-to-address to 
'https://bugzilla.samba.org/show_bug.cgi?id=7265, merged-upstream: 
https://bugzilla.samba.org/show_bug.cgi?id=7684' from 
'https://bugzilla.samba.org/show_bug.cgi?id=7265'
Changed Bug forwarded-to-address to 
'https://bugzilla.samba.org/show_bug.cgi?id=7265, merged-upstream: 
https://bugzilla.samba.org/show_bug.cgi?id=7684' from 
'https://bugzilla.samba.org/show_bug.cgi?id=7265'
> tags 574468 + fixed-upstream
Bug #574468 [winbind] samba: pam_winbind leaks file descriptors
Bug #606350 [winbind] Possible file descriptor leak in pam_winbind
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 574468 - status-NEW
Bug#574468: samba: pam_winbind leaks file descriptors
Usertags were: status-NEW.
Usertags are now: .
> usertags 574468 + status-RESOLVED resolution-FIXED
Bug#574468: samba: pam_winbind leaks file descriptors
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
574468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574468
Debian Bug Tracking System
Contact [email protected] with problems


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to