Am Sonntag 18 Oktober 2009 11:37:18 schrieb Alexander Galanin: > Package: obexftp > Version: 0.23-1 > Severity: important > > obexftp should return non-zero exit code if GET operation fails > > Steps to reproduce the problem: > 1. Normal operation: > > $ obexftp -b 00:1E:3B:2C:FB:B3 -g telecom/pb.vcf > Browsing 00:1E:3B:2C:FB:B3 ... > Connecting..\done > Tried to connect for 77ms > Receiving "telecom/pb.vcf"... Sending ""...|done > -done > Disconnecting..\done > > 2. Check exit code. Should be zero > > $ echo $? > 0 > > 3. Failure: > $ obexftp -b 00:1E:3B:2C:FB:B3 -g telecom/nonexistent ; echo $? > Browsing 00:1E:3B:2C:FB:B3 ... > Connecting..\done > Tried to connect for 76ms > Receiving "telecom/nonexistent"... Sending ""...|done > /failed: telecom/nonexistent > Disconnecting..-done > > 2. Check exit code. Should be non-zero, but zero returned > > $ echo $? > 0
Due to bug #549623, upstream was already asked to rework the return codes internally. This needs time and was not completed, yet. In obexftp-0.22 and earlier, obexftp always returned 0. So this bug, contrary to bug #549623, is not a regression. Additionally, it is nowhere mentioned that it will return a non-zero code, so you should not rely on it. HS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
