[Savannah-hackers-public] Testing new Savannah website infrastructure

The Savannah web site is testing on the new infrastructure again today. Please be on the lookout for any problems. Please report any issues you find with it. Thanks! The Savannah Hackers Team

[savannah-help-public] [sr #109247] Username, Password, and Email

Follow-up Comment #1, sr #109247 (project administration): The email address associated with your account is at redcom.com and not dgtlrift.com. Does that help? ___ Reply to this item at:

[savannah-help-public] [sr #109247] Username, Password, and Email

Follow-up Comment #2, sr #109247 (project administration): Re-sending because I forgot to CC the originator email. The email address associated with your account is at redcom.com and not dgtlrift.com. Does that help? ___ Reply to this

Re: [Savannah-hackers-public] perl warning from cvs.sv.gnu.org

Hello Andreas, Andreas Schwab wrote: > When I try to run cvs server on cvs.sv.gnu.org I get a warning from > perl: Thank you for the report. I can recreate this using client side commands by using this in a project directory: LANG=de_DE.UTF-8 cvs -qn up > $ ssh cvs.sv.gnu.org cvs server >

Re: [Savannah-hackers-public] git status update

Leo Famulari wrote: > remote: Traceback (most recent call last): > remote: File "hooks/post-receive", line 6, in > remote: import git_multimail > remote: ImportError: No module named git_multimail Thank you for that report. This is the git-multimail hook. There are several different

Re: [Savannah-hackers-public] git over https

Bob Proulx wrote: > This isn't the final configuration though since this uses the package > installed git, which should be fine but doesn't support shallow clones > with --depth 1 yet as of the OS Trisquel 7 release with git 1.9.1. > Therefore we are using git from a Debian Jessie S

Re: [Savannah-hackers-public] git over https

Leo Famulari wrote: > Bob Proulx wrote: > > Drat! This does appear to be a regression. > > > > In your opinion is that enough of a regression to warrent reverting > > (once again) the git service back to the old server? Of course that > > means another IP add

[savannah-help-public] [sr #108874] lwip-contrib git repository not linked on project pages

Follow-up Comment #6, sr #108874 (project administration): I still don't understand. When I look at the "Browse Sources Repository" page I see that it lists the lwip-contrib too. It also says "Note: this group has multiple Git repositories." right at the top. Looks like it is listing multiple

[Savannah-hackers-public] Chef client hitting emacs cgit eterm-color?

Anyone know why "Chef Client" is repeatedly hitting this? (I know that Chef is a Puppet like tool.) http://git.savannah.gnu.org/cgit/emacs.git/plain/etc/e/eterm-color I have been staring at the activity and for some reason I am seeing a lot of "Chef Client" accessing two particular emacs cgit

Re: [Savannah-hackers-public] git status update

Bob Proulx wrote: > But the cgit web server was returning a proxy error. In order to > avoid needing to debug that on the spot I proxied it over to the old > server temporarily. That is running okay this way for the moment. > Can debug the local native server at our leisure. Tha

[savannah-help-public] [sr #108874] lwip-contrib git repository not linked on project pages

Follow-up Comment #10, sr #108874 (project administration): Oh! Now I understand. Sorry. I was missing the obvious. It wasn't the source code access sections but links to the cgit source code browser sections. I think you were being clear enough in your descriptions. I just wasn't understanding

[savannah-help-public] [sr #108874] lwip-contrib git repository not linked on project pages

Follow-up Comment #8, sr #108874 (project administration): Start at the Savannah project page: https://savannah.nongnu.org/projects/lwip Select the [Source code] link from the navigation menu. https://savannah.nongnu.org/projects/lwip/#devtools Select [Source Code Manager: Git Repository]

[savannah-help-public] [sr #109246] Can't upload signed releases with `scp' anymore, but `rsync' works instead?

Follow-up Comment #1, sr #109246 (project administration): Recently a security vulnerability was discovered and reported by Sylvain Beucler concerning this area of operation. The screened list of server side options has changed. That is the root cause of the problem you are experiencing now. The

[savannah-help-public] [sr #109210] I can't connect to my repository via ssh, but cvs can?

Follow-up Comment #4, sr #109210 (project administration): After seeing your other ticket 109246 I wanted to ask here what the status of this problem is for you. All okay now? My summary of your problem report is that users are allowed to run version control commands such as cvs commands (or svn

[savannah-help-public] [sr #109246] Can't upload signed releases with `scp' anymore, but `rsync' works instead?

Update of sr #109246 (project administration): Status:None => Done Assigned to:None => rwp ___ Reply to this item at:

Re: [Savannah-hackers-public] Savannah Test Project

Assaf Gordon wrote: > checks for the mercurial/hg part. That is excellent! That is exactly what is needed. Sorry for the delays in getting back to this. I made some small changes to the patch and pushed it to a "pu" proposed updates branch, along with other unrelated changes. If you agree I

Re: [savannah-help-public] [sr #109229] CNAME

Savannah Hackers, Daniel Pimentel wrote: > I have a domain called guga.io and I'd like to use guga.io as my group > guga.nongnu.org. I added a CNAME but redirect to savannah main site. I'd like > to add a A in my DNS or CNAME. I have no idea how or if this is supported. Does anyone else? Is

[savannah-help-public] [sr #109237] Can't install dicom package (0.1.1 and 0.1.2 (user version)) in octave 4.0.2 and ubuntu 14.0

Follow-up Comment #1, sr #109237 (project administration): Hi! You have posted a bug to the Savane administration tracker. But you are posting about Octave. I am sorry but this is the wrong project. I will try to reassign the ticket. ___

[savannah-help-public] [sr #109237] Reassigned to another tracker [was: Can't install dicom package (0.1.1 and 0.1.2 (user version)) in octave 4.0.2 and ubuntu 14.0]

Follow-up Comment #3, sr #109237 (project administration): It turns out that we can't reassign the ticket because the GNU Octave project does not use the ticket tracker for bugs. Therefore there is no place for it to go. Sorry. You will need to contact the Octave project and submit the ticket

[savannah-help-public] [sr #108871] Gnash project's git mail notification is giving out wrong repository URL

Update of sr #108871 (project administration): Status:None => In Progress Assigned to:None => rwp ___ Follow-up Comment #3: Oh wow.

[savannah-help-public] [sr #109241] test ticket to test submission and email

Update of sr #109241 (project administration): Open/Closed:Open => Closed ___ Follow-up Comment #1: > Test ticket to test submission and email. Seems to be working. Closing.

[savannah-help-public] [sr #109236] Error while trying to clone the Emacs git repo (via http)

Update of sr #109236 (project administration): Status:None => Confirmed Assigned to:None => rwp ___ Follow-up Comment #1: Confirmed.

Re: [savannah-help-public] [sr #109229] CNAME

Karl Berry wrote: > http://guga.nongnu.org also works. I had not known such a thing was possible. Thanks! > There is no provision for package administrator's modification of DNS > (and I don't think there should be). I was confused by the original poster's request about that. It didn't make

[savannah-help-public] [sr #109229] CNAME

Update of sr #109229 (project administration): Assigned to:None => rwp Open/Closed:Open => Closed ___ Follow-up Comment #1: I am sorry

[savannah-help-public] [sr #108124] Cannot View Other Branches In Loggerhead

Update of sr #108124 (project administration): Open/Closed:Open => Closed ___ Follow-up Comment #4: Last comment here was 2012 and this problem seems to have been resolved previously so

Re: [savannah-help-public] Downloading attachments: error: the file can't be found

Bernhard Voelker wrote: > When trying to download an attachment of a bug, e.g. one of the two > attachments of the findutils bug >https://savannah.gnu.org/bugs/?50259 > then the Savannah webpage returns the error message "The file can't > be found". Any hint? > >

Re: [Savannah-hackers-public] Old frontend apache web server

Bob Proulx wrote: > I am going to do a simple shutdown of the apache server on the old > system. That will prevent people accessing it and then any problems > such as that will be found. > > Should we instead put up a simple top level catchall page with a > return of 503? Th

Re: [savannah-help-public] Downloading attachments: error: the file can't be found

> Bingo! Wow, that was a strange effect - I uploaded that file myself > just a couple hours ago from another PC. Yay! I like easy to solve problems. :-) Just to stop future occurrences of this I just now switched the old server over to a generic "site moved" page returning 503. This should

Re: [savannah-help-public] Can you fix this for him?

Richard Stallman wrote: > Can you fix this for him, and ack to me? We will look into it. I peeked very quickly and I see no email from the web server to jo...@yellowcouch.org and therefore don't think there is any missing email. But we will make contact and figure this out. Bob > ---

[Savannah-hackers-public] Old frontend apache web server

I think the new web server is working out very well. I see no indicators that we would return to the previous one by this point in time. I think it is time to stop access to the old one in order to prevent confusion from people that are still hitting the old one. Looking at the access logs there

[savannah-help-public] [sr #109271] can't upload: no such file or directory

Follow-up Comment #3, sr #109271 (project administration): I am only going to say that while I can recreate the error the source of the problem is defeating me. As I look at the server configuration this looks like it should be working. But obviously it is not. So just logging this here as

[Savannah-hackers-public] Savannah VMs rebooted for latest security kernel

I have installed the latest security kernel and rebooted the VMs onto it. All of the services are operating normally. Initially I ran the test suite and the "download" tests all failed. The NFS mount had not happened at boot time. The problem was lack of an IP address for "olddownload" at boot

Re: [Savannah-hackers-public] download access for uploading files broken

> I have the solution! (i think). Yay! > This guy deserves a beer! > http://www.xkyle.com/solving-the-nfs-16-group-limit-problem/ He did do a good write-up. :-) > 1. Because we DO use "--manage-gids" in > download:/etc/default/nfs-kernel-server , > it means that rpc.mountd on download

Re: [Savannah-hackers-public] download access for uploading files broken

] root 24072 12446 0 05:33 pts/100:00:00 grep nfs root@download:/# Verify that the libnss-mysql is working. Assaf already was here to make sure it was working in the baton pass. root@download:~# getent passwd rwp rwp:x:65821:1003:Bob Proulx:/srv:/usr/local/bin/sv_membersh Start

[Savannah-hackers-public] download access for uploading files broken

Joël Krähemann reported today to savannah-users that sftp upload was not working. Of course this was disabled Nov-2016 due to security concerns. I stated that scp and rsync were supported and recommended using rsync. Unfortunately I didn't test it before sending out that message. Seeing Matt

Re: [Savannah-hackers-public] download access for uploading files broken

> Where do groups come from? > MySQL on internal0 ! which was just rebooted! > > Then, checking download:/var/log/daemon.log shows clearly: > === > Feb 24 03:03:25 download mountd[4812]: libnss-mysql: Connection to server > '208.118.235.75' failed: Lost connection to MySQL server at 'reading

Re: [Savannah-hackers-public] download access for uploading files broken

> I am still leaning toward a problem with locks over nfs as to why the > rsync isn't working. But not sure yet. But that does not appear to be it. I wrote a small test program to acquire locks over the nfs mount and that seems to be working perfectly. Therefore I not know why rsync is not

Re: [Savannah-hackers-public] [savannah-reports-private-boun...@gnu.org: Forward of moderated message]

Hi Karl, Karl Berry wrote: > Bob/Assaf - these monit reports were sent to "root@localhost" and > therefore were held for moderation in mailman. I didn't want to add that > address to any mailman field because it's invalid; mailman will let you > add it but then (annoyingly/wrongly/uselessly)

Re: [Savannah-hackers-public] download access for uploading files broken

Hi Assaf, Assaf Gordon wrote: > Thanks for fixing the NFS last night! (glad we found the solution). Yay! So nice to understand the database - DNS interaction change that snagged us upon the reboot. :-) > Bob Proulx wrote: > > But that does not appear to be it. I wrote a small

[savannah-help-public] [sr #109263] replace master branch

Follow-up Comment #3, sr #109263 (project administration): You have put the Savannah admins into a difficult situation. Our task is to curate the source code. To keep it safe from data corruption and catastrophe. To keep it accessible to the community. To worry about security. We have literally

Re: [savannah-help-public] Fwd: git.sv.gnu.org ssh host key

ayleph wrote: > I have the following entry from my known_hosts file, and I connected as > recently as January 16th with no warning message. > > git.sv.gnu.org,208.118.235.72 ssh-rsa >

[savannah-help-public] [sr #109257] cgit sometimes serves a stale page for five minutes

Update of sr #109257 (project administration): Status:None => Wont Do Assigned to:None => rwp ___ Follow-up Comment #1: I think

Re: [Savannah-hackers-public] Downstream questions about Savannah and HTTPS

Leo Famulari wrote: > If anyone from Savannah has anything to add to the discussion, feel free > to jump in :) Thanks for the invite. I will jump in. :-) Bob

Re: [savannah-help-public] Fwd: git.sv.gnu.org ssh host key

Hello ayleph, ayleph wrote: > I'm not sure if I sent the below report to the correct place originally, Yes this is the correct place to ask for help about Savannah. And also the savannah-users mailing list was a good place too. I was surprised that none of the users responded to you there. I

Re: [Savannah-hackers-public] Testing new Savannah website infrastructure

> > I sync'd the file attachments from the old to the new. [...] > > > > frontend:/var/lib/savane/trackers_attachments# rsync -av > > /var/lib/savane/trackers_attachments/ > > frontend0:/var/lib/savane/trackers_attachments/ > > If it helps, > I have a script to do this (and also copy the "new

Re: [Savannah-hackers-public] vcs0 cgi errors ("502 bad gateway")

Hi Assaf, Assaf Gordon wrote: >2017/02/10 10:58:20 [error] 3647#0: *370418 connect() to > unix:/var/run/fcgiwrap.socket failed (11: Resource temporarily unavailable) > while connecting to upstream, client: X.X.X.X, server: git.savannah.gnu.org, > request: "GET

[Savannah-hackers-public] cvs: timeout: fork system call failed: Resource temporarily unavailable

Today Andrew grabbed me on IRC with complaints from cvs checkouts: timeout: fork system call failed: Resource temporarily unavailable This was intermittent throughout the day. I was able to catch some of them myself when doing test checkouts repeatedly. Nagios noted the service flapping

Re: [Savannah-hackers-public] bzr post-commit email hook

Glenn Morris wrote: > PS I would also copy /etc/logrotate.d/bzr across. Yes. Looks like bzr is logging to /var/lib/bzr/bzr-anon.log. Which I think should be /var/log/bzr/bzr-anon.log instead. I am going to make that change. Will copy the logrotate over for the new location. > Other relevant

Re: [Savannah-hackers-public] bzr post-commit email hook

Glenn Morris wrote: > ChangeLog tells me to update the log on mgt0 instead, but I cannot > log in to mgt0. I just made a big edit, import, cleanup to the authorized keys file. Try it again now. I it should allow you in. You should be able to log in from fencepost to mgt0 now. In other

Re: [Savannah-hackers-public] bzr post-commit email hook

Glenn Morris wrote: > Bob Proulx wrote: > > Yes. Looks like bzr is logging to /var/lib/bzr/bzr-anon.log. Which I > > think should be /var/log/bzr/bzr-anon.log instead. I am going to make > > that change. Will copy the logrotate over for the new location. > >

Re: [Savannah-hackers-public] Savannah Test Project

Hello Assaf, Assaf Gordon wrote: > Hello Bob and all, > > I've pushed the following additions to > the savannah-tests project: Very good! :-) Bob

Re: [Savannah-hackers-public] bzr post-commit email hook

Glenn Morris wrote: > Bob Proulx wrote: > > I just made a big edit, import, cleanup to the authorized keys file. > > Try it again now. I it should allow you in. You should be able to > > log in from fencepost to mgt0 now. > > Thanks. If security is a concern you sho

[Savannah-hackers-public] New VMs status update - 2016-08-15

Savannah Hackers, Quick update on the new VMs. Host mgt0: Done and ready to go. I am using it as the lilypad machine and administration host for accessing the other systems. Host internal0: I think this one is done and ready to go. Although it hasn't been transitioned to yet. It needs ones

Re: [Savannah-hackers-public] SavannahHosts r212

Karl Berry wrote: > Bob writes: > +* Are people using download for a pserver? There are notes to that > + effect in the download /etc/default/iptables-rules file. > > locate /CVS/ on download tells me there is a CVS repository for > audio-video (nothing else). Whether it is still used,

Re: [Savannah-hackers-public] Savannah project ada-mode

h...@sdf.org wrote: > > Hugh Mayfield writes: > > The mailing list 'ada-mode-users' does not seem to be working properly. > > Stephe: thank you for your email. Unfortunately I don't have the > experience to know the answer to these. I thought it would be best to ask > the list so that you can

[savannah-help-public] [sr #109129] My access to the GPSD repository is broken

Update of sr #109129 (project administration): Status:None => Need Info Assigned to:None => rwp ___ Follow-up Comment #1: Your error

[savannah-help-public] [sr #109129] My access to the GPSD repository is broken

Follow-up Comment #4, sr #109129 (project administration): I did a quick look and I see this that may be associated with your login. The log doesn't really associate these things enough to be sure. userauth_pubkey: unsupported public key algorithm: ssh-ed25519 Remember that the current VMs are

[savannah-help-public] [sr #109129] My access to the GPSD repository is broken

Follow-up Comment #3, sr #109129 (project administration): Do DSA keys work? Sorry. No time to investigate myself at the moment. But see this reference. http://savannah.gnu.org/maintenance/SshAccess/ Please try using an RSA key. It is what you want to be using regardless.

[savannah-help-public] [sr #109126] Password Recovery "Missing Parameters"

Update of sr #109126 (project administration): Status:None => Need Info Assigned to:None => rwp ___ Follow-up Comment #1: Hi. The

Re: [Savannah-hackers-public] mismatching licenses in list on Savannah (hashes.txt)

Assaf Gordon wrote: > My understanding is this: > > The file used in the real website is > frontend:/etc/savane/content/gnu-content/hashes.txt > That is, if that file changes, the list of license shown on the website will > change. I think so too. The live files are in /etc/savane. > The

Re: [Savannah-hackers-public] temporary non fast forward git push needed

Hi Leah, Leah Rowe wrote: > The current patch on libreboot.git in savannah for GNU Libreboot needs > reverting, I need you to temporarily enable non-fast-forward pushing so > I can remove it from the master repo. > > I refer to >

Re: [Savannah-hackers-public] temporary non fast forward git push needed

Hi Leah, Leah Rowe wrote: > Yes, normally I'd just revert but that's a big-ass uncompressed pic I > pushed. Yes. I saw that! It was as we might say here, a big honker! Which was a big reason I had sympathy for getting it fixed. :-) Things like this are what we are here for. Please let us

[savannah-help-public] [sr #109138] wget receives a TLS warning alert

Update of sr #109138 (project administration): Open/Closed:Open => Closed ___ Follow-up Comment #1: Since alpha.gnu.org isn't part of Savannah there isn't anything us Savannah folks can do

Re: [Savannah-hackers-public] New VMs status update (menu.txt fix)

Assaf Gordon wrote: > menu.txt is parsed as php code, and was using the short-hand " " frontend0's php5 is configured to ignore those: >... > For now I changed the menu.txt instead of changing php5's configuration. I think that is a good idea. PHP short tags have been deprecated for a very long

[savannah-help-public] [sr #109161] gcl repository has permission problems (unpacker error)

Follow-up Comment #2, sr #109161 (project administration): See this http://savannah.gnu.org/maintenance/UsingGit/ and look for "Fixing checkout from git:// to ssh://" ___ Reply to this item at:

[savannah-help-public] [sr #109161] gcl repository has permission problems (unpacker error)

Update of sr #109161 (project administration): Assigned to:None => rwp Open/Closed:Open => Closed ___ Follow-up Comment #1: Hello Camm,

[savannah-help-public] [sr #109160] fusebits changing error

Update of sr #109160 (project administration): Status:None => Invalid Open/Closed:Open => Closed ___ Follow-up Comment #1: Hello. You

Re: [savannah-help-public] [sr #109144] Change project name

Karl Berry wrote: > > > > To me, "lig" means ligatures. A three-character name could mean > basically anything. As you know, I am not a fan of such short names > being "usurped" by relatively new or little-known/used projects. > > But I will not

Re: [savannah-help-public] [sr #109144] Change project name

Hi Assaf, Daniel Pimentel wrote: > > Summary: Change project name I see and read the documentation for this here: http://savannah.gnu.org/maintenance/RenamingProjectGroup/ You are the expert on this. What do you think? Thanks!

[savannah-help-public] [sr #109142] Super and Hyper key don'k work is some branches

Update of sr #109142 (project administration): Open/Closed:Open => Closed ___ Follow-up Comment #1: You have posted a bug to the Savannah administration project. But the bug you have

[savannah-help-public] [sr #109142] Super and Hyper key don'k work is some branches

Follow-up Comment #2, sr #109142 (project administration): I should also have mentioned that the best bug reporting interface for emacs is M-x report-emacs-bug inside of emacs. So I will mention it now. ___ Reply to this item at:

Re: [savannah-help-public] http://bzr.savannah.gnu.org/lh/gsrc 503

carl hansen wrote: > Service Temporarily Unavailable > > The server is temporarily unable to service your request due to maintenance > downtime or capacity problems. Please try again later. > -- > Apache/2.2.16 (Debian) Server at bzr.savannah.gnu.org Port 80 Hmm... I

Re: [Savannah-hackers-public] commit mail coming from @vcs.

Hi Karl, Karl Berry wrote: > Bob - it seems commit mail has started coming from @vcs.savannah.gnu.org > in some cases. Maybe it is user specific. For example, see message > below; mail from "dvc" (David Craven), and I also noted "nckx", is @vcs, > but not others. Good catch. I have been

[savannah-help-public] [sr #109156] Graceful request for updating path-set.git/description

Update of sr #109156 (project administration): Status:None => Done Open/Closed:Open => Closed ___ Follow-up Comment #1: Done! Thank

[Savannah-hackers-public] [task #14171] Snmp agents usage by LwIp

Update of task #14171 (project administration): Open/Closed:Open => Closed ___ Follow-up Comment #1: Hello. You have submitted a bug against the Savannah source forge. However your bug is

[Savannah-hackers-public] Network Problem? DDoS? System? 2016-10-29

Hi Ruben, It appears that Savannah is experiencing some type of network connectivity problem. Users have reported timeouts trying to access vcs. I can confirm the timeouts seen here too. Plus Nagios is latched in failure. The Savannah web frontend seems okay. Things appear to be a problem

Re: [Savannah-hackers-public] Network Problem? DDoS? System? 2016-10-29

Savannah Hackers, Ruben saw that the problem was a web crawler that is crawling fast but not closing connections effectively becoming a SYN attack. It also hit www.gnu.org yesterday. Therefore he blocked it site wide since it would just move on to yet another web server after this. I have been

Re: [Savannah-hackers-public] [gnu.org #1162706] Website DOWN

Therese Godefroy via RT wrote: > > planet.gnu.org (and its RSS feeds) are down and have been unreachable > > for weeks or months. Is PlanetGNU no longer maintained? > > Does anyone know what happened to this website? This is the fourth bug > report of this kind. Thanks for any clue. Not I. The

[savannah-help-public] [sr #108874] lwip-contrib git repository not linked on project pages

Update of sr #108874 (project administration): Assigned to:None => rwp ___ Follow-up Comment #2: In answer to your question asking if anyone is reading these bugs the answer is no. As

Re: [Savannah-hackers-public] SSH host keys for the new machine?

John Sullivan wrote: > Personally, I vote for option #3, because it will reduce the number of > variables in debugging the inevitable problems that will appear in the > transition. Thanks for commenting! (I will note that there was an additional private comment.) Not hearing any dissenting

[savannah-help-public] [sr #109164] Remove my registered account in Savannah with deprecated lavabit email since i lost my password

Update of sr #109164 (project administration): Status:None => Done Assigned to:None => rwp ___ Follow-up Comment #1: It is

[savannah-help-public] [sr #109115] Accidentally deleted an attachment

Follow-up Comment #2, sr #109115 (project administration): Assaf traced through the site code and found the location where attachments are saved. Yay! Thanks Assaf. :-) However it is our fault that this took too long to address. Now that we know where to look the file is no longer available

Re: [savannah-help-public] [sr #109115] Accidentally deleted an attachment

Bob Proulx wrote: > Paolo Redaelli wrote: > > I accidentally deleted attachment #37500 from a bug of our project Liberty > ... > > Assaf or Karl, do you know where attachments are stored? Is that in > the database or in the file system? I guess no one knows where a

[savannah-help-public] [sr #109165] Why aren't the mbox files protected and public available for everyone?

Update of sr #109165 (project administration): Open/Closed:Open => Closed ___ Follow-up Comment #1: The shortest answer is that those decisions were made years ago and no one from that era

[savannah-help-public] [sr #109164] Remove my registered account in Savannah with deprecated lavabit email since i lost my password

Update of sr #109164 (project administration): Open/Closed:Open => Closed ___ Reply to this item at:

[savannah-help-public] [sr #109166] questions about importing a new mailing list (moved from sourceforge.net)

Update of sr #109166 (project administration): Open/Closed:Open => Closed ___ Follow-up Comment #1: Thanks for chatting with us about importing the mailing list archive. I am not

Re: [Savannah-hackers-public] [Savannah-cvs] [266] MigrationChecklist: more tasks

Karl Berry wrote: > +* Check for special permissions for gnu webmasters? > > I don't know for a fact if it is still the case, but it is true that at > least at one time anyone in the www group could commit to any type=gnu > web repository (CVS). This was useful. -k Yes. I believe that is

[savannah-help-public] [sr #109172] Haven't received new user confirmation yet

Follow-up Comment #1, sr #109172 (project administration): Mail was sent to your Oct 22 20:36:16 frontend postfix/smtp[26858]: 57E9885DFA: to=, relay=mta5.am0.yahoodns.net[66.196.118.240]:25, delay=1, delays=0.06/0.01/0.06/0.91, dsn=2.0.0, status=sent (250 ok dirdel)

[savannah-help-public] [sr #109172] Haven't received new user confirmation yet

Update of sr #109172 (project administration): Open/Closed:Open => Closed ___ Follow-up Comment #3: > OK, got it. I had gone to "Spam" > Can't blame the spamming detector, given the title

[savannah-help-public] [sr #109172] Haven't received new user confirmation yet

Update of sr #109172 (project administration): Assigned to:None => rwp ___ Follow-up Comment #2: Sorry for the incomplete post. I will try again. Mail was sent to your address. As

Re: [Savannah-hackers-public] Serving Git over HTTPS

Hello Leo, Leo Famulari wrote: > Greetings throughout the sunny Savannah! :-) > I wonder, is it technically feasible to serve > over HTTPS? > > That would give anonymous users privacy and some measure of authenticity > when fetching the source code of hosted

[savannah-help-public] [sr #108639] Delete linux-doc-hr

Update of sr #108639 (project administration): Status:None => Done Open/Closed:Open => Closed ___ Follow-up Comment #4: Sounds

[savannah-help-public] [sr #108874] lwip-contrib git repository not linked on project pages

Follow-up Comment #5, sr #108874 (project administration): Note that if you go to the top level web page of cgit or gitweb you get an index of repositories: (be patient as the full listing is a slow operation) http://git.savannah.gnu.org/cgit/ You can scroll down through the list and see both

[savannah-help-public] [sr #109115] Accidentally deleted an attachment

Update of sr #109115 (project administration): Open/Closed:Open => Closed ___ Follow-up Comment #3: Unfortunately I don't think anything can be done to recover this file. I hate to have

[Savannah-hackers-public] SSH host keys for the new machine?

Savannah Hackers, The two systems vcs and download are routinely accessed by Savannah users over ssh. We are getting close to being able to switch over to the new vcs0 and download0 machines. Which brings this question of plan. Option 1: Do we use the previous 1024 bit SSH rsa host keys on the

[savannah-help-public] [sr #108639] Delete linux-doc-hr

Update of sr #108639 (project administration): Assigned to:None => rwp ___ Follow-up Comment #2: Hi. The simple answer is no there hasn't. Because there hasn't been any volunteers who

[savannah-help-public] [sr #109126] Password Recovery "Missing Parameters"

Update of sr #109126 (project administration): Open/Closed:Open => Closed ___ Follow-up Comment #2: It has been since 2016-08-30 and there has been no response. I assume this is because

[savannah-help-public] [sr #109115] Accidentally deleted an attachment

Update of sr #109115 (project administration): Assigned to:None => rwp ___ Follow-up Comment #1: Sorry for the long delay in responding. Volunteers with expertise here are in short

[savannah-help-public] [sr #109144] Change project name

Follow-up Comment #1, sr #109144 (project administration): Sorry for the long delay. Unfortunately project review volunteers are in short supply. There was some very small discussion about this request. No one liked the very short three letter project name because it was too short and implied

[savannah-help-public] [sr #109197] Savannah password not working before verification

Update of sr #109197 (project administration): Status:None => Need Info Assigned to:None => rwp ___ Follow-up Comment #1: Good that

<    2   3   4   5   6   7   8   9   10   11   >