noffle-users

Re: [Noffle-users] Noffle with tin

[Balas M. <ba...@tt...>]

On Fri, 2 Jul 2004, Jim Hague wrote:

> On 01-Jul-2004 Balas Mark wrote:
> >> If you're using inetd, you need to replace the 'nntp' line there with
> >> nntp stream tcp nowait news /usr/sbin/tcpd /usr/local/bin/noffle -r
> >>
> >> (assuming your noffle executable is in /usr/local/bin). If it's xinetd you
> >> use,
> >> edit packages/redhat/noffle-xinetd and change 'disable = yes' to 'disable =
> >> no', and copy it to /etc/xinetd.d and remove any file there that runs
> >> leafnode.
> >
> > I did it (which noffle said that the executable is in /usr/bin/noffle);
> > now tin connects to localhost, than gives the error message
> >
> >    Connection to news server has timed out. Reconnect? (Y/n) Y
>
> Let's start by making sure that Noffle is installed and will work as a server.
>
> First, I think you said you'd done a 'noffle --query groups' and a 'noffle
> --fetch' to populate the news base with groups and some articles.
>
> Now try a quick server session run from the command line. Here's one I just
> did. The lines I typed to the server are indicated by '>'.
>
>   jim@fluffy:~$ noffle -r
>   200 NNTP server NOFFLE 1.1.4
> > list active uk.comp.os.*
>   215 Groups
>   uk.comp.os.win95 2317 2317 y
>   uk.comp.os.linux 56726 56374 y
>   uk.comp.os.win2000 4655 4655 y
>   .
> > quit
>   205 Goodbye
>   jim@fluffy:~$
>
> You may not get the same group list.
>
> Assuming that all works, the remaining problem is sorting out inetd or xinetd.

It seems it worked:

trychydts:~# noffle -r
200 NNTP server NOFFLE 1.0.1
list active uk.comp.os.*
215 Groups
uk.comp.os.linux 185354 185355 y
uk.comp.os.win2000 18083 18084 y
uk.comp.os.win95 52220 52221 y
.
quit
205 Goodbye

> The goal is to be able to do the same as above but via a network connection,
> like this:
>
>   jim@fluffy:~$ telnet localhost nntp
>   Trying 127.0.0.1...
>   Connected to localhost.
>   Escape character is '^]'.
>   200 NNTP server NOFFLE 1.1.4
>   list active uk.comp.os.*
>   215 Groups
>   uk.comp.os.win95 2317 2317 y
>   uk.comp.os.linux 56726 56374 y
>   uk.comp.os.win2000 4655 4655 y
>   .
>   quit
>   205 Goodbye
>   Connection closed by foreign host.
>   jim@fluffy:~$

[...]

> If you can do the above telnet session successfully, then Noffle is correctly
> installed as a server, and the problem is with the tin configuration.

There seems to be a problem here:

There is a problem here:

trychydts:~# telnet localhost nntp
Trying 127.0.0.1...
Connected to trychydts.
Escape character is '^]'.
200 NNTP server NOFFLE 1.0.1
list active uk.comp.os.*
503 Cannot init server
215 Groups
Connection closed by foreign host.



> Now, your system will be using inetd or xinetd, but not both. Most modern
> Linux
> distros use xinetd, but not all - Debian, for example, uses inetd by default.
> I'm guessing from what you said that you have xinetd. This is trickier for me
> to help with, 'cos I'm on Debian. Can you mail the contents of the noffle file
> you put in /etc/xinetd.d and we'll check for the problem.

I am on Debian, too, so my system most probably uses inetd.

I hope you meant to contents of the /etc/init.d/noffle file; it is this:
-------
#!/bin/sh

[ -f /etc/noffle/conf.debian ] || exit 0
. /etc/noffle/conf.debian
[ -x $NOFFLE ] || exit 0

PATH=/bin:/usr/bin:/sbin:/usr/sbin

case "$1" in
  start)
    echo -n "Initializing noffle: "
    [ "$NOFFLE_FETCHMODE" = ppp ] && $NOFFLE --offline
    [ "$NOFFLE_FETCHMODE" = cron ] && $NOFFLE --online
    echo "done."
    ;;
  stop)
    echo -n "Stopping noffle: "
    $NOFFLE --offline
    echo "done."
    ;;
  restart|force-reload)
    $0 start
    ;;
  *)
    echo "Usage: /etc/init.d/$NAME {start|stop}"
    exit 1
    ;;
esac

exit 0
# vim:set ts=8:
------

Thanks any help in advance,


Mark Balas

Re: [Noffle-users] Noffle with tin

[Jim H. <jim...@ac...>]

On 01-Jul-2004 Balas Mark wrote:
>> If you're using inetd, you need to replace the 'nntp' line there with
>> nntp stream tcp nowait news /usr/sbin/tcpd /usr/local/bin/noffle -r
>>
>> (assuming your noffle executable is in /usr/local/bin). If it's xinetd you
>> use,
>> edit packages/redhat/noffle-xinetd and change 'disable = yes' to 'disable =
>> no', and copy it to /etc/xinetd.d and remove any file there that runs
>> leafnode.
> 
> I did it (which noffle said that the executable is in /usr/bin/noffle);
> now tin connects to localhost, than gives the error message
> 
>    Connection to news server has timed out. Reconnect? (Y/n) Y

Let's start by making sure that Noffle is installed and will work as a server.

First, I think you said you'd done a 'noffle --query groups' and a 'noffle
--fetch' to populate the news base with groups and some articles.

Now try a quick server session run from the command line. Here's one I just
did. The lines I typed to the server are indicated by '>'.

  jim@fluffy:~$ noffle -r
  200 NNTP server NOFFLE 1.1.4
> list active uk.comp.os.*
  215 Groups
  uk.comp.os.win95 2317 2317 y
  uk.comp.os.linux 56726 56374 y
  uk.comp.os.win2000 4655 4655 y
  .
> quit
  205 Goodbye
  jim@fluffy:~$

You may not get the same group list.

Assuming that all works, the remaining problem is sorting out inetd or xinetd.
The goal is to be able to do the same as above but via a network connection,
like this:

  jim@fluffy:~$ telnet localhost nntp
  Trying 127.0.0.1...
  Connected to localhost.
  Escape character is '^]'.
  200 NNTP server NOFFLE 1.1.4
  list active uk.comp.os.*
  215 Groups
  uk.comp.os.win95 2317 2317 y
  uk.comp.os.linux 56726 56374 y
  uk.comp.os.win2000 4655 4655 y
  .
  quit
  205 Goodbye
  Connection closed by foreign host.
  jim@fluffy:~$

This, by the way, is what inetd or xinetd do - they handle the network port, and
start a program to service the connection. That program thinks it is just
talking to standard input and output.

If you can do the above telnet session successfully, then Noffle is correctly
installed as a server, and the problem is with the tin configuration.

Now, your system will be using inetd or xinetd, but not both. Most modern Linux
distros use xinetd, but not all - Debian, for example, uses inetd by default.
I'm guessing from what you said that you have xinetd. This is trickier for me
to help with, 'cos I'm on Debian. Can you mail the contents of the noffle file
you put in /etc/xinetd.d and we'll check for the problem.

> I guess I am overlooking something trivial again (because of my nearly
> complete lack of experience). I do appreciate your patience.

No problem - I've battled (x)inetd in the past. You're not the only one to have
problems. I do know that this is the difficult stage; don't worry - we will get
there.

-- 
Jim Hague - jim...@ac...          Never trust a computer you can't lift.

Re: [Noffle-users] Noffle with tin

[Balas M. <ba...@tt...>]

On Thu, 1 Jul 2004, Jim Hague wrote:

> On 01-Jul-2004 Balas Mark wrote:
> > I tried it; tin gave me this answer:
> >
> > Reading config file...
> > release 20020311 ("Toxicity") [UNIX] (c) Copyright 1991-2002 Iain Le
> >
> > Connecting to localhost...
> >
> > Leafnode 1.9.19, pleased to meet you!
>   ^^^^^^^^
>   Noffle != Leafnode.....

I suspected it, I just did not know how to get rid of it.

> Your (x)inetd is configured to run Leafnode, not Noffle (unless you want to use
> Leafnode, in which case you're asking the wrong list....). If you're using
> inetd, you need to replace the 'nntp' line there with
>
> nntp stream tcp nowait news /usr/sbin/tcpd /usr/local/bin/noffle -r
>
> (assuming your noffle executable is in /usr/local/bin). If it's xinetd you use,
> edit packages/redhat/noffle-xinetd and change 'disable = yes' to 'disable =
> no', and copy it to /etc/xinetd.d and remove any file there that runs leafnode.

I did it (which noffle said that the executable is in /usr/bin/noffle);
now tin connects to localhost, than gives the error message

   Connection to news server has timed out. Reconnect? (Y/n) Y

I guess I am overlooking something trivial again (because of my nearly
complete lack of experience). I do appreciate your patience.



Mark Balas

Re: [Noffle-users] Noffle with tin

[Jim H. <jim...@ac...>]

On 01-Jul-2004 Balas Mark wrote:
> I tried it; tin gave me this answer:
> 
> Reading config file...
> release 20020311 ("Toxicity") [UNIX] (c) Copyright 1991-2002 Iain Le
> 
> Connecting to localhost...
> 
> Leafnode 1.9.19, pleased to meet you!
  ^^^^^^^^
  Noffle != Leafnode.....

> 
> Reading keymap file...
> 
> Reading input history file...
> 
> Reading groups from active file...
> Can't open /var/lib/news/active
> 
> And then it exits.

Your (x)inetd is configured to run Leafnode, not Noffle (unless you want to use
Leafnode, in which case you're asking the wrong list....). If you're using
inetd, you need to replace the 'nntp' line there with

nntp stream tcp nowait news /usr/sbin/tcpd /usr/local/bin/noffle -r

(assuming your noffle executable is in /usr/local/bin). If it's xinetd you use,
edit packages/redhat/noffle-xinetd and change 'disable = yes' to 'disable =
no', and copy it to /etc/xinetd.d and remove any file there that runs leafnode.


-- 
Jim Hague - jim...@ac...          Never trust a computer you can't lift.

Re: [Noffle-users] Noffle with tin

[Balas M. <try...@fr...>]

At 11:38 2004.07.01., Jim Hague wrote:
>On 01-Jul-2004 Balas Mark wrote:
> > I am using tin for reading news and I tried to use it with noffle. I
> > successfully configured noffle to download some articles from a 
> newsgroup I
> > regulary read (in "full" mode) and saved them in /var/spool/noffle.
> >
> > I tried to configure tin to use this spool: I changed spool dir
> > /etc/tin/tin.defaults to the directory mentioned above, but tin does not
> > seem to recognise the articles or the group.
>
>Short explanation:

Thank you for your explanations, they were really helpful in understanding 
the problem. However, still did not succeed; I could really appreciate if 
you could help a bit more, if you can.


>You need to use 'tin -r' or 'rtin' with Noffle, and either put the name of the
>machine running Noffle in /etc/nntpserver or in an environment variable
>NNTPSERVER. In your case, Noffle is on the same machine as tin, so 'localhost'
>as the machine name is fine. Try this:
>
>$ export NNTPSERVER=localhost
>$ tin -r


I tried it; tin gave me this answer:

Reading config file...
release 20020311 ("Toxicity") [UNIX] (c) Copyright 1991-2002 Iain Le

Connecting to localhost...

Leafnode 1.9.19, pleased to meet you!

Reading keymap file...

Reading input history file...

Reading groups from active file...
Can't open /var/lib/news/active

And then it exits.


Thanks in advance,


Mark Balas

Re: [Noffle-users] Noffle with tin

[Jim H. <jim...@ac...>]

On 01-Jul-2004 Balas Mark wrote:
> I am using tin for reading news and I tried to use it with noffle. I 
> successfully configured noffle to download some articles from a newsgroup I 
> regulary read (in "full" mode) and saved them in /var/spool/noffle.
> 
> I tried to configure tin to use this spool: I changed spool dir 
> /etc/tin/tin.defaults to the directory mentioned above, but tin does not 
> seem to recognise the articles or the group.

Short explanation:

You need to use 'tin -r' or 'rtin' with Noffle, and either put the name of the
machine running Noffle in /etc/nntpserver or in an environment variable
NNTPSERVER. In your case, Noffle is on the same machine as tin, so 'localhost'
as the machine name is fine. Try this:

$ export NNTPSERVER=localhost
$ tin -r

Longer explanation (apologies if you know all this):

The 'traditional' way in which news servers store the articles they receive is
in a file system hierarchy under /var/spool/news. For example, article 255 in
comp.lang.c would be in a file with path 'comp/lang/c/255'. News reading
programs would read directly from these files. This is what tin is trying to do
on your system.

This traditional storage has its good points, but is not very good if the news
reading program is on a different machine to the news server. So a protocol,
NNTP, is used to communicate between readers and servers (and between servers).
Once you're using NNTP, you don't have to use the traditional spool storage.
Noffle's original author decided to keep articles in a database-like file
instead, which is why Noffle uses /var/spool/noffle and not /var/spool/news;
/var/spool/noffle doesn't have the structure expected under /var/spool/news. So
to use Noffle, you have to use NNTP.

-- 
Jim Hague - jim...@ac...          Never trust a computer you can't lift.

[Noffle-users] Noffle with tin

[Balas M. <try...@fr...>]

Hello!


I decided just recently to use Linux so I have to tell in advance that I am 
really inexperienced - sorry for that.

I am using tin for reading news and I tried to use it with noffle. I 
successfully configured noffle to download some articles from a newsgroup I 
regulary read (in "full" mode) and saved them in /var/spool/noffle.

I tried to configure tin to use this spool: I changed spool dir 
/etc/tin/tin.defaults to the directory mentioned above, but tin does not 
seem to recognise the articles or the group.

Could you help me out somehow?


Thanks in advance,



Mark Balas

[Noffle-users] no sure way to UNmark for download

[Dan J. <ji...@ji...>]

Gentlemen, I remove the line from the requested/* file in question,
but the article in question is often fetched anyway.
Blast, there's no sure way to cancel a request once one has seen
the ominous "[ NOFFLE INFO: Marked for download ]"
$ set /var/spool/noffle/requested/news.gmane.org
$ cat $1
<so...@ob...n't.want.to.download>
$ ed $1
d
wq
$ noffle -f #often gets it anyway

[Noffle-users] check for noffle.conf syntax errors before even leaving the editor

[Dan J. <ji...@ji...>]

Emacs users might want to put

# Check for syntax errors before even leaving the editor!:
# Local Variables:
# compile-command: "noffle -v"
# End:

at the bottom of noffle.conf.

[Noffle-users] Re: test noffle filters offline

[Dan J. <ji...@ji...>]

BTW, the current online real time feedback,
"Filter 7 fired on message <E1B...@mo...>"
isn't enough to make us confident our filter isn't going overboard,
etc.  True, it doesn't need to be as verbose as procmail's logs, but
still, an additional line saying what matched would be nice... or at
least the original From and Subject, so we don't have to try to dig
them up to check.

Re: [Noffle-users] test noffle filters offline

[Jim H. <jim...@ac...>]

On 25-May-2004 ji...@ji... wrote:
> Wishlist: a way to test our noffle filters out on a message without
> having to go online. Like spamassassin -t.  Probably have to create
> some local group, etc.

Yes, I can see that this would be a nice thing to have. I'll take a look when I
can (off on holiday tomorrow...).

-- 
Jim Hague - jim...@ac...          Never trust a computer you can't lift.

[Noffle-users] test noffle filters offline

[<ji...@ji...>]

Wishlist: a way to test our noffle filters out on a message without
having to go online. Like spamassassin -t.  Probably have to create
some local group, etc.

Re: [Noffle-users] Remote access to a noffle news server

[Jim H. <jim...@ac...>]

On 03-May-2004 Richard Worwood wrote:
> I'm a newbie to noffle and to be honest configuring news servers in general
> and I'm having a bit of a problem setting up noffle so that I can access it
> remotely using a non linux news client such as outlook express.
> 
> I've got ipchains setup to permit access to port 119 and also xinetd
> configured to start noffle but it is not allowing connections to port 119
> remotely.

Yes, the inital setting up can be a bit fiddly.

The first thing to do is to get everything working for local access on the
server machine. On the server, try

$ telnet localhost nntp

If everything is working on the server, you'll see

Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
200 NNTP server NOFFLE 1.1.4

If, on the other hand, it says

Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused

then the xinetd setup isn't right. I'm still on inetd, but I believe that the
noffle xinetd configuration should look like this:

service nntp
{
        disable         = no
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = news
        group           = news
        only_from       = 127.0.0.1
        server          = /usr/bin/noffle
        server_args     = -r
}

Note the setting for 'disable'. Also, if you want to allow access from other
machines you'll need to do something about only_from.

Once you can connect on the server, then remote access problems are either
xinetd from restrictions or iptables problems.

Hope this helps. Let us see your xinetd configuration if you still have
problems.

Finally, if you're planning to allow access over the net, you'll want some form
of authentication....


-- 
Jim Hague - jim...@ac...          Never trust a computer you can't lift.

[Noffle-users] Remote access to a noffle news server

[Richard W. <ric...@td...>]

I'm a newbie to noffle and to be honest configuring news servers in general
and I'm having a bit of a problem setting up noffle so that I can access it
remotely using a non linux news client such as outlook express.

I've got ipchains setup to permit access to port 119 and also xinetd
configured to start noffle but it is not allowing connections to port 119
remotely.

If anyone can assist in this I would be most gratefull.

Re: [Noffle-users] Marked for Download Problem

[Jim H. <jim...@ac...>]

On 08-Apr-2004 Andre Berger wrote:
> Took me a while to figure out what went wrong: It was a timing
> problem. My news user agent sometimes fetched the articles between
> step one and step two, then listed them as fetched and subsequently
> ignored the bodies that arrived later. I made sure it won't run while
> a noffle fetch is in progress, and everything is OK now.

That makes it sound like your user agent is caching articles. Does it have any
way of turning off article caching? There are some notes in docs/NOTES on
various agents.


-- 
Jim Hague - jim...@ac...          Never trust a computer you can't lift.

[Noffle-users] Re: can't remove Path

[Dan J. <ji...@ji...>]

Jim> That's because according to my reading of the RFCs a well-formed article MUST
Jim> have a Path header.

Well, when I post thru gmane.org, mine is thrown away.  And when I
post thru news.individual.net, it even becomes X-Orig-Path:
unknown.local!not-for-mail, not what I gave it.
OK, as I suppose I can't save any bytes in the archives of posterity
by manipulating it... over and out.

Re: [Noffle-users] can't remove Path

[Jim H. <jim...@ac...>]

On 09-Apr-2004 Dan Jacobson wrote:
> Reading noffle.conf(5) I see path-header can't be set to make no Path
> header at all, for those times one just might want to do that.

That's because according to my reading of the RFCs a well-formed article MUST
have a Path header.

5.  Mandatory Headers
                                                                                
   An article MUST have one, and only one, of each of the following
   headers: Date, From, Message-ID, Subject, Newsgroups, Path.


-- 
Jim Hague - jim...@ac...          Never trust a computer you can't lift.

[Noffle-users] can't remove Path

[Dan J. <ji...@ji...>]

Reading noffle.conf(5) I see path-header can't be set to make no Path
header at all, for those times one just might want to do that.

Re: [Noffle-users] Marked for Download Problem

[Andre B. <and...@we...>]

* Jim Hague <jim...@ac...>, 2004-03-31 23:07 +0200:
> On 31-Mar-2004 Andre Berger wrote:
> > I see a strange behavior in noffle 1.1.5: articles Marked for
> > Download are never fetched. In the first place, I don't understand
> > why there are such articles anyway.
> 
> Noffle fetches from upstream in basically two steps. First it issues an XOVER
> to get the overview info for the unread articles upstream. The filters run on
> the overview information. Articles are created at that point as 'Marked for
> download', assuming they survived filtering, and entered in the list of
> articles to be requested from upstream.
> 
> The next step is to take articles to be requested in turn and download their
> bodies.
> 
> If anything goes wrong with the second step, articles will be left as 'marked
> for download'. I see this quite often from my upstream; the upstream is usually
> overloaded and will have overviews available before bodies. The article bodies
> appear on subsequent fetches. If, however, your newsreader caches articles, you
> won't see the body when it arrives, as the newsreader will just show the 'body'
> it got before, the one saying 'Marked for download'. Which newsreader are you
> using?
> 
> > I'm on modem dialup, and my
> > /etc/ppp/ip-up contains "noffle -n && noffle -f", my /etc/ppp/ip-down
> > "noffle -o".
> 
> Ah. You're using online mode. That shouldn't make any difference, but I don't
> use it myself so I can't be sure.
> 
> If you run noffle -f from the command line, it should give you some details on
> what it downloads. The same details will be recorded in the syslog 'news' as
> well. Check them over and see if you get many 'Retrieving failed' messages.

Took me a while to figure out what went wrong: It was a timing
problem. My news user agent sometimes fetched the articles between
step one and step two, then listed them as fetched and subsequently
ignored the bodies that arrived later. I made sure it won't run while
a noffle fetch is in progress, and everything is OK now. Also, I
switched to offline mode just in case. 

Thanks!

-Andre

Re: [Noffle-users] Marked for Download Problem

[Jim H. <jim...@ac...>]

On 31-Mar-2004 Andre Berger wrote:
> I see a strange behavior in noffle 1.1.5: articles Marked for
> Download are never fetched. In the first place, I don't understand
> why there are such articles anyway.

Noffle fetches from upstream in basically two steps. First it issues an XOVER
to get the overview info for the unread articles upstream. The filters run on
the overview information. Articles are created at that point as 'Marked for
download', assuming they survived filtering, and entered in the list of
articles to be requested from upstream.

The next step is to take articles to be requested in turn and download their
bodies.

If anything goes wrong with the second step, articles will be left as 'marked
for download'. I see this quite often from my upstream; the upstream is usually
overloaded and will have overviews available before bodies. The article bodies
appear on subsequent fetches. If, however, your newsreader caches articles, you
won't see the body when it arrives, as the newsreader will just show the 'body'
it got before, the one saying 'Marked for download'. Which newsreader are you
using?

> I'm on modem dialup, and my
> /etc/ppp/ip-up contains "noffle -n && noffle -f", my /etc/ppp/ip-down
> "noffle -o".

Ah. You're using online mode. That shouldn't make any difference, but I don't
use it myself so I can't be sure.

If you run noffle -f from the command line, it should give you some details on
what it downloads. The same details will be recorded in the syslog 'news' as
well. Check them over and see if you get many 'Retrieving failed' messages.

-- 
Jim Hague - jim...@ac...          Never trust a computer you can't lift.

[Noffle-users] Marked for Download Problem

[Andre B. <and...@we...>]

Hi there,

I see a strange behavior in noffle 1.1.5: articles Marked for
Download are never fetched. In the first place, I don't understand
why there are such articles anyway. I'm on modem dialup, and my
/etc/ppp/ip-up contains "noffle -n && noffle -f", my /etc/ppp/ip-down
"noffle -o". My newsreader is set up to fetch articles from localhost
every five minutes, it's run from fetchmail as postconnect command.

-Andre

Re: [Noffle-users] Re: Version 1.1.5 in CVS

[Jim H. <jim...@ac...>]

On 26-Mar-2004 Rolf Leggewie wrote:
> Jim Hague <jim...@ac...> writes:
> 
>> That's the right idea. In fact you want
>>
>> cvs -z3 -d:pserver:ano...@cv...:/cvsroot/noffle
>>         patch -D 2003-06-25 noffle
> 
> Sure and that is what I did.  But what can I say, it did not work!  I
> got lots of errors about "Reversed (or previously applied) patch
> detected".

Actually, the above isn't quite right. The date should be *after* the date that
the final 1.1.5 changes were made. 2003-06-26 works.

That leaves one further problem. The debian control files (under 'debian' in
the CVS tree) were removed from the release; they're part of Noffle CVS but
at the time I didn't want to distribute them as part of a Noffle release, as
they're not under my control. So the patch will contain changes to debian/
files that don't exist. You might want to remove them from the patch before
applying.

Anyway, if you do all that the patch will apply correctly to 1.1.5. I've just
tried it. :-)

-- 
Jim Hague - jim...@ac...          Never trust a computer you can't lift.

[Noffle-users] Re: Version 1.1.5 in CVS

[Rolf L. <no...@no...>]

Jim Hague <jim...@ac...> writes:

> That's the right idea. In fact you want
>
> cvs -z3 -d:pserver:ano...@cv...:/cvsroot/noffle
>         patch -D 2003-06-25 noffle

Sure and that is what I did.  But what can I say, it did not work!  I
got lots of errors about "Reversed (or previously applied) patch
detected".  This might be due to the fact that you made the change
locally on June 25th but the upload was a bit later.  I am not sure if
this would disturb CVS but this would seem a logical explanation to me
since then the diff I got would try to implement changes which you
uploaded already for 1.1.5 and which I have in that source distribution.
-- 
http://home.arcor.de/leggewie/
http://leggewie.biz/hamster.htm

Re: [Noffle-users] Version 1.1.5 in CVS

[Jim H. <jim...@ac...>]

On 25-Mar-2004 Rolf Leggewie wrote:
> if I interpret "cvs -z3
> -d:pserver:ano...@cv...:/cvsroot/noffle rlog -h
> noffle/ChangeLog" correctly, there does not appear to be a tag for
> release 1.1.5.

Correct. I stuffed up.....

> In the ChangeLog in 1.1.5 I read that the last change
> was made on June 25th of last year for that version.  I used "cvs -z3
> -d:pserver:ano...@cv...:/cvsroot/noffle patch -D
> 2003-06-25" to get a diff for the most current source release.  Is that
> correct?

That's the right idea. In fact you want

cvs -z3 -d:pserver:ano...@cv...:/cvsroot/noffle
        patch -D 2003-06-25 noffle

I'd also suggest 'patch -u' for shorter and more readable output.


-- 
Jim Hague - jim...@ac...          Never trust a computer you can't lift.

[Noffle-users] Version 1.1.5 in CVS

[Rolf L. <no...@no...>]

Hi,

if I interpret "cvs -z3
-d:pserver:ano...@cv...:/cvsroot/noffle rlog -h
noffle/ChangeLog" correctly, there does not appear to be a tag for
release 1.1.5.  In the ChangeLog in 1.1.5 I read that the last change
was made on June 25th of last year for that version.  I used "cvs -z3
-d:pserver:ano...@cv...:/cvsroot/noffle patch -D
2003-06-25" to get a diff for the most current source release.  Is that
correct?

Best regards

Rolf
-- 
http://home.arcor.de/leggewie/
http://leggewie.biz/hamster.htm