Re: Re: Recent snapshots?

--=-4qDjlVCjtVkkazTHi2Yo
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

On Thu, 2003-01-23 at 06:13, Jos Vos wrote:

> I never answered this, IIRC.  But nothing seems to have changed since
> then.  That is, no new snapshots (or releases) are visible (some kind
> of process that automatically extracts a weekly snapshot from bitkeeper
> and put it on the ftp site would still be great).

See below - I took two days researching options before replying to this
email.

> 
> To answer your question: I am interested in both the 1.4.x and 1.5.x
> versions (or whatever future releases are named).  I'm especially
> interested in the PostgreSQL support and the implementation of new
> features, that make up2date preferable above apt etc.  But as
> development progress is unclear to me now, it is very difficult to
> contribute to the further development of Current.

Bingo. See below

> 
> To summarize:
> A status update on the development tracks of Current (current code,
> future plans, proposed schedule) *and* a more easy access to the
> code base(s) would make it more easy for others to help with the
> development of Current.

I've been threatened with patches before.... :)

Here;s the deal. I hate CVS. So I tried bk. John and I found bk to be
VERY powerful in some areas (the bk guis, while looking like tk, are
nigh on perfect)

BUT.

That caused a number of folks to not want to deal with Current. There's
also no easy to shelp at bug reports, todo list, etc online.

So, I quit. 

Just kidding. We're looking at hosting options now. I, personally, don't
think soureforge has a long history ahead of it. I would much prefer to
find some site running gforge or whatever. Savannah is also a potential.

So, I'm going to compromise. We'll switch to CVS at one of these hosting
sites (I'm inquiring at a couple about their subversion plans) and I'll
put up with CVS. 

You (the collective you) will post meaningful bug reports, help with web
pages, and submit patches. That last being the one I care about most.

So take heart - I'm changing the development process right now to
improve current.

-------------------------------------------------------------------------

Whats taking so long with support for 8.0? 
Well, if you take the notes attached to this email, and install current
on an 8.0 box, you'll discover that it doesn't work.

What appears to be happening is either some undocumented chnage in
apache, or mod_python, is causing the second <Location> block to not be
correctly used.

What that means is that when current/up2date goes to actually transfer a
file, neither the accesshandler nor the typehandler in mod_python is
running. Obviously, current as an anonymous only server in 1.4.x will
live without the accesshandler. But we HAVE to have the typehandler, and
it just plain doesn't work. Johns looked at it, I've looked at it, and
so far two OTHER people have looked at it. None of us see the problem.

So, if you're an apache demi-god or even senior mortal being, we need
help. I think its in the apache config (its either wrong, and just kinda
worked for some reason under 1.3, or its right and just don't work under
2.0)

You'll have to do this testing on an 8.0 box.
-- 
Hunter Matthews                          Unix / Network Administrator
Office: BioScience 145/244               Duke Univ. Biology Department
Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779 A5DB 8B09 F0F8 8438
Never take candy from strangers. Especially on the internet.

--=-4qDjlVCjtVkkazTHi2Yo
Content-Disposition: attachment; filename=server8.notes
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; name=server8.notes; charset=ISO-8859-1

1. Apache -> httpd rename
   Delete current.spec dependancy or wrap it in 8.x-ness

2. httpd now has an /etc/httpd/conf.d dir
   Tailor made for us to slip a current.conf file into.
   Installation is now easier.

3. mod_ssl configured in /etc/httpd/conf.d/ssl.conf file
   has "ServerName new.host:443" which must be replaced with the=20
   real ssl'd server name.

Typical error message is as follows:

[Sat Jan 11 19:01:24 2003] [warn] RSA server certificate CommonName (CN)
`dangermouse.biology.duke.edu' does NOT match server name!?

4. /var/log/httpd is now writable only by root, as is the "parent" httpd
   process.  HOWEVER, the actual children are owned by "apache". So=20
   as a temporary measure, I moved the log file up one dir to /var/log.

5. Rpm breakage. (he did upgrade from 4.0 to 4.1)=20
   rpm.headerFromPackage() is now rpm.ts.hdrFromFdno()

6. Go back to 6 for final 1.5 solution, but installing rpm404-python and=20
   librpm404 should be a good temporary fix for 1.4

7. Something in 6.2 packages is causing xmlrpclib to choke on the=20
   getObsoletes file. Ditched 6.2 for now.

8. Error from the mime_magic_file. Disabled by commenting out in=20
   httpd.conf. Fix / work around later.

  =20

--=-4qDjlVCjtVkkazTHi2Yo--