savannah-hackers-public
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-hackers-public] Update on upgrades


From: Bob Proulx
Subject: [Savannah-hackers-public] Update on upgrades
Date: Fri, 28 Jan 2022 12:28:28 -0700

Savannah Hackers,

Just a very short status update note.

I have been focusing on migrating services to the new vcs2 which is
the up to date Trisquel 9 image.  It includes the newer OpenSSH and
avoids the SHA1 deprecation problem with ssh that members committing
vcs possibly hit if they have the newest OpenSSH.

Git has been transferred to the new server late December.  A few
initial forgotten items but worked out asap and hopefully soon
enough.  All seems good.

One problem report outstanding from Paul Eggert about ssh connections
hanging around that is as yet not understood.

I have been subsequently working on getting Subversion over on the new
systems.  The regression test suite of external services is the
easiest summary.

    FAIL: svn-http
    FAIL: svn-https
    PASS: svn-rsync
    PASS: svn-ssh
    PASS: svn-svn
    PASS: svn-web

The svn:// protocol through xinetd for anonymous checkouts is working.
The authenticated ssh for member access (same as for git) and commits
is working.  The ViewVC web interface is working.  The raw repository
rsync access (trivial really) is of course working.

I have been banging my head against the https/http WebDAV
configuration.  That's all Apache using libapache2-mod-svn and seems
like it should be working but I haven't been able to make it happy
yet.  I'll keep working on it.  The smallest of details can cause the
biggest problems.  Once that is fixed then Subversion can move to the
new OS and ssh for svn will also be good to go for SHA1 obsolescence.

After that I would start on hg and bzr.  Also download which also uses
member ssh access.

I also should work on frontend too.  I actually don't think it would
be as much effort as the vcs systems.  It was the SHA1 obsolescence
that focused my efforts there.

Bob

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]