News Group Issues within Pine?

News Group Issues within Pine?

[Hart Larry]

Well, since at least 1997 I am still grabbing binaries from Pine, but now I 
must pipe raw messages through uudeview -    because of the yenc encoding.
Anyway, here on Shellworld, since we don't have news, I grab via nntp from 
Giganews.  All seems to go well until either I change news-groups during the 
same Pine session, or mysteriously while I am grabbing binaries.  All of a 
sudden, I see an error message, "no state found for news group 
alt.binaries.remixes.mp3, reading as new"  Once that happens, all the rest of 
my .newsrc file is hidden away, and I only at most have that 1 group active.
Now that Giganews is up to 700 days binary retention, many binary groups are 
way too large for Pine to read, or even after you open a larger group, 
sometimes, says, "problem detected, abort trap, trying to save debug"
On Shellworld I can still work on groups through trn  but on my local machine 
trn will not compile in FC9
Sure replacing an older .newsrc file temporarily restores these groups, but 
obviously I need to read or catchup.  However, this no state found problem is 
becoming worse.  Can some1 please suggest why this is happening or a fix.
I've tried setting an nntp range in Pine, but 30thousand is as high as it will 
go, but you only see the last 30000 postings.
Thanks so much in advance
Hart

Re: News Group Issues within Pine?

[Geoff Shang]

Hi,

Which version of Pine are you using?

I saw someone discussing AlPine's limit of 1 million messages, but this is 
a lot higher than 30 thousand.

Geoff.

Re: News Group Issues within Pine?

[Hart Larry]

Hi Jeff:  Here on Shellworld, its 4.64, which was last version of pine, but 
even on my hard-drive, its Alpine 2.00 (LFD 1167 2008-08-23) built Wed Aug 27 
14:30:56 EDT 2008 on x86-1.fedora.phx.redhat.com
Really unless the binary is within last 2days or so, I cannot grab much older 
with that nntp range set.  If I make that value 0  then I see everything or at 
least since my last visit.
Hart

Re: News Group Issues within Pine?

[Jude DaShiell]

shellworld.net has had alpine up and running for at least the last year.
  The alpine program is the one to file bugs against since only those with 
uwashington.edu accounts can file bugs against pine and get support.  The 
working arrangement is that pine is experimental software and intended as 
such.  Stuff that works in pine gets ported over to alpine and things that 
break in pine either get replaced or removed.  When something is broken in 
both packages, then file the bug against alpine and it'll likely get 
attention whether you have a uwashington.edu account or not.  This is the 
same strategy Okidata followed when manufacturing printers.  They used 
Japan as a test bed to make their mistakes and correct those mistakes and 
sold the models with the corrections to the rest of the world. On Sun, 19 
Sep 2010, Hart Larry wrote:

> Hi Jeff:  Here on Shellworld, its 4.64, which was last version of pine, but 
> even on my hard-drive, its Alpine 2.00 (LFD 1167 2008-08-23) built Wed Aug 27 
> 14:30:56 EDT 2008 on x86-1.fedora.phx.redhat.com
> Really unless the binary is within last 2days or so, I cannot grab much older 
> with that nntp range set.  If I make that value 0  then I see everything or 
> at least since my last visit.
> Hart
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>

Re: News Group Issues within Pine?

[Geoff Shang]

On Mon, 20 Sep 2010, Jude DaShiell wrote:

> The alpine program is the one to file bugs against since only those with 
> uwashington.edu accounts can file bugs against pine and get support.

Not sure when this was the case, but it's not the case any longer.  UW is 
not developing Pine in any form, ALPine or any other version.  They have 
decided to cease development of their own client.

I've also heard (without confirmation) that this decision and the 
resultant purchasing of commercial licenses for a replacement nearly sent 
them broke.

It is the consensus of the alpine-info mailing list that the 
re-alpine.SourceForge.net project is the only place that's showing any 
signs of life.

Geoff.