Re: [Savannah-users] Reading bug reports upside down
> Date: Fri, 18 Mar 2011 00:38:31 -0600 > From: Jordi Gutiérrez Hermoso > Cc: savannah-users@gnu.org > > 2011/3/18 Michał Masłowski : > >> I find it very awkward to read bug reports upside down, starting from > >> the newest, down to the actual bug report buried at the bottom of the > >> bug thread. > >> > >> Can this be modified easily? Would a patch to Savane be necessary or > >> accepted? > > > > Use "Print items comments from the oldest to the latest" option in your > > account conf. > > Thanks. That's a weird default. Do people actually like it? > > - Jordi G. H. > >
Re: [Savannah-users] Upgraded version control system environment
> Date: Fri, 08 Apr 2011 21:38:41 + > From: "Michael J. Flickinger" > > Today the version control system environment was upgraded from debian lenny to > debian squeeze. Thanks. Can you tell if bzr was upgraded as part of this, and if so, what is its current version on Savannah?
Re: [Savannah-users] Bazaar upgraded
> Date: Sat, 09 Apr 2011 12:56:30 + > From: "Michael J. Flickinger" > > Bazaar has been upgraded from version 2.1.2 to 2.3.1. Thank you!
Re: [Savannah-users] Loggerhead for Bazaar
> Date: Sun, 10 Apr 2011 14:59:27 + > From: "Michael J. Flickinger" > > Savannah now supports Loggerhead for Bazaar again. > Projects using Bazaar are accessible via http://bzr.savannah.gnu.org/lh/. Thanks!
Re: [Savannah-users] deleting old (bzr) branches
> Date: Thu, 14 Apr 2011 12:32:32 +0930 > From: Karl Goetz > > is there a way to delete old branches? Sorry for asking the obvious, but did you try "bzr rmbranch"?
Re: [Savannah-users] deleting old (bzr) branches
> Date: Sun, 17 Apr 2011 10:58:40 +0930 > From: Karl Goetz > Cc: savannah-users@gnu.org > > > Sorry for asking the obvious, but did you try "bzr rmbranch"? > > No problem. I hadn't tried that, but with good reason: its not in the > version of bzr i normally use. I've tried a checkout of trunk, and it > appears to have that functionality. This command was added to Bazaar in version 2.2.0 (the current stable release is 2.3.1). > I've tried deleting a few branches (eg deploy-standard-server/), but > they are still listed at [1]. does this take a while to refresh? Looks like that (or maybe there's some bug or a need for cleanup on Savannah). Note that this branch no longer shows with its last revision, like live branches do. Also the "bzr branches" command (available as part of the bzrtools plugin) does not show this branch in the list it produces. So I think the deletion did work, for all practical purposes.
[Savannah-users] Problems with SSH connections to Savannah?
Did something happen with SSH connections to Savannah? I've got this error message trying to update from Emacs bzr repository: Exception: Error reading SSH protocol banner Traceback (most recent call last): File "paramiko\transport.pyo", line 1516, in run File "paramiko\transport.pyo", line 1633, in _check_banner SSHException: Error reading SSH protocol banner bzr: ERROR: Unable to connect to target of bound branch BzrBranch7(file:///D:/gnu/bzr/emacs/trunk/) => bzr+ssh://e...@bzr.savannah.gnu.org/emacs/trunk/: Unable to connect to SSH host bzr.savannah.gnu.org; Error reading SSH protocol banner Meanwhile, "git pull" from the Make repository stalls. Help? TIA
Re: [Savannah-users] Problems with SSH connections to Savannah?
> Date: Tue, 14 May 2013 16:49:01 +0300 > From: Eli Zaretskii > > Did something happen with SSH connections to Savannah? I've got this > error message trying to update from Emacs bzr repository: > > Exception: Error reading SSH protocol banner > Traceback (most recent call last): > File "paramiko\transport.pyo", line 1516, in run > File "paramiko\transport.pyo", line 1633, in _check_banner > SSHException: Error reading SSH protocol banner > > bzr: ERROR: Unable to connect to target of bound branch > BzrBranch7(file:///D:/gnu/bzr/emacs/trunk/) => > bzr+ssh://e...@bzr.savannah.gnu.org/emacs/trunk/: Unable to connect to SSH > host bzr.savannah.gnu.org; Error reading SSH protocol banner > > Meanwhile, "git pull" from the Make repository stalls. > > Help? For some reason, this appeared on the list 7 hours after it was sent (was lists.gnu.org dormant between 9:50 and 16:13 EDT?). Whatever problem was that, it seems to have been solved since then. Thanks.
Re: [Savannah-users] Problems with SSH connections to Savannah?
> Date: Tue, 14 May 2013 14:26:01 -0600 > From: Bob Proulx > > Can you try from a different system, say, fencepost? I tried back then, with git only: it stalled on fencepost as well for many seconds. You should be able to see that in the logs. > I think there might be a problem between you and vcs.sv. No problems at all, since the slowdown disappeared. I get my normal speed, in both bzr and git.
Re: [Savannah-users] Problems with SSH connections to Savannah?
> Date: Tue, 14 May 2013 14:26:01 -0600 > From: Bob Proulx > > $ grep eliz /var/log/auth.log | tail -n8 > May 14 14:09:46 vcs sshd[10524]: Accepted publickey for eliz from > 87.69.4.28 port 2490 ssh2 > May 14 14:09:47 vcs sshd[10524]: pam_unix(sshd:session): session opened for > user eliz by (uid=0) > May 14 14:13:10 vcs sshd[6938]: pam_unix(sshd:session): session closed for > user eliz > May 14 14:26:28 vcs sshd[10524]: pam_unix(sshd:session): session closed for > user eliz > May 14 19:59:55 vcs sshd[2531]: Accepted publickey for eliz from 87.69.4.28 > port 3637 ssh2 > May 14 19:59:55 vcs sshd[2531]: pam_unix(sshd:session): session opened for > user eliz by (uid=0) > May 14 20:00:44 vcs sshd[3466]: Accepted publickey for eliz from 87.69.4.28 > port 3643 ssh2 > May 14 20:00:45 vcs sshd[3466]: pam_unix(sshd:session): session opened for > user eliz by (uid=0) That bzr error happened at 16:46:08 +0300 (thank you, ~/.bzr.log!). The above times are much later, when the problem already disappeared as mysteriously as it appeared. For bzr, the message I cited shows some diagnostics. For git, I don't know what happened, only that "git pull" will stall without showing any output for many seconds, even minutes. That was around the same time as shown above for bzr, so please look in the logs around there. Thanks.
[Savannah-users] Cannot access the Texinfo SVN repository
After a long time interval without updating my SVN sandbox of Texinfo, I tried to update, but bumped into a problem: D:\gnu\svn\texinfo\trunk>svn update Updating '.': svn: E720002: Unable to connect to a repository at URL 'svn+ssh://e...@svn.savannah.gnu.org/texinfo/trunk' svn: E720002: Can't create tunnel: The system cannot find the file specified. This is on Windows, but it used to work. I did try to SSH into svn.savannah.gnu.org, and it did work. What am I doing wrong? (Sorry, I almost never use SVN, so perhaps I use an incorrect command? But I did try the exact "svn co" command shown on the Savannah project page, with the same result: error message.) Thanks in advance for any help, and sorry for my confusion.
Re: [Savannah-users] Cannot access the Texinfo SVN repository
> Date: Tue, 23 Dec 2014 21:26:55 +0200 > From: Eli Zaretskii > > After a long time interval without updating my SVN sandbox of Texinfo, > I tried to update, but bumped into a problem: > > D:\gnu\svn\texinfo\trunk>svn update > Updating '.': > svn: E720002: Unable to connect to a repository at URL > 'svn+ssh://e...@svn.savannah.gnu.org/texinfo/trunk' > svn: E720002: Can't create tunnel: The system cannot find the file > specified. > > This is on Windows, but it used to work. I did try to SSH into > svn.savannah.gnu.org, and it did work. Please ignore me: the problem was that SVN_SSH must point to an ssh program using Unix-style forward slashes, not backslashes. Sorry for the noise.
Re: [Savannah-users] Cannot access the Texinfo SVN repository
> Date: Tue, 23 Dec 2014 14:54:10 -0500 > From: Assaf Gordon > > On 12/23/2014 02:26 PM, Eli Zaretskii wrote: > >svn: E720002: Unable to connect to a repository at URL > > 'svn+ssh://e...@svn.savannah.gnu.org/texinfo/trunk' > >svn: E720002: Can't create tunnel: The system cannot find the file > > specified. > > > > This is on Windows, but it used to work. I did try to SSH into > > svn.savannah.gnu.org, and it did work. > > I'm not well versed with SVN either, but I found these two mentions of the > same error on windows, > hinting that it could be a problem in SVN not finding the SSH program: > > http://kiranpatils.wordpress.com/2009/08/13/svn-cant-create-tunnel-the-system-cannot-find-the-path-specified/ > https://subversion.open.collab.net/ds/viewMessage.do?dsForumId=4&dsMessageId=148269 Yes, that was the reason. What puzzled me was that SVN_SSH was set in my case, and it pointed to the correct place. The problem, as I found out, was that SVN on Windows needs the value of SVN_SSH to use Unix-style forward slashes. (By contrast, Git wants backslashes. Go figure.) Thanks for your help.
Re: Testing if this message reaches the savannah-users
> From: Vaidas BoQsc > Date: Sat, 26 Jun 2021 10:42:39 +0300 > Cc: savannah-users@gnu.org > > from:BoQsc > to:"savannah-users@gnu.org" > date:Jun 22, 2021, 10:30 AM > subject:I'm curious about how mailing lists work > mailed-by:gmail.com > > > The above is all I know. Go to your "Sent" folder of Gmail, and find the message you think did not make it to the list. Click on that message, and you should see the 3 vertical dots at the right margin. Click those 3 dots and select "Download message". In the file that is downloaded you will see "Message-ID", "date", and other headers -- this is what Ian asks for.
Re: Email notifications from bug tracker
> Date: Tue, 17 May 2022 00:33:10 -0600 > From: Bob Proulx > > > I will get Postfix configured for user address mapping, DKIM > > signatures, transport, and delivery. That will fix the future sending > > of messages from the web UI which includes bug tickets, password > > recovery, and other administrative uses. I don't think past failed > > messages can be re-sent in any meaningful way however. > > I believe I have the system configured for email now. This means that > messages generated from the web UI from now forward should be okay. > They will have the correct From address and will be supported with > DKIM and such. > > Previous messages that have already failed will be unlikely to be > possible to regenerate them correctly. Maybe. I will look at it > tomorrow. But I think it unlikely. There were massive problems on the info-gnu-emacs mailing list yesterday. I wrote to mail...@gnu.org about that, but didn't yet receive any replies.
Re: DNS issue affecting gnu.org (and subdomains)
> Date: Sat, 25 Mar 2023 23:38:29 +0600 > Cc: savannah-users@gnu.org > From: Ar Rakin > > Hello Sebastian, > > I'm also unable to access gnu.org. I don't exactly know why this is > happening, though I've encountered this type of issues before, with my > own domains. But it got fixed automatically after a few days. Hopefully, > it will be fixed automatically after some time. > > What I can see: > > $ host gnu.org > ;; connection timed out; no servers could be reached > > $ ping gnu.org > ping: gnu.org: Temporary failure in name resolution You will find the information here: https://hostux.social/@fsfstatus That place is always good to look at when such issues occur.
[Savannah-users] Re: [Savannah-announce] Replacing FTP queue with SFTP?
> Date: Thu, 2 Nov 2006 23:50:54 +0100 > From: Sylvain Beucler <[EMAIL PROTECTED]> > > We're considering providing SFTP access to the download > area. It will be troublesome to keep both the old FTP queue > system and SFTP at the same time though. > > Would it be OK to disable the FTP queue and replace it with SFTP? I'm not sure I understand what would be affected by this change, and thus cannot make up my mind about the issue. Could you perhaps say a few words about when the download area is used and for what purposes? TIA ___ Savannah-users mailing list Savannah-users@gnu.org http://lists.gnu.org/mailman/listinfo/savannah-users
[Savannah-users] Re: Replacing FTP queue with SFTP?
> Date: Fri, 3 Nov 2006 14:46:43 +0100 > From: Sylvain Beucler <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], > [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] > > Here are some answers :) Thanks. This answers my questions. I think that switching to SFTP would be a good idea, since that makes it easier, at least for me, to upload files. ___ Savannah-users mailing list Savannah-users@gnu.org http://lists.gnu.org/mailman/listinfo/savannah-users
Re: git server upgraded
> Date: Fri, 20 Sep 2024 14:57:56 -0600 > From: Bob Proulx > > Savannah Users, > > TL;DR: git server upgraded, please report any problems Here is one: when pushing to the Emacs Git repository, I see: $ git push Counting objects: 4, done. Compressing objects: 100% (4/4), done. Writing objects: 100% (4/4), 455 bytes | 0 bytes/s, done. Total 4 (delta 3), reused 0 (delta 0) remote: /usr/bin/env: 'python2': No such file or directory <<< To git.savannah.gnu.org:/srv/git/emacs.git 0834106..a6dafbc emacs-30 -> emacs-30 Thanks.
Re: git repositories no longer available
> Date: Tue, 01 Oct 2024 16:56:22 +0200 > From: Stephen Kitt > > It’s not clear to me what the current git server upgrade situation is, > but https://git.savannah.gnu.org/cgit/bash.git, > https://git.savannah.gnu.org/cgit/make.git etc. say “No repositories > found”, git.savannah.gnu.org is refusing connections, and > https://git.savannah.gnu.org/git/make.git etc. return 404s. It was so for a short period of time, but now I don't see any problems, at least not with the Emacs Git repository.
Re: git repositories no longer available
> From: Corwin Brust > Date: Tue, 1 Oct 2024 11:27:35 -0500 > Cc: savannah-users@gnu.org > > On Tue, Oct 1, 2024 at 11:10 AM Stephen Kitt wrote: > > > > > > It was so for a short period of time, but now I don't see any > > > problems, at least not with the Emacs Git repository. > > > > Indeed, it’s working for me too now. > > > > There was an outage affecting all FSF hosted infrastructure for about > the last twelve hours, ending around an hour back. Things should be > stable or stabilizing now. (There is still some checking and > restarting of things on the Savannah side as of this minute.) Sadly, these outages happen lately almost every day. It make our work as GNU maintainers harder than it has to be. I really hope this will get better soon. > This is the spot to check for announcements when FSF sysops cannot use > it's own email and other services to let us know what's up: > > https://hostux.social/@fsfstatus Sadly, when these problems happen, there's usually nothing pertinent on that site. The information about connectivity problems appears there hours after the problems start.
Re: cannot stat /var/lock/cvs/web/www: No such file or directory
> Date: Wed, 20 Nov 2024 06:16:52 +0100 > From: Dora Scilipoti > > Hello, > > cvs updating my working directory www doesn't seem to be working for me > since yesterday: > > ~/www$ cvs update > cvs update: Updating . > cvs [update aborted]: cannot stat /var/lock/cvs/web/www: No such file or > directory Works here, FWIW.
