Your message dated Thu, 20 Jan 2005 22:06:53 -0600
with message-id <[EMAIL PROTECTED]>
and subject line txt2pdbdoc generates (somewhat) corrupt/invalid pdb files
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--------------------------------------
Received: (at submit) by bugs.debian.org; 10 Nov 2001 02:33:06 +0000
>From [EMAIL PROTECTED] Fri Nov 09 20:33:06 2001
Return-path: <[EMAIL PROTECTED]>
Received: from cx228877-b.btnrug1.la.home.com (singularity.resonant.org) 
[24.13.198.99] (mail)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 162NxC-0007gY-00; Fri, 09 Nov 2001 20:33:06 -0600
Received: from zed by singularity.resonant.org with local (Exim 3.32 #1 
(Debian))
        id 162Nx5-0002EN-00; Fri, 09 Nov 2001 20:32:59 -0600
From: Zed Pobre <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: txt2pdbdoc generates (somewhat) corrupt/invalid pdb files
X-Reportbug-Version: 1.35
X-Mailer: reportbug 1.35
Date: Fri, 09 Nov 2001 20:32:59 -0600
Message-Id: <[EMAIL PROTECTED]>
Sender: Zed Pobre <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]

Package: txt2pdbdoc
Version: 1.4.1-2
Severity: important

I own a Handera 330, which has slots for CompactFlash and SD cards,
and a MicroTech CameraMate USB CF/SD reader, and use exclusively CF
cards.  This is a bug that only shows up if you use txt2pdbdoc on a
document and then copy it directly to the CF card for later use --
apparantly the act of hotsyncing it repairs the damaged header.  If
the damage is not repaired by the system, however, the net result when
the document is later read can be anything from strange to very
unpleasant, depending on the reader.  One reader stripped out the
first two characters (or if the first character was a newline,
replaced it with a space) and subsequently wouldn't display those two
characters next to each other later in the document.  Other readers
crashed, causing a complete PDA reset.  I'm tempted to mark this bug
grave, considering that can cause data loss, but since I think the act
of transferring data via a CF card directly is fairly uncommon, I'm
leaving it as important for now.

By syncing a document to the PDA, transferring it via PDA software to
the CF card, and then copying it from the CF back to the hard drive, I
was able to make a comparison between the damaged and repaired file.
The difference appears to be only in the header, the first few hundred
bytes or so, and the corrected file was 324 bytes longer than the
original.

I can make before-and-after documents available to you upon request if
you need them.

I hope you can fix this; txt2pdbdoc is currently the only PalmDoc
generator in unstable that I can get to work at all.

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux singularity 2.4.13-xfs #3 Tue Oct 30 21:45:34 CST 2001 i686
Locale: LANG=en_US, LC_CTYPE=en_US

Versions of packages txt2pdbdoc depends on:
ii  libc6                         2.2.4-5    GNU C Library: Shared libraries an
ii  perl                          5.6.1-5    Larry Wall's Practical Extraction 


---------------------------------------
Received: (at 118930-done) by bugs.debian.org; 21 Jan 2005 04:06:56 +0000
>From [EMAIL PROTECTED] Thu Jan 20 20:06:55 2005
Return-path: <[EMAIL PROTECTED]>
Received: from wsip-68-224-223-13.br.no.cox.net (resonant.org) [68.224.223.13] 
(postfix)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1Crq4V-00053b-00; Thu, 20 Jan 2005 20:06:55 -0800
Received: by resonant.org (Postfix, from userid 1000)
        id E702E26AB88; Thu, 20 Jan 2005 22:06:53 -0600 (CST)
Date: Thu, 20 Jan 2005 22:06:53 -0600
From: Zed Pobre <[EMAIL PROTECTED]>
To: Erik Schanze <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: txt2pdbdoc generates (somewhat) corrupt/invalid pdb files
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL 
PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
        protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
X-No-Archive: Yes
X-GPG-Fingerprint: FF 75 8D 70 57 8D A4 7D  3A DE 6D 2F 25 C3 E6 E7
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 


--4Ckj6UjgE2iN1+kY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jan 08, 2005 at 08:59:20PM +0100, Erik Schanze wrote:
>=20
> Have you still found some time to test the bug again?
> Could you please provide some files before and after transmission
> on Palm via CF card for inspection?=20
>=20
> Unfortunatelly, no other user had reported similar behavior during last y=
ears.
> Are you sure, that this misbehavior is not a defect of your devices?

    My most recent tests, copying to a Memory Stick and then reading
=66rom either Weasel Reader or iSilo on a Sony NX80V, have caused no
crashes.  This may have been a Handera-specific bug, or a bug specific
to the original AportisDoc (no longer available) or an earlier version
of WeaselReader.

    Closing the bug.  Thanks for your patience.

--=20
Zed Pobre <[EMAIL PROTECTED]> a.k.a. Zed Pobre <[EMAIL PROTECTED]>
PGP key and fingerprint available on finger; encrypted mail welcomed.


--4Ckj6UjgE2iN1+kY
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5

iQEVAwUBQfB/3R0207zoJUw5AQHIcwf7BAL7dy2V7PTq4ZrlwhQ40/GmpRKzbWBe
tJ6t7ehYN8uVYpSNo34q8Cb7/7e/BSm1RnxW/+v68bRAdqkJp3PH8HspqWfgSpLr
70QBNPzMpegFFDzm/IK+5Ukn1W894M7NCLWgJF56pL5lrtm5XKYsKd5M2ZX/W05c
/L/IMzZa4dm4zjFR6oUdL1m/D8IGuHqHkHfDpsbhdRntkAW4HyOSJjsIqtvo/z1z
vowUkkBSxo6uDFFC9ORKUC3TJPajiBODlQ8ADWaJqVgPV1My87VPHW+ytntQIbXn
smG9rCFIe8soQkXaZjccDBsmhlj2J7cMJFnweIMU/Y40KA61il6k5w==
=EMVd
-----END PGP SIGNATURE-----

--4Ckj6UjgE2iN1+kY--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to