Re: git repositories no longer available
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.) 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 You can also get slightly granular stats from this public facing page of performance information: https://git.savannah.gnu.org/
Re: cvs login
On Wed, Feb 28, 2024 at 7:56 PM Peter Frazier wrote: > > according to: > > https://savannah.gnu.org/cvs/?group=www > > ...there is an anonymous login for gnu.org cvs, but logging-in with the > anonymous handle fails. > > > "cvs -t -d :pserver:anonym...@cvs.savannah.gnu.org:sources/www co ccvs > login" > I am not sure about the "ccvs login" part especially- from your command, above. Can you explain in detail this command line and what it is doing? (Sorry, I've forgotten most of what I've ever known of csv). It seems meaningfully different from the suggested commands on the www CVS page you linked. I tried the below command (which I found on the page you linked) and that seemed to work fine, so I think anonymous access is working, at least to some degree: cvs -z3 -d:pserver:anonym...@cvs.savannah.gnu.org:/web/www co www
Re: urgent: request for removal from appearing in my mail-list.
On Thu, Nov 2, 2023 at 10:16 PM Jan Owoc wrote: > > By writing to a public mailing list to which anyone can subscribe to, > you've made your email address available to all subscribers. [SNIP] > > I know that some Savannah admins read this list, so maybe they could > (in their volunteer time) let you know whether it's possible to > manually edit the archives to remove the 4 emails you've sent. They > cannot reach out to the thousands of subscribers of this email list. > Greetings. I, for one, saw this note but have nothing to add. If we have a way to remove an email address after someone has replied to a public mailing list I haven't found instructions for that in our knowledge-base.
Re: Spam message when using CVS for webpages
On Wed, Oct 18, 2023 at 10:07 AM Gavin Smith wrote: > On Wed, Oct 18, 2023 at 09:56:17AM -0500, Corwin Brust wrote: > > Thanks for raising this issue. FWIW it has also been brought up by > > others. We are planning on discussing with FSF today, at the regular > > "volunteers" meeting, where most weeks svh and fsf sysop staff connect. > > > > We'll update you assuming this topic does get discussed and there is some > > conclusion to share (or when there is). > > > > Kind regards, > > Corwin > > That's good to hear! Thank you for your quick response. > Hi Gavin, I wanted to write back just to quickly confirm that this was discussed with FSF staff. Per my understanding, I believe others of the Savannah Hackers are planning to weigh in on this discussion as well. (If that happens in another thread/ticket I'll be sure to CC you if I spot you in the copy-trail.) I also plan to make another reply myself to clarify my own position (granted, as the newest member of the team), in brief: that this notification is above and beyond the plain requirements of hosting an AGPL program and should be either removed/rolled-back or else perhaps we could consider setting the QUIET flag en-mass. Meanwhile, as the team works to invite discussion and socialize a consensus, I think Ineiv has already provided instruction for turning this off within the Savannah web interface. Don't hesitate to reach out if you have any trouble with that or other thoughts you may have. Thanks again for writing. Corwin
Re: Spam message when using CVS for webpages
On Wed, Oct 18, 2023 at 9:46 AM Gavin Smith wrote: > I am trying to update a project's webpages after a new release, but > every time I issue a cvs command the message is printed: > > > sv_membersh is part of Savane. > > In order to download the corresponding source code of Savane, run > > > > rsync -avz --cvs-exclude ga...@cvs.savannah.nongnu.org:/opt/src/savane > . > > I don't know what sv_membersh or Savane is or why I should care. [SNIP] > > This message looks like an advert to me and isn't helpful. Thanks for raising this issue. FWIW it has also been brought up by others. We are planning on discussing with FSF today, at the regular "volunteers" meeting, where most weeks svh and fsf sysop staff connect. We'll update you assuming this topic does get discussed and there is some conclusion to share (or when there is). Kind regards, Corwin
Re: Login change
On Sun, Sep 17, 2023 at 11:51 AM Anton Shepelev wrote: > > Hello, all > Hi Anton! > > Can one (and I, for that matter) change one's login at savannah.org? > It is possible, however it requires an administrator to do and is somewhat involved for us to do. If you are interested, there's some background here: https://savannah.gnu.org/maintenance/RenamingAccounts/ Please do open a ticket if necessary: https://savannah.nongnu.org/task/?group=administration&func=additem Best, Corwin
Re: [Savannah-hackers-public] cgit syntax highlight request
On Fri, Apr 28, 2023 at 4:45 PM Ian Kelling wrote: > > > Bob Proulx writes: > > > [[PGP Signed Part:Undecided]] > > Savannah Users, > > > > A user on IRC (daviid) has requested that cgit on Savannah be modified > > to perform syntax highlighting by default on the various source page > > display pages. > > > > I did some research into this topic of cgit syntax highlighting. It Thanks for looking into it. > > seems there are two popular ways to enable syntax highlighting in > > cgit. One uses the Python "Pygments" and one uses the standalone > > "highlight" utility. > > > > On IRC there were various comments about pygments and previous > > security vulnerabilities it has been through. The other option using > > "highlight" I note is packaged for Debian and therefore if any > > security vulnerabilities were found that the security channel would > > normally provide a patch which would be quickly installed on our > > systems. Therefore in my opinion using "highlight" would be the best > > option. > > I agree. I actually got a patch into git for it's gitweb interface so > that it uses highlight as it's syntax highlighter. I think it used > pygments before, I can't remember for sure. Anyways, I did it because > highlight detected bash scripts and highlighted them, whereas the > previous highlighter did not. I also agree. > > > > > I tried it with both dark and light themes and it seems acceptable in > > either. Which is important to me personally as I almost always use a > > dark theme when possible. > > > > Personally I rather prefer the non-colorized display. Colors are one > > of those bike-shed items that everyone wants to be different. > > Therefore the common ground is often the no-color option. I much > > prefer if people clone to their own sandbox and then they can use > > their own preferences for all bike-shed things like colors and fonts. > > But this is a shared resource and everyone is using it as a commons > > area. I will bring the topic up for discussion. > > > > What is the opinion of the group at this time? Should we enable > > syntax color highlight in cgit by default? > > I'd prefer colorized output, but, first you should check the resource > use. When I made the git change, I found that highlight and pygments (i > think) had roughly equivalent performance, but I was surprised how much > cpu time they took up. So, I suggest check the page load time difference > for a few files: the extra time will be 100% cpu use of a forked > process. +1 for all of this. Especially, I also like colors and will pay CPU loads some attention, if we start giving them. > > > Should we leave color as > > it is now without? Should we try it for a time period and see how it > > is received? What would the users like to see here? > > My preference is to enable this on an experimental basis, watching it closely when we turn it on and, perhaps, taking discussing further analysis and thoughts regularly, such as as a standing point at the volunteer meeting for a few occurrences (ie, until terminated or deemed stable). > > Bob > > > > [[End of PGP Signed Part]] > >
Re: ssh member access updated
On Wed, Mar 23, 2022 at 4:47 PM Bob Proulx wrote: > > SHA1. Hopefully it will all work transparently for everyone. I can git pull via ssh. Thanks very much.
Re: freetype download link failure
On Tue, Sep 14, 2021 at 3:19 PM Anderson Base wrote: > hi, Hi Anderson! > http://download.savannah.gnu.org/releases/freetype/freetype-2.10.1.tar.gz > > I cannot download from this address. Can you check it please? Thanks It appears that since around Aug 22nd a large number of release packages have been moved into an "freetype-old" sub-folder beneath the (usual) releases folder. http://download.savannah.nongnu.org/releases/freetype/freetype-old/ I'm able to download the version you mentioned using this link: https://bigsearcher.com/mirrors/nongnu/freetype/freetype-2.10.1.tar.gz > > > Thanks. > > Anderson Baseggio Regards, Corwin
