unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sam Vilain <sam@vilain.net>
Cc: savannah-hackers@gnu.org, rms@gnu.org,
	arch-users@lists.fifthvision.net,
	captain_milk_farmer@hotmail.com, emacs-devel@gnu.org
Subject: Re: [Savannah-hackers] Savannah NEEDS sftp; suggestions and offer of help
Date: Sat, 2 Aug 2003 02:59:44 +0100	[thread overview]
Message-ID: <200308020259.53945.sam@vilain.net> (raw)
In-Reply-To: <20030801163052.GA15240@reactor-core.org>

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


    The risk seems low; I and other Debian developers have been using the
    current C libraries for a couple weeks now and they are working
    nicely.

Yes, upgrading the C libraries is asking for trouble. Why not just
build the newer version against your distribution?

  sudo apt-get install build-essential fakeroot
  apt-get build-dep ssh
  apt-get source ssh
  cd `ls -dt openssh*|head -1`
  dpkg-buildpackage -b -uc -rfakeroot
  cd ..
  scp ssh*deb savannah.gnu.org:
    [...]

If it saves you time, there's a binary for 3.6.1p2 compiled in this
manner for debian stable at:

  http://vilain.net/ssh_3.6.1p2-4_i386.deb

[md5 b68f3c6b8ad231b5f3382178027b8359]
- -- 
Sam Vilain, sam@vilain.net

Real software engineers eat quiche.





-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/KxsTpCUwqQW1LxMRAoeFAKDD8TaaQNFe6WuJ4s1+oSQf1Bq3pwCgv0iF
s5goFGs+w9Fce+ebX7P44Kc=
=gl3k
-----END PGP SIGNATURE-----

  reply	other threads:[~2003-08-02  1:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01  7:49 Savannah NEEDS sftp; suggestions and offer of help Jonathan Walther
2003-08-01  9:48 ` [Savannah-hackers] " Jaime E. Villate
2003-08-01 16:30   ` Jonathan Walther
2003-08-02  1:59     ` Sam Vilain [this message]
2003-08-02  9:21       ` Rudy Gevaert
2003-08-02 14:04         ` Nic
2003-08-03  7:33           ` Jonathan Walther
2003-08-01 11:40 ` Andreas Fuchs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200308020259.53945.sam@vilain.net \
    --to=sam@vilain.net \
    --cc=arch-users@lists.fifthvision.net \
    --cc=captain_milk_farmer@hotmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=savannah-hackers@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).