Processing commands for [email protected]: > # > # bts-link upstream status pull for source package torbrowser-launcher > # 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 #783922 (http://bugs.debian.org/783922) > # Bug title: Newest TBB does not start with provided AppArmor profile in > enforce mode > # * https://github.com/micahflee/torbrowser-launcher/issues/177 > # * remote status changed: open -> closed > # * closed upstream > tags 783922 + fixed-upstream Bug #783922 [torbrowser-launcher] Newest TBB does not start with provided AppArmor profile in enforce mode Added tag(s) fixed-upstream. > usertags 783922 - status-open Usertags were: status-open. Usertags are now: . > usertags 783922 + status-closed There were no usertags set. Usertags are now: status-closed. > # remote status report for #784041 (http://bugs.debian.org/784041) > # Bug title: exceptions.OSError: [Errno 2] No such file or directory > # * https://github.com/micahflee/torbrowser-launcher/issues/176 > # * remote status changed: (?) -> closed > # * closed upstream > tags 784041 + fixed-upstream Bug #784041 [torbrowser-launcher] exceptions.OSError: [Errno 2] No such file or directory Added tag(s) fixed-upstream. > usertags 784041 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here.
Please contact me if you need assistance. -- 783922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783922 784041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784041 Debian Bug Tracking System Contact [email protected] with problems -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
