headers
Adam Funk | 2 Dec 2009 15:03
Favicon

can't re-compile leafnode after Ubuntu karmic upgrade

I recently upgraded from Ubuntu jaunty to karmic, and it occurred to
me that I ought to re-compile leafnode (version
leafnode-2.0.0.alpha20090908a.luascript) against the updated
libraries.  

The configure step [1] seems to work OK [2], but make fails [3] even
after doing make clean first.  I have the lua5.1 package (version
5.1.4-3) on the system, which configure seems to detect.  

I'd appreciate any suggestions (but it's not really urgent since the
old binaries are still running without any apparent problems).

Thanks,
Adam

[1]  my configure command

./configure   --prefix=/usr/local                \
      --sysconfdir=/etc/news/leafnode2   --mandir=/usr/local/man            \
      --localstatedir=/var               --enable-lua                       \
      --enable-runas-user=news           --enable-spooldir=/var/spool/news

[2]  last part of its output

=== configuration summary: (NONE is ok here and means the default) ===
prefix:      /usr/local
sysconfdir:  /etc/news/leafnode2
spooldir:    /var/spool/news
RUNAS_USER:  news
RUNAS_GROUP: 9
(Continue reading)

Permalink | Reply | 2 comments |
headers
Chris G | 2 Dec 2009 18:28

Does 'expire' really mean what it says?

At the top of my leafnode config file I have:-

    ## Unread articles will be deleted after this many days if
    ## you don't define special expire times. Mandatory.
    expire = 20

Does it really mean *unread* articles will be deleted after 20 days?
Or does it mean *all* articles will be deleted after 20 days?

--

-- 
Chris Green
Permalink | Reply | 7 comments |
headers
David Rosen | 2 Dec 2009 18:32
Picon

Re: Does 'expire' really mean what it says?

It does if you run texpire via cron.

On Wed, Dec 2, 2009 at 11:28 AM, Chris G <cl@...> wrote:

> At the top of my leafnode config file I have:-
>
>    ## Unread articles will be deleted after this many days if
>    ## you don't define special expire times. Mandatory.
>    expire = 20
>
> Does it really mean *unread* articles will be deleted after 20 days?
> Or does it mean *all* articles will be deleted after 20 days?
>
> --
> Chris Green
>
> --
> _______________________________________________
> leafnode-list mailing list
> leafnode-list@...
> https://www.dt.e-technik.uni-dortmund.de/mailman/listinfo/leafnode-list
> http://leafnode.sourceforge.net/
>

--

-- 
David
Permalink | Reply | 2 comments |
headers
Chris G | 2 Dec 2009 18:54

Re: Does 'expire' really mean what it says?

On Wed, Dec 02, 2009 at 11:32:55AM -0600, David Rosen wrote:
> On Wed, Dec 2, 2009 at 11:28 AM, Chris G <cl@...> wrote:
> 
> > At the top of my leafnode config file I have:-
> >
> >    ## Unread articles will be deleted after this many days if
> >    ## you don't define special expire times. Mandatory.
> >    expire = 20
> >
> > Does it really mean *unread* articles will be deleted after 20 days?
> > Or does it mean *all* articles will be deleted after 20 days?
> >
> It does if you run texpire via cron.
> 
It does what?  :-)

.... in fact the leafnode man page does explain things more fully,
texpire deletes articles 'expire' days after they were last read.

I was just confused by the default comment in the config file which
(sort of) suggests that only unread articles will be expired.

--

-- 
Chris Green
Permalink | Reply | 1 comment |
headers
David Rosen | 2 Dec 2009 18:58
Picon

Re: Does 'expire' really mean what it says?

Sry, answered your subject line :(

Was reading on my damn phone. POS Blackberry (just like the user to blame
the device, aint it?)

What version of leafnode BTW? (not that I think it matters but it could be
relevant, I use the 2.0 beta branch and from what I recall (I dont expire
much, I keep a BIG archive) it deletes everything older than the expired
date.

On Wed, Dec 2, 2009 at 11:54 AM, Chris G <cl@...> wrote:

> On Wed, Dec 02, 2009 at 11:32:55AM -0600, David Rosen wrote:
> > On Wed, Dec 2, 2009 at 11:28 AM, Chris G <cl@...> wrote:
> >
> > > At the top of my leafnode config file I have:-
> > >
> > >    ## Unread articles will be deleted after this many days if
> > >    ## you don't define special expire times. Mandatory.
> > >    expire = 20
> > >
> > > Does it really mean *unread* articles will be deleted after 20 days?
> > > Or does it mean *all* articles will be deleted after 20 days?
> > >
> > It does if you run texpire via cron.
> >
> It does what?  :-)
>
> .... in fact the leafnode man page does explain things more fully,
> texpire deletes articles 'expire' days after they were last read.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matthias Andree | 2 Dec 2009 19:20
Picon
Picon

Re: Does 'expire' really mean what it says?

Am 02.12.2009, 18:28 Uhr, schrieb Chris G <cl@...>:

> At the top of my leafnode config file I have:-
>
>     ## Unread articles will be deleted after this many days if
>     ## you don't define special expire times. Mandatory.
>     expire = 20
>
> Does it really mean *unread* articles will be deleted after 20 days?

Yes (assuming texpire installed as cron job, as Daniel remarked rightly),  
but leafnode-2 will retain context for threads that you read, i. e.  
articles of which you have read a followup will remain in the spool  
(unless you run texpire -a that is).

Zero maintenance means not filling up your disk if you leave everything  
alone, right? :)

> Or does it mean *all* articles will be deleted after 20 days?

leafnode-2: "20 days after any article in the thread was last read"
leafnode-1 in any setting, or leafnode-2 with texpire -a: "20 days after  
the article was last read" (if ever).

reading articles defers expiry unless you specify the -f option to  
fetchnews.

If someone wants to help leafnode, feel free to write this up for  
leafnode-2 and create a patch or a new section for texpire.8.in and/or  
leafnode.8.in. You will be credited in the NEWS file. :)
(Continue reading)

Permalink | Reply | 3 comments |
headers
Les Harris | 2 Dec 2009 19:35
X-Face
Picon
Gravatar

Re: can't re-compile leafnode after Ubuntu karmic upgrade

Adam Funk <a24061@...> writes:

> The configure step [1] seems to work OK [2], but make fails [3] even
> after doing make clean first.  I have the lua5.1 package (version
> 5.1.4-3) on the system, which configure seems to detect.  

This is a known issue.  MA posted a small patch here:

http://article.gmane.org/gmane.network.leafnode/4351

I am working on making a deb of leafnode-2 and can confirm it works!

--

-- 
Do they only stand
By ignorance, is that their happy state,
The proof of their obedience and their faith?
Permalink | Reply | 1 comment |
headers
Chris G | 2 Dec 2009 20:29

Re: Does 'expire' really mean what it says?

On Wed, Dec 02, 2009 at 07:20:22PM +0100, Matthias Andree wrote:
> Am 02.12.2009, 18:28 Uhr, schrieb Chris G <cl@...>:
>
>> At the top of my leafnode config file I have:-
>>
>>     ## Unread articles will be deleted after this many days if
>>     ## you don't define special expire times. Mandatory.
>>     expire = 20
>>
>> Does it really mean *unread* articles will be deleted after 20 days?
>
> Yes (assuming texpire installed as cron job, as Daniel remarked rightly), 
> but leafnode-2 will retain context for threads that you read, i. e.  
> articles of which you have read a followup will remain in the spool  
> (unless you run texpire -a that is).
>
> Zero maintenance means not filling up your disk if you leave everything  
> alone, right? :)
>
>> Or does it mean *all* articles will be deleted after 20 days?
>
> leafnode-2: "20 days after any article in the thread was last read"
> leafnode-1 in any setting, or leafnode-2 with texpire -a: "20 days after  
> the article was last read" (if ever).
>
> reading articles defers expiry unless you specify the -f option to  
> fetchnews.
>
> If someone wants to help leafnode, feel free to write this up for  
> leafnode-2 and create a patch or a new section for texpire.8.in and/or
(Continue reading)

Permalink | Reply | 2 comments |
headers
Whiskers | 2 Dec 2009 23:07
Picon
Favicon

Re: Does 'expire' really mean what it says?

On Wed, 2 Dec 2009 19:29:42 +0000 Chris G <cl@...> wrote:
> On Wed, Dec 02, 2009 at 07:20:22PM +0100, Matthias Andree wrote:
> > Am 02.12.2009, 18:28 Uhr, schrieb Chris G <cl@...>:
> >> At the top of my leafnode config file I have:-
> >>
> >>     ## Unread articles will be deleted after this many days if
> >>     ## you don't define special expire times. Mandatory.
> >>     expire = 20
> >>
> >> Does it really mean *unread* articles will be deleted after 20 days?

[...]

> > If someone wants to help leafnode, feel free to write this up for  
> > leafnode-2 and create a patch or a new section for texpire.8.in
> > and/or leafnode.8.in. You will be credited in the NEWS file. :)

[...]

> What the rules for texpire actually mean is that any article that has
> not been read for 'expire' days will be deleted.  I guess the subtlety
> is that 'unread for 20 days' is very different from 'unread'.

Perhaps a better wording for the sample config file might be:

    Articles will be deleted after being unread for this many days if you
    don't define special expire times.  Mandatory.

--

-- 
-- ^^^^^^^^^^
(Continue reading)

Permalink | Reply | 1 comment |
headers
Adam Funk | 3 Dec 2009 15:24
Favicon

Re: can't re-compile leafnode after Ubuntu karmic upgrade

On 2009-12-02, Les Harris wrote:

> Adam Funk <a24061@...> writes:
>
>> The configure step [1] seems to work OK [2], but make fails [3] even
>> after doing make clean first.  I have the lua5.1 package (version
>> 5.1.4-3) on the system, which configure seems to detect.  
>
> This is a known issue.  MA posted a small patch here:
>
> http://article.gmane.org/gmane.network.leafnode/4351
>
> I am working on making a deb of leafnode-2 and can confirm it works!

That patch works.  Thanks.

(Sorry I didn't find it in the archive before asking.)
Permalink | Reply | 0 comments |

Gmane