Bug#363002: xbuffy: Does not report any useful information

2006-04-21 Thread Bernhard R. Link
package xbuffy
tags 363002 pending
thanks

* Frédéric Brière [EMAIL PROTECTED] [060421 00:25]:
 On Mon, Apr 17, 2006 at 09:28:36AM +0200, Bernhard R. Link wrote:
   Just since the upgrade from a recent version in Unstable, xbuffy
   reports all mailboxes to have 0 messages (with option -orig that's
   no messages in box, without -orig that's no new messages).
 
 Same here.  3.3.bl.3-25 works fine, but 3.3.bl.3.dfsg-1 does no good.
 
 I'm attaching a trimmed-down message that still exhibits this behavior.
 (I didn't dare trim it down further, in case the X header parser subs
 were too picky.)

Thanks. With that I found what I overlooked.

A version being able to parse this mbox will hit the archives soon.

Hochachtungsvoll,
Bernhard R. Link


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



Bug#363002: xbuffy: Does not report any useful information

2006-04-20 Thread Frédéric Brière
On Mon, Apr 17, 2006 at 09:28:36AM +0200, Bernhard R. Link wrote:
  Just since the upgrade from a recent version in Unstable, xbuffy
  reports all mailboxes to have 0 messages (with option -orig that's
  no messages in box, without -orig that's no new messages).

Same here.  3.3.bl.3-25 works fine, but 3.3.bl.3.dfsg-1 does no good.

I'm attaching a trimmed-down message that still exhibits this behavior.
(I didn't dare trim it down further, in case the X header parser subs
were too picky.)

 That's strange.

Well, not given the size of the diff between 3 and 3.dfsg, it ain't. :)


-- 
 Frédéric Brière*[EMAIL PROTECTED]

 =  [EMAIL PROTECTED] IS NO MORE:  http://www.abacomsucks.com  =
From [EMAIL PROTECTED]  Thu Apr 20 17:17:37 2006
Date: Thu, 20 Apr 2006 17:17:37 -0400
To: Frederic Briere [EMAIL PROTECTED]
Subject: foo
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1
From: [EMAIL PROTECTED] (Frederic Briere)
Content-Length: 141
Lines: 6

foo

-- 
 Frédéric Brière*[EMAIL PROTECTED]

 =  [EMAIL PROTECTED] IS NO MORE:  http://www.abacomsucks.com  =



Bug#363002: xbuffy: Does not report any useful information

2006-04-17 Thread Bernhard R. Link
* Ben Pearre [EMAIL PROTECTED] [060417 04:57]:
 Just since the upgrade from a recent version in Unstable, xbuffy
 reports all mailboxes to have 0 messages (with option -orig that's
 no messages in box, without -orig that's no new messages).
 
 [...]
 I'm using procmail and mutt on local files (ie. berkeley mbox).  No
 Status header field on unread messages, Status: RO is added to
 read messages.

That's strange. What Mailserver do you use?
Perhaps it is best to send me the example mailbox, as I can debug the
problem then, as I'm currently a bit unsure what could cause this.

Hochachtungsvoll,
Bernhard R. Link


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



Bug#363002: xbuffy: Does not report any useful information

2006-04-16 Thread Ben Pearre
Package: xbuffy
Version: 3.3.bl.3.dfsg-1
Severity: important


Just since the upgrade from a recent version in Unstable, xbuffy
reports all mailboxes to have 0 messages (with option -orig that's
no messages in box, without -orig that's no new messages).

Age: not sure about this; /usr/share/doc/xbuffy/changelog.Debian does
not list anything suspicious recently; previous (working) version may
have been up to a couple of months old, also from Unstable, but I
don't have a version number.  Where can I get that?

xbuffy is finding and opening the mailboxes correctly: if I enter an
invalid filename it reports -1 messages.  Running under strace shows
the files being successfully found, stat64'd, opened, read, ...

I'm using procmail and mutt on local files (ie. berkeley mbox).  No
Status header field on unread messages, Status: RO is added to
read messages.

I'm actually using zsh; not sure why reportbug thinks I'm using bash.

Here's some of ~/.xbuffyrc, although I've tried permutations, simple
cases (eg. first line only), etc.  I'll send a sample mbox file that
xbuffy doesn't read if anyone requests it, but that's big...

box ~/Mail/Inbox
box ~/Mail/ciy
box ~/Mail/cu
headertime 0
nobeep
box ~/Mail/dave
box ~/Mail/family
box ~/Mail/grade/admin
title grade/admin

I didn't know what severity to give this bug: xbuffy is completely
unusable on my system since it reports no useful information at all
(severity 2:Grave), but I have not tested on other systems.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.2
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages xbuffy depends on:
ii  libc6 2.3.6-6GNU C Library: Shared libraries
ii  libx11-6  2:1.0.0-6  X11 client-side library
ii  libxaw7   1:1.0.1-4  X11 Athena Widget library
ii  libxt61:1.0.0-3  X11 toolkit intrinsics library

xbuffy recommends no packages.

-- debconf information excluded


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