Processed: [bts-link] source package prey

[Debian Bug Tracking System]

Processing commands for control at bugs.debian.org:

> #
> # bts-link upstream status pull for source package prey
> # 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 #668787 (http://bugs.debian.org/668787)
> # Bug title: [prey] Lock module prevents Prey from sending reports.
> #  * https://github.com/prey/prey-bash-client/issues/282
> #  * remote status changed: (?) -> open
> usertags 668787 + status-open
Bug#668787: [prey] Lock module prevents Prey from sending reports.
There were no usertags set.
Usertags are now: status-open.
> # remote status report for #668790 (http://bugs.debian.org/668790)
> # Bug title: [prey] Screenshot is not taken even if it's specified to be taken in Session module config.
> #  * https://github.com/prey/prey-bash-client/issues/283
> #  * remote status changed: (?) -> open
> usertags 668790 + status-open
Bug#668790: [prey] Screenshot is not taken even if it's specified to be taken in Session module config.
There were no usertags set.
Usertags are now: status-open.
> # remote status report for #668796 (http://bugs.debian.org/668796)
> # Bug title: [prey] Alert module doesn't say the message when prey.sh is run by cron.
> #  * https://github.com/prey/prey-bash-client/issues/284
> #  * remote status changed: (?) -> open
> usertags 668796 + status-open
Bug#668796: [prey] Alert module doesn't say the message when prey.sh is run by cron.
There were no usertags set.
Usertags are now: status-open.
> thanks
Stopping processing here.

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