just tried making 0.97

just tried making 0.97

[Daniel Monjar]

And I got this:
-------------------------
make[1]: Leaving directory `/home/dmonjar/pgnus-0.97/lisp'
cd texi && make EMACS="/usr/local/bin/emacs" all
make[1]: Entering directory `/home/dmonjar/pgnus-0.97/texi'
make[1]: *** Warning: File `gnus.texi' has modification time in the
future (938448958 > 938448167)
if test -x /usr/bin/makeinfo; then \
  makeinfo -o gnus gnus.texi; \
else \
  /usr/local/bin/emacs -batch -q -no-site-file -eval '(find-file
"gnus.texi")' -l texinfmt -f texinfo-every-node-update -f
tex                                            info-format-buffer -f
save-buffer; \
fi
if test -x /usr/bin/makeinfo; then \
  makeinfo -o message message.texi; \
else \
  /usr/local/bin/emacs -batch -q -no-site-file -eval '(find-file
"message.texi")' -l texinfmt -f texinfo-every-node-update
-f                                             texinfo-format-buffer -f
save-buffer; \
fi
if test -x /usr/bin/makeinfo; then \
  makeinfo -o emacs-mime emacs-mime.texi; \
else \
  /usr/local/bin/emacs -batch -q -no-site-file -eval '(find-file
"emacs-mime.texi")' -l texinfmt -f
texinfo-every-node-update                                             -f
texinfo-format-buffer -f save-buffer; \
fi
make[1]: *** Warning:  Clock skew detected.  Your build may be
incomplete.
make[1]: Leaving directory `/home/dmonjar/pgnus-0.97/texi'

[dmonjar@monjard ~/pgnus-0.97]$ ls -l texi/gnus.texi
-rw-r--r--   1 dmonjar  dmonjar    705101 Sep 27 12:15 texi/gnus.texi

[dmonjar@monjard ~/pgnus-0.97]$ date
Mon Sep 27 12:03:28 EDT 1999

[dmonjar@monjard ~/pgnus-0.97]$ 
----------------------------------

of course, after I come back from lunch the problem will go away
<grin>...
-- 
Daniel Monjar (mailto:dmonjar@orgtek.com)
Organon Teknika
Durham, NC US

Re: just tried making 0.97

[Ted Rathkopf]

Daniel Monjar <dmonjar@orgtek.com> writes:

> make[1]: *** Warning:  Clock skew detected.  Your build may be
> incomplete.
> make[1]: Leaving directory `/home/dmonjar/pgnus-0.97/texi'

Are you building this on an NFS mounted drive?  If so, check the
clocks on both the machine where you are doing the build and the
machine which hosts the drive.

I had a similar problem when I was trying to build something last
week, and found that the clocks were about 20 minutes off.  Once I set 
the clocks to approximately the same time, everything worked fine.


-- 
Ted Rathkopf

Re: just tried making 0.97

[Lars Magne Ingebrigtsen]

Ted Rathkopf <ted@rathkopf.org> writes:

> Are you building this on an NFS mounted drive?  If so, check the
> clocks on both the machine where you are doing the build and the
> machine which hosts the drive.

The clock skew was on Quimby.  I've now whacked it about a bit.

(And we're still testing the news-to-mail thing.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

CVS write access policy & nntp gateway & bug reports & stuff

[Lars Magne Ingebrigtsen]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> (And we're still testing the news-to-mail thing.)

Hey!  It worked!

Anybody can now access the quimby.gnus.org news server.  Gatewaying
back and forth seems to work ok, so anyone who want to use it -- feel
free.

CVS read policy:  Anyone who wants to check things out of the CVS
thing -- go ahead.

CVS write policy:  People who have write access can check things into
the repository whenever they feel like it.  Before doing a release, I
will be going over the diff and chucking out anything I don't like,
but if nobody puts in things I don't like, that will make things
easier for me.  :-)  But you have my confidence.  Oh, but pleeeze --
please update the ChangeLog when you do any changes.

Perhaps a pgnus-current.tar.gz package should be created once a day -- 
just a CVS checkout, and then tarred and gzipped?

All bug reports go to the gnus-bug newsgroup.  Perhaps this group
shouldn't be open for reading for the entire world, since there might
be sensitive information there?  How about password-protecting that
group, but with a "public" password that people on this list knows
about? 

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: just tried making 0.97

[Stainless Steel Rat]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

* Daniel Monjar <dmonjar@orgtek.com>  on Mon, 27 Sep 1999
| make[1]: *** Warning: File `gnus.texi' has modification time in the
| future (938448958 > 938448167)

The problem here is that the timestamp on the file is in the future of what 
your system thinks the current time is.  This often happens with NFS.

Check your system time, and make sure that you have the correct time zone
offset.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE376Ksgl+vIlSVSNkRAnl+AKDV1H4vP5rSvIhiF0DDRYHVHEcfSACggPKQ
LtqZPz7yNimBWOhazVMuJRA=
=Ba98
-----END PGP SIGNATURE-----

-- 
Rat <ratinox@peorth.gweep.net>    \ Do not taunt Happy Fun Ball.
Minion of Nathan - Nathan says Hi! \ 
PGP Key: at a key server near you!  \ 

Re: CVS write access policy & nntp gateway & bug reports & stuff

[Wes Hardaker]

>>>>> On 27 Sep 1999 18:40:44 +0200, Lars Magne Ingebrigtsen <larsi@gnus.org> said:

Lars> Oh, but pleeeze -- please update the ChangeLog when you do any
Lars> changes.

You might consider generating the ChangeLog file from the cvs log
messages...  I do this and that way I don't have to worry about people 
updating the ChangeLog file.  Of course, teaching them to write
properly formatted commit messages is sometimes equally a pain...

I have a perl script if ya like...


-- 
"Ninjas aren't dangerous.  They're more afraid of you than you are of them."

Re: CVS write access policy & nntp gateway & bug reports & stuff

[Robert Bihlmeyer]

Hi,

>>>>> On 04 Oct 1999 08:59:31 -0700
>>>>> Wes Hardaker <wjhardaker@ucdavis.edu> said:

> You might consider generating the ChangeLog file from the cvs log
> messages...

IMHO it's better to induce people to keep a proper ChangeLog. If these 
people use emacs (which is a viable assumption in our case), and
pcl-cvs (not a big deal to install/enable), they can in turn generate
the log messages from the ChangeLog. (As easy as M-x cvs-update and
then 'C' on to commit a file.)

        Robbe

-- 
Robert Bihlmeyer	reads: Deutsch, English, MIME, Latin-1, NO SPAM!
<robbe@orcus.priv.at>	<http://stud2.tuwien.ac.at/~e9426626/sig.html>