Processed: [bts-link] source package hylafax

Debian Bug Tracking System owner at bugs.debian.org
Mon Feb 19 02:09:03 CET 2007


Processing commands for control at bugs.debian.org:

> #
> # bts-link upstream status pull for source package hylafax
> # 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 #180072
> #  * http://bugs.hylafax.org/show_bug.cgi?id=385
> #  * remote status changed: (?) -> NEW
> usertags 180072 + status-NEW
Bug#180072: hylafax-client: hex in strings doesn't work
Usertags were: status-NEW.
Usertags are now: status-NEW.
> # remote status report for #182098
> #  * http://bugs.hylafax.org/show_bug.cgi?id=465
> #  * remote status changed: (?) -> NEW
> usertags 182098 + status-NEW
Bug#182098: hylafax-server: please implement -?, --help, dont just accept invalid args
Usertags were: status-NEW.
Usertags are now: status-NEW.
> # remote status report for #373148
> #  * http://bugs.hylafax.org/show_bug.cgi?id=791
> #  * remote status changed: (?) -> NEW
> usertags 373148 + status-NEW
Bug#373148: hylafax-server: Failed to properly detect high-speed data carrier
Usertags were: status-NEW.
Usertags are now: status-NEW.
> # remote status report for #406395
> #  * http://bugs.hylafax.org/show_bug.cgi?id=842
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> INVALID
> usertags 406395 + status-RESOLVED resolution-INVALID
Bug#406395: hylafax-server: bin/faxrcvd, bin/notify won't be able to send email
Usertags were: resolution-INVALID status-RESOLVED.
Usertags are now: resolution-INVALID status-RESOLVED.
> # remote status report for #409417
> #  * http://bugs.hylafax.org/show_bug.cgi?id=840
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> usertags 409417 + status-RESOLVED resolution-FIXED
Bug#409417: hylafax-server: [PATCH] faxinfo(1) should not return 0 on broken faxfile
Usertags were: resolution-FIXED status-RESOLVED.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #409532
> #  * http://bugs.hylafax.org/show_bug.cgi?id=841
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> WORKSFORME
> usertags 409532 + status-RESOLVED resolution-WORKSFORME
Bug#409532: hylafax-server: notifications lack retry time
Usertags were: resolution-WORKSFORME status-RESOLVED.
Usertags are now: resolution-WORKSFORME status-RESOLVED.
> thanks
Stopping processing here.

Please contact me if you need assistance.

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




More information about the Bts-link-devel mailing list