Bug#285580: Manpage problems
Package: obexftp Version: 0.10.6-1 Severity: normal Hello, Thanks for packaging obexftp! There is a problem with the manpage: at the beginning of OPTIONS, it says: The ordering of options is important. Every command will use the most recent device set. Every file without command switch will apply to the command given most recent. See EXAMPLES however, there is no EXAMPLES section. Actually, some examples would be nice, especially showing how to connect with the various means (IrDA, BT, custom transport; also, I thought that you needed to always specify -t when using IrDA, but obexftp complains). Ciao, Enrico -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages obexftp depends on: ii libbluetooth1 2.11-1Library to use the BlueZ Linux Blu ii libc6 2.3.2.ds1-19 GNU C Library: Shared libraries an ii libopenobex-1.0-0 1:1.0.0-rel-3 OBEX protocol library -- no debconf information signature.asc Description: Digital signature
Bug#285581: Cannot connect to a Siemens S55
Package: obexftp Version: 0.10.6-1 Severity: normal Hello, I changed laptop and I can't connect to my Siemens S55 anymore. gsmpb works using /dev/ircomm0, so the IrDA hardware seems to work. Here are the results using version 0.10.6-1: viaza:~# obexftp -i -x No custom transport Connecting...failed: connect Still trying to connect Connecting...failed: connect Still trying to connect Connecting...failed: connect Still trying to connect viaza:~# obexftp -t /dev/ircomm0 -x Do you really want to use IrDA via ttys? Custom transport set to 'Siemens/Ericsson' Connecting...failed: FBS UUID Still trying to connect Connecting...failed: connect Still trying to connect Connecting...failed: connect Still trying to connect Here are the results using version 0.10.3+4rc3-2: viaza:~# obexftp -i -x No custom transport Connecting...failed: connect Still trying to connect Connecting...failed: connect Still trying to connect Connecting...failed: connect Still trying to connect viaza:~# obexftp -t /dev/ircomm0 -x Custom transport set to 'Siemens/Ericsson' Connecting...failed: S45 UUID failed: FBS UUID Still trying to connect Connecting...failed: connect Still trying to connect Connecting...failed: connect Still trying to connect With gsmpb, however, it works: viaza:~# gsmpb -s /dev/ircomm0 -c -d - -pLD |x| |xx|x |xxx|xx |xxx|x |xxx|x |xx|x |xx|x ||x |xxx|x |x|x I don't know where to look at, but I rest at your disposal. Ciao, Enrico -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages obexftp depends on: ii libbluetooth1 2.11-1Library to use the BlueZ Linux Blu ii libc6 2.3.2.ds1-19 GNU C Library: Shared libraries an ii libopenobex-1.0-0 1:1.0.0-rel-3 OBEX protocol library -- no debconf information
Bug#285597: cook: FTBFS (amd64/gcc-4.0): static declaration of 'limit' follows non-static declaration
Package: cook Severity: normal Tags: patch When building 'cook' on amd64 with gcc-4.0, I get the following error: gcc -Ifile_check -Icommon -g -O2 -c \ file_check/file_check.c file_check/file_check.c:31: error: static declaration of 'limit' follows non-static declaration file_check/file_check.h:29: error: previous declaration of 'limit' was here make[1]: *** [file_check/file_check.o] Error 1 make[1]: Leaving directory `/cook-2.23' make: *** [build-stamp] Error 2 With the attached patch 'cook' can be compiled on amd64 using gcc-4.0. Regards Andreas Jochens diff -urN ../tmp-orig/cook-2.23/file_check/file_check.c ./file_check/file_check.c --- ../tmp-orig/cook-2.23/file_check/file_check.c 2003-05-01 01:56:20.0 +0200 +++ ./file_check/file_check.c 2004-12-14 11:32:57.730866296 +0100 @@ -28,7 +28,7 @@ #include intwarning; -static int limit; +intlimit; static int number_of_blank_lines; static int number_of_errors; static int line_number;
Processed: Adjusting Tag
Processing commands for [EMAIL PROTECTED]: > tags 238136 + upstream patch Bug#238136: efax problem (and fix) for sending fax notices There were no tags set. Tags added: upstream, patch > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#285648: Efax can send pdf as well
Package: efax Version: 0.9a-15 Severity: wishlist Tags: patch upstream Since efax uses ghostscript to handle postscript, and ghostscript can do pdf as well, it just has to use it. Trivial patch below. --- fax.fixed 2003-08-15 17:04:47.0 +0200 +++ fax.pdffix 2004-04-06 17:35:55.0 +0200 @@ -770,8 +770,8 @@ read x <$1 case $x in - %!*|?%!*) - echo "$1 is postscript..." + %!*|?%!*|%PDF*) + echo "$1 is postscript or pdf ..." # GS can't deal with long paths so we 'cd' DIRNAME=`dirname $1` ; BASENAME=`basename $1` ( cd $DIRNAME ; \ signature.asc Description: Digital signature
Bug#102921: It works for true, believe me
It's christmas and you want to make her happy in bed! And you need the right stuff... But why give out so many bucks for that? Try our damn good stuff and compare with other sites' price: http://rvxdbs182.dbzwishdfef.com/ Casandra
