Log in

No account? Create an account
LogJam [entries|archive|friends|userinfo]

[ website | LogJam ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

LoserJabber 2.1.3 [Feb. 6th, 2001|12:27 pm]
I have released LoserJabber 2.1.3.

Most importantly, this fixes the "no events in history" bug.

Read the Full ChangeLog for details.

I also have started building Debian packages for this release.
Download .tar.gz, .deb, or .rpm.
(In case you were wondering, I use Debian. I just never had a need for packages.)

In other news, I still hate sourceforge. Nothing ever works; they have really annoying web forms, which are doubly annoying because their servers are so slow; they are always changing things; it's confusing, even to me, and I'm a relatively experienced computer user.

I mean, I really appreciate the free hosting... but if I could host anywhere else, I would.

So, with this release of LoserJabber, I am no longer using the sourceforge interface for anything. I'll still use them for web space, CVS, and mailing lists, but only until I can get Brad to give me an account on bradfitz.com.

The next releases of LoserJabber will probably be the integration of *conditional* GNOME support.

[User Picture]From: corvar
2001-02-06 01:03 pm (UTC)


So if we are using the CVS version, should we just do a cvs update, or what?

I did notice the version number in CVS did not change.
(Reply) (Thread)
From: evan
2001-02-06 01:21 pm (UTC)


Whoopsie. CVS update again. :)
(Reply) (Parent) (Thread)
[User Picture]From: corvar
2001-02-06 01:33 pm (UTC)


That definitely broke stuff ;)
If you want a copy of what I see when I compile let me know.
(Reply) (Parent) (Thread)
From: evan
2001-02-06 02:31 pm (UTC)


I checked a fresh copy out of CVS, and I think I found the problem.

CVS update (be sure to run ./autogen.sh again) and see if it works.

Otherwise, let me know what the compile errors are. :)
(Reply) (Parent) (Thread)
[User Picture]From: corvar
2001-02-06 03:10 pm (UTC)


I do a ./autogen.sh everytime ;) I am not positive when it is needed or not, so I do it everytime. I rm -fr'ed the old source tree and did a clean checkout. After that everything works just fine, I guess I should have done that before saying anything. What I was seeing with just doing an update was:
ptiwrtx:/usr/src/misc/loserjabber-cvs/loserjabber# cvs update
? aclocal.m4
? configure
? Makefile.in
? config.log
? config.h
? Makefile
? debian
? stamp-h
? config.cache
? config.status
? loserjabber.spec
? pixmaps/Makefile.in
? pixmaps/Makefile
? src/Makefile.in
? src/Makefile
? src/.deps
? src/loserjabber
cvs server: Updating .
cvs server: Updating doc
cvs server: Updating macros
cvs server: Updating pixmaps
cvs server: Updating src
ptiwrtx:/usr/src/misc/loserjabber-cvs/loserjabber# ./autogen.sh
Generating build environment...
./cNow run ./configure .
ptiwrtx:/usr/src/misc/loserjabber-cvs/loserjabber# ./configure --prefix=/usr
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gtk-config... /usr/bin/gtk-config
checking for GTK - version >= 1.2.0... yes
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for a BSD compatible install... /usr/bin/install -c
checking how to run the C preprocessor... gcc -E
checking for getopt.h... yes
checking for getopt_long... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
creating src/Makefile
creating pixmaps/Makefile
creating debian/Makefile
sed: can't read ./debian/Makefile.in: No such file or directory
creating loserjabber.spec
creating config.h
config.h is unchanged
ptiwrtx:/usr/src/misc/loserjabber-cvs/loserjabber# make
cd . && autoheader
make all-recursive
make[1]: Entering directory `/usr/src/misc/loserjabber-cvs/loserjabber'
Making all in src
make[2]: Entering directory `/usr/src/misc/loserjabber-cvs/loserjabber/src'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/misc/loserjabber-cvs/loserjabber/src'
Making all in pixmaps
make[2]: Entering directory `/usr/src/misc/loserjabber-cvs/loserjabber/pixmaps'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/misc/loserjabber-cvs/loserjabber/pixmaps'
Making all in debian
make[2]: Entering directory `/usr/src/misc/loserjabber-cvs/loserjabber/debian'
make[2]: *** No rule to make target `all'. Stop.
make[2]: Leaving directory `/usr/src/misc/loserjabber-cvs/loserjabber/debian'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/misc/loserjabber-cvs/loserjabber'
make: *** [all-recursive-am] Error 2
[Exit 2 ]
(Reply) (Parent) (Thread)
From: evan
2001-02-06 03:30 pm (UTC)


Ah, good.
A clean checkout wouldn't have solved it... I had forgotten to commit debian/Makefile.am, which ./autogen.sh generates into Makefile.in, which ./configure generates into Makefile, which make was whimpering about not finding.

It's really confusing, to me, which is why I didn't catch it.

Thanks for the help!
(Reply) (Parent) (Thread)
[User Picture]From: bradfitz
2001-02-06 01:22 pm (UTC)
I'll hook ya up next time we get together....
(Reply) (Thread)