Processing commands for [email protected]:

> #
> # bts-link upstream status pull for source package epiphany-browser
> # 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 #476955 (http://bugs.debian.org/476955)
> # Bug title: extensions API changed but the directory to look for them is the 
> same
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=588362
> #  * remote status changed: UNCONFIRMED -> RESOLVED
> #  * remote resolution changed: (?) -> OBSOLETE
> #  * closed upstream
> tags 476955 + fixed-upstream
Bug #476955 [epiphany-browser] extensions API changed but the directory to look 
for them is the same
Added tag(s) fixed-upstream.
> usertags 476955 - status-UNCONFIRMED
Usertags were: status-UNCONFIRMED.
Usertags are now: .
> usertags 476955 + status-RESOLVED resolution-OBSOLETE
There were no usertags set.
Usertags are now: status-RESOLVED resolution-OBSOLETE.
> # remote status report for #560310 (http://bugs.debian.org/560310)
> # Bug title: epiphany-extensions: Certificate extension doesn't work with 
> webkit-based Epiphany
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=618429
> forwarded 560310 https://bugzilla.gnome.org/show_bug.cgi?id=594856, 
> merged-upstream: http://bugzilla.gnome.org/show_bug.cgi?id=618429
Bug #560310 [epiphany-extensions] epiphany-extensions: Certificate extension 
doesn't work with webkit-based Epiphany
Changed Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=594856, merged-upstream: 
http://bugzilla.gnome.org/show_bug.cgi?id=618429' from 
'https://bugzilla.gnome.org/show_bug.cgi?id=594856'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
476955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476955
560310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560310
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