[Savannah-help-public] please alias paxutils-announce and paxutils-forum to help-tar@gnu.org

I'm currently listed as being in charge of the mailing lists [EMAIL PROTECTED] and [EMAIL PROTECTED], but I don't know their administrative password. Currently these lists are mostly just spam. They are somewhat obsolete now, since the tar maintainer is currently working on paxutils. However,

[Savannah-help-public] savannah claims my account has expired, then refuses connection, then times out, ...

I'm having problems similar to what Bruce Korb reported earlier today http://savannah.gnu.org/support/?107654. I can't connect to Savannah with either git or bzr. Symptoms differ. For example: 1008-lnxsrv02 $ bzr up Your account has expired; please contact your system administrator Connection

[Savannah-help-public] [sr #107654] Developer GIT actually -- account expired????

Follow-up Comment #4, sr #107654 (project administration): https://savannah.gnu.org/forum/forum.php?forum_id=6772 says that PAM authentication isn't working, which would explain your problem. It should be fixed ASAP. ___ Reply to this item

[Savannah-help-public] [sr #107655] Unable to access CVS: Your account has expired; please contact your system administrator

Follow-up Comment #1, sr #107655 (project administration): This problem is a duplicate of https://savannah.gnu.org/support/index.php?107654. https://savannah.gnu.org/forum/forum.php?forum_id=6772 says that PAM authentication isn't working, which would explain your problem. It should be fixed

[Savannah-help-public] [sr #107694] Savannah git/bzr access down

URL: http://savannah.gnu.org/support/?107694 Summary: Savannah git/bzr access down Project: Savannah Administration Submitted by: eggert Submitted on: Mon 23 May 2011 05:58:08 PM PDT Category: Developer CVS

[Savannah-help-public] [sr #107714] Savannah git/bzr access down

URL: http://savannah.gnu.org/support/?107714 Summary: Savannah git/bzr access down Project: Savannah Administration Submitted by: eggert Submitted on: Thu 02 Jun 2011 09:44:02 AM PDT Category: Developer CVS

[Savannah-help-public] [sr #107714] Savannah git/bzr access down

Follow-up Comment #1, sr #107714 (project administration): Apparently the problem is fixed now, as the bzr server is now up. If someone fixed this, thanks! I'd like to close this support request but don't see anything in the Web UI to do that. For reference, here's the thread in emacs-devel

[Savannah-help-public] Savannah down again

Savannah is down hard again, and has been down for at least a couple of hours. Git and bzr access does not work, e.g.: $ git pull ssh: connect to host git.sv.gnu.org port 22: No route to host fatal: The remote end hung up unexpectedly $ cd ../emacs/trunk $ bzr up ssh: connect to host

[Savannah-help-public] [sr #107969] Can't authenticate to bzr.sv.gnu.org

Follow-up Comment #1, sr #107969 (project administration): I am observing a similar problem with git. Seems to be site-wide. ___ Reply to this item at: http://savannah.gnu.org/support/?107969

[Savannah-help-public] [sr #108096] Cannot browse Emacs source code via the web

URL: http://savannah.gnu.org/support/?108096 Summary: Cannot browse Emacs source code via the web Project: Savannah Administration Submitted by: eggert Submitted on: Thu 26 Jul 2012 01:24:56 AM PDT Category: Anonymous Web

[Savannah-help-public] [sr #108097] git history for grep is corrupted on the web

___ Details: If I visit: http://git.savannah.gnu.org/cgit/grep.git/log/ and click on the entry labeled: 2012-03-15 grep: -r no longer follows symlinks; use fts Paul Eggert 12 -380/+312 the link is: http://git.savannah.gnu.org/cgit/grep.git/commit/?id

[savannah-help-public] [sr #108097] git history for grep is corrupted on the web

Follow-up Comment #2, sr #108097 (project administration): I just now checked this link, and it's working now, so thanks for fixing it, and I suggest closing this bug report. (Why can't I close my own bug report? It'd save you some work)

[savannah-help-public] [sr #108214] anonymous git access failing -- savannah firewall problems?

URL: http://savannah.gnu.org/support/?108214 Summary: anonymous git access failing -- savannah firewall problems? Project: Savannah Administration Submitted by: eggert Submitted on: Sun 23 Dec 2012 09:04:18 AM PST

[savannah-help-public] [sr #108294] bzr access to Emacs source code is down

URL: http://savannah.gnu.org/support/?108294 Summary: bzr access to Emacs source code is down Project: Savannah Administration Submitted by: eggert Submitted on: Mon 29 Apr 2013 07:55:33 AM PDT Category: Developer Source

[savannah-help-public] [sr #108294] bzr access to Emacs source code is down

Follow-up Comment #1, sr #108294 (project administration): I should probably clarify: the diagnostic bzrlib is version 2.1.2 from /usr/lib/python2.6/dist-packages/bzrlib must be coming from Savannah. There's no such file on my client (Fedora 17 x86-64). There is a directory

[savannah-help-public] [sr #108294] bzr access to Emacs source code is down

Follow-up Comment #3, sr #108294 (project administration): Thanks, it's working for me now. ___ Reply to this item at: http://savannah.gnu.org/support/?108294 ___ Message sent via/by

[savannah-help-public] [sr #108451] GNU Emacs web repository embarrassingly slow

URL: http://savannah.gnu.org/support/?108451 Summary: GNU Emacs web repository embarrassingly slow Project: Savannah Administration Submitted by: eggert Submitted on: Wed 27 Nov 2013 04:06:56 PM PST Category: Anonymous

Re: [savannah-help-public] [sr #108451] GNU Emacs web repository embarrassingly slow

Dmitry Gutov wrote: Follow-up Comment #3, sr #108451 (project administration): They both responded pretty fast ( 5 sec). Same here. It's 5 sec for me now too. Thanks to whoever improved the performance.

[savannah-help-public] [sr #108451] GNU Emacs web repository embarrassingly slow

Follow-up Comment #5, sr #108451 (project administration): Yes, please close it. (Why can't I close my own bug reports?) ___ Reply to this item at: http://savannah.gnu.org/support/?108451

[Savannah-hackers-public] Re: bzr + savannah.gnu.org slow again

Following up on my previous message, my commit to the Emacs trunk took over 50 minutes (!). Here's the finished .bzr.log entry: Fri 2011-02-25 21:53:48 -0800 0.073 bazaar version: 2.2.2 0.073 bzr arguments: [u'commit', u'-m', u'Merge: lib-src changes mostly to avoid GCC warnings'] 0.096

[Savannah-hackers-public] bzr + savannah.gnu.org slow again

Savannah.gnu.org is very slow for bzr commits on the Emacs trunk, with symptoms much like they were about 24 hours ago. Perhaps the same thing is happening again? My most recent attempt to commit is taking more than 20 minutes. It's not done yet, so I don't know how long it will take exactly.

[Savannah-hackers-public] tar.git/plain/NEWS?id=release_1_27 does not work

This web page: http://git.savannah.gnu.org/cgit/tar.git/tree/NEWS?id=release_1_27 has a link to this: http://git.savannah.gnu.org/cgit/tar.git/plain/NEWS?id=release_1_27 The latter web page should exist, but doesn't. Is there something busted with git.savannah.gnu.org, or with GNU Tar, or

[savannah-help-public] link spammer Jenson frogbot on savannah

The account Jenson frogbot is being used to send link spam on Savannah; see: http://savannah.gnu.org/bugs/?39475#comment1 Can you please fix this? Thanks.

[savannah-help-public] weird posting of drug-paraphernalia material on Savannah

in data Date: Thu, 09 Jul 2015 20:29:42 + From: Winston Shellock invalid.nore...@gnu.org To: Paul Eggert egg...@cs.ucla.edu, Jonathan Hartley tart...@tartley.com, Winston Shellock joelthes...@gmail.com, ka...@ucw.cz, j...@meyering.net Additional Item Attachment, bug #35915 (project grep

[savannah-help-public] Savannah git down for Emacs repository

For example: $ git clone git://git.savannah.gnu.org/emacs.git Cloning into 'emacs'... fatal: Could not read from remote repository. And if I visit: http://git.savannah.gnu.org/cgit/emacs.git my browser hangs.

[savannah-help-public] savannah git is down or unusably slow

This morning I've been plagued with scenarios like this when trying to hack on gnulib: $ git pull Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. $ [wait for a while] $ git pull Already

Re: [savannah-help-public] can't push changes to gnulib on Savannah

On 03/25/2016 12:42 PM, Assaf Gordon wrote: Can you please try again? It's OK now, though the symptoms were weird. Before I got your email I saw this: $ git push Counting objects: 10, done. Delta compression using up to 4 threads. Compressing objects: 100% (10/10), done. Writing objects:

[savannah-help-public] can't push changes to gnulib on Savannah

I ran this from a Gnulib source directory on my machine (penguin.cs.ucla.edu): $ git push Counting objects: 10, done. Delta compression using up to 4 threads. Compressing objects: 100% (10/10), done. Writing objects: 100% (10/10), 2.54 KiB | 0 bytes/s, done. Total 10 (delta 8), reused 0 (delta

[savannah-help-public] GNU Emacs repository corrupted on savannah

This was just reported on emacs-devel here: http://lists.gnu.org/archive/html/emacs-devel/2016-05/msg00438.html Here are the symptoms I see: $ git clone git://git.sv.gnu.org/emacs.git Cloning into 'emacs'... remote: Counting objects: 763375, done. remote: Compressing objects: 100%

Re: [savannah-help-public] GNU Emacs repository corrupted on savannah

Bob Proulx wrote: The FSF admins have isolated and corrected the problem. The report is that the problem was a faulty SSD in a RAID10 set of four. It was returning corrupted data and reporting it as good data. That's exceptionally bad hardware. Ouch! What type of SSD it was, exactly? I

[savannah-help-public] savannah git access down (overloaded server?)

Here are some of the symptoms I'm observing now, from UCLA: $ git pull remote: Counting objects: 29, done. remote: fatal: unable to create thread: Resource temporarily unavailable error: git upload-pack: git-pack-objects died with error. fatal: git upload-pack: aborting due to possible

[savannah-help-public] git.sv.gnu.org flaky; pumprock.net connection refused

git.sv.gnu.org was flaky a few minutes ago. Sometimes it would work, and sometimes not; see transcript below. When I visit https://pumprock.net/fsfstatus for the out-of-band status report for Savannah status, I get "Connection refused". Has that the fsfstatus URL changed? It's still listed at

[savannah-help-public] [sr #109616] insufficient permission for pushing a git commit

Follow-up Comment #1, sr #109616 (project administration): I suggest bookmarking this URL: https://quitter.im/fsfstatus It currently says "7h ... www.gnu.org is going down for maintenance" which I take it means that they've been doing sysadmin work for seven hours and things are not fully

savannah down; quitter.im/fsfstatus also down

Currently I can't visit https://savannah.gnu.org (209.51.188.79), and the FSF status web page is also down. Savannah is not responding, and Firefox rejects the quitter.im URL, saying: An error occurred during a connection to quitter.im. SSL received a record that

Git pushes and pulls from savannah often hang

thing). For this repository, 'git config -l' reports: push.default=simple user.name=Paul Eggert user.email=egg...@cs.ucla.edu user.signingkey=7E3792A9D8ACF7D633BC1588ED97E90E62AA7E34 sendemail.smtpencryption=ssl sendemail.smtpserver=zimbra.cs.ucla.edu sendemail.smtpuser=eggert