[sr #111026] AGPL spamming my `git pull` outputs

Follow-up Comment #12, sr#111026 (group administration): [comment #11 comment #11:] > > The issue has been resolved for the git server. > > I confirm that it seems to be sane again, thank you. Same here. Thanks. ___ Reply to this item a

[sr #111026] AGPL spamming my `git pull` outputs

Follow-up Comment #7, sr#111026 (group administration): [comment #3 comment #3:] > Stefan, the workaround, in case you don't know, is to check the "Quiet SSH member shell" option on https://savannah.nongnu.org/my/admin/ ... it's under "Optional Features". Thanks, Karl. I did this (for my own acc

[Savannah-help-public] [sr #107118] Correction to Bzr access instructions on Savannah project pages.

Follow-up Comment #6, sr #107118 (project administration): I get "Error: Item not found" at https://savannah.gnu.org/support/index.php?10739 ___ Reply to this item at: ___

[Savannah-help-public] [sr #107077] bzr+ssh:// preferable to sftp://

Follow-up Comment #25, sr #107077 (project administration): Implementation proposal posted here: http://lists.gnu.org/archive/html/savannah-hackers-public/2010-03/msg00019.html ___ Reply to this item at:

[Savannah-help-public] [sr #107077] bzr+ssh:// preferable to sftp://

Follow-up Comment #24, sr #107077 (project administration): Re-opened, assigned to self, marked as in-progress. Implementation discussion is in this thread: http://lists.gnu.org/archive/html/savannah-hackers-public/2010-03/threads.html#00011

[Savannah-help-public] [sr #107077] bzr+ssh:// preferable to sftp://

Update of sr #107077 (project administration): Status:None => In Progress Assigned to:Beuc => kfogel Open/Closed: Closed => Open _

[Savannah-help-public] [sr #107143] bzr+ssh:// access should work on savannah for Bazaar

Update of sr #107143 (project administration): Status: Wont Do => In Progress Assigned to:Beuc => kfogel Open/Closed: Closed => Open __

[Savannah-help-public] [sr #107077] bzr+ssh:// preferable to sftp://

Follow-up Comment #23, sr #107077 (project administration): Can this ticket please be re-opened, as all parties seem to agree (based on out-of-band conversations) that bzr+ssh access on Savannah is a desirable thing and not a security risk, and that it's just a question of resources now? Thanks.

Re: [Savannah-help-public] Re: Smart server for Emacs Bazaar repository

Sylvain Beucler writes: >On Fri, Feb 12, 2010 at 12:24:16PM -0500, Karl Fogel wrote: >> Eli Zaretskii writes: >> >Karl, any news on setting up bzr+ssh? >> >> Too swamped with more pressing stuff to do anything with it right now. >> As soon as that changes, I&

[Savannah-help-public] Re: Smart server for Emacs Bazaar repository

Eli Zaretskii writes: >Karl, any news on setting up bzr+ssh? Too swamped with more pressing stuff to do anything with it right now. As soon as that changes, I'll do something, but can't commit to when. -K

[Savannah-help-public] [sr #107118] Correction to Bzr access instructions on Savannah project pages.

Follow-up Comment #3, sr #107118 (project administration): Yes, that was a typo, sorry. The second "emacs-bzr-repository" on that line is a mistake. ___ Reply to this item at:

[Savannah-help-public] [sr #107190] Need commit emails for Emacs's trunk branch in Bazaar.

Follow-up Comment #3, sr #107190 (project administration): Thank you, Sylvain. I think it makes sense to close this now, and if we notice other problems/regressions, we can open separate tickets for those. ___ Reply to this item at: <

[Savannah-help-public] [sr #107190] Need commit emails for Emacs's trunk branch in Bazaar.

Follow-up Comment #1, sr #107190 (project administration): In [1], Glenn Morris points out the correct list address and asks a couple of questions: > I hope this can be fixed soon, I consider this > an important feature. (I see the ticket is > indeed classed as "important".) > > Anyone know i

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #27, sr #106612 (project administration): This can be closed. Emacs has migrated to Bazaar, and remaining issues have their own tickets opened. ___ Reply to this item at: ___

[Savannah-help-public] [sr #107190] Need commit emails for Emacs's trunk branch in Bazaar.

URL: Summary: Need commit emails for Emacs's trunk branch in Bazaar. Project: Savannah Administration Submitted by: kfogel Submitted on: Sat 02 Jan 2010 07:32:58 PM GMT Category:

[Savannah-help-public] [sr #107170] Please make Emacs CVS read-only; we are switching to Bazaar now.

Follow-up Comment #3, sr #107170 (project administration): Thank you, Sylvain! ___ Reply to this item at: ___ Message sent via/by Savannah http:

[Savannah-help-public] [sr #107170] Please make Emacs CVS read-only; we are switching to Bazaar now.

Follow-up Comment #1, sr #107170 (project administration): For reference, the two emails from Stefan Monnier and Chong Yidong where this decision was made are: http://lists.gnu.org/archive/html/emacs-devel/2009-12/msg00532.html http://lists.gnu.org/archive/html/emacs-devel/2009-12/msg00547.html

[Savannah-help-public] [sr #107170] Please make Emacs CVS read-only; we are switching to Bazaar now.

URL: Summary: Please make Emacs CVS read-only; we are switching to Bazaar now. Project: Savannah Administration Submitted by: kfogel Submitted on: Sat 12 Dec 2009 09:08:41 PM GMT

[Savannah-help-public] [sr #107143] bzr+ssh:// access should work on savannah for Bazaar

Follow-up Comment #2, sr #107143 (project administration): sr #107077 seems to have current discussion about this. It's also marked "closed", but comments since then have clarified that bzr+ssh does not have to imply a security problem, and admins indicate they may be willing to add it. ___

[Savannah-help-public] [sr #106951] Upgrade bzr.sv.gnu.org to Bazaar 1.17

Follow-up Comment #7, sr #106951 (project administration): Backports has Bazaar 2.0.2 now: http://www.backports.org/debian/pool/main/b/bzr/ Bazaar developers recommend upgrading to that. The loggerhead we're running should already be compatible, according to the developers I talked to (maybe

[Savannah-help-public] [sr #107118] Correction to Bzr access instructions on Savannah project pages.

Follow-up Comment #1, sr #107118 (project administration): Heh, obviously in the proposed updated instructions, this "Developper [sic]" should just be: "Developer" ___ Reply to this item at:

[Savannah-help-public] [sr #107142] Browsing Bazaar repositories doesn't work

Follow-up Comment #4, sr #107142 (project administration): Blecch :-(. Crashing no fun. Is there anything others can do to help with the checking? ___ Reply to this item at: _

[Savannah-help-public] [sr #107077] bzr+ssh:// preferable to sftp://

Follow-up Comment #22, sr #107077 (project administration): Also, regarding this: * "For example: do you intend, at a point, to implement centralised mail notification on commit? (which is the first thing people ask here) Currently this relies on an expansive, per-repository scanning every 5 min

[Savannah-help-public] [sr #107142] Browsing Bazaar repositories doesn't work

Follow-up Comment #2, sr #107142 (project administration): Hunh. And now it's broken again: 503 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.9

[Savannah-help-public] [sr #106531] Bazaar commit notification emails omit large diffs

Follow-up Comment #18, sr #106531 (project administration): By the way, my patch (see https://savannah.gnu.org/support/index.php?106531#comment12) was accepted into bzr-hookless-email, so it is now possible to limit diffs by bytes as well as lines. For details, see: http://bazaar.launchpad.ne

[Savannah-help-public] [sr #107077] bzr+ssh:// preferable to sftp://

Follow-up Comment #19, sr #107077 (project administration): Sylvain et al, In https://savannah.gnu.org/support/?107077#comment14, Robert Collins (a Bazaar developer) points out that bzr+ssh access does *not* imply shell access or the ability to run arbitrary hooks. He also points out that sftp

[Savannah-help-public] [sr #107142] Browsing Bazaar repositories doesn't work

Follow-up Comment #1, sr #107142 (project administration): This should be closed -- the problem is gone now. ___ Reply to this item at: ___ Messag

[Savannah-help-public] [sr #107143] bzr+ssh:// access should work on savannah for Bazaar

URL: Summary: bzr+ssh:// access should work on savannah for Bazaar Project: Savannah Administration Submitted by: kfogel Submitted on: Wed 25 Nov 2009 08:52:38 AM GMT Category: No

[Savannah-help-public] [sr #107118] Correction to Bzr access instructions on Savannah project pages.

URL: Summary: Correction to Bzr access instructions on Savannah project pages. Project: Savannah Administration Submitted by: kfogel Submitted on: Thu 12 Nov 2009 10:50:27 PM GMT

[Savannah-help-public] [sr #107070] cvs.savannah.gnu.org update and checkout broken due to read-only /tmp dir

URL: Summary: cvs.savannah.gnu.org update and checkout broken due to read-only /tmp dir Project: Savannah Administration Submitted by: kfogel Submitted on: Wed 21 Oct 2009 02:45:10 AM GMT

[Savannah-help-public] [sr #106531] Bazaar commit notification emails omit large diffs

Follow-up Comment #16, sr #106531 (project administration): That makes some sense, especially given that the concern for recipients is the size of the overall mail, not the size of the diff specifically (it just happens that the diff is the element whose size varies the most). In any case, we do

[Savannah-help-public] [sr #106531] Bazaar commit notification emails omit large diffs

Follow-up Comment #14, sr #106531 (project administration): Can you expand on that? There is the question of whether we should place any limit or not; that is a separate issue. But if we decide we do want to place a limit, then I think this hook (assuming we're using it) would be the right plac

[Savannah-help-public] [sr #106531] Bazaar commit notification emails omit large diffs

Follow-up Comment #12, sr #106531 (project administration): I have submitted a patch adding a '--byte-limit' option to bzr-hookless-email upstream: https://code.edge.launchpad.net/~kfogel/bzr-hookless-email/byte-limit/+merge/11233 No action requested right now. If the patch is accepted, we may

[Savannah-help-public] [sr #106951] Upgrade bzr.sv.gnu.org to Bazaar 1.17

Follow-up Comment #5, sr #106951 (project administration): It's in backports now. (You may even have already installed it, I don't know...) ___ Reply to this item at: _

[Savannah-help-public] [sr #106951] Upgrade bzr.sv.gnu.org to Bazaar 1.17

Follow-up Comment #3, sr #106951 (project administration): I talked to two of the bzr backports packagers today, Wouter van Heyst and Jelmer Vernooij, and they will get Bazaar 1.17 into backports.org for Debian stable. Looks like they can probably do it tomorrow, (2009-08-05); I'll check in with

[Savannah-help-public] [sr #106531] Bazaar commit notification emails omit large diffs

Follow-up Comment #11, sr #106531 (project administration): No misunderstanding -- I will take a look at the script and see about getting a patch into it upstream, if still needed. ___ Reply to this item at:

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #26, sr #106612 (project administration): I would mark this ticket as being dependent on new ticket https://savannah.gnu.org/support/index.php?106951 (about upgrading Bazaar on savannah to 1.17), but I don't see how to add the dependency. So, I'm posting this comment instead.

[Savannah-help-public] [sr #106951] Upgrade bzr.sv.gnu.org to Bazaar 1.17

URL: Summary: Upgrade bzr.sv.gnu.org to Bazaar 1.17 Project: Savannah Administration Submitted by: kfogel Submitted on: Wed 29 Jul 2009 04:30:48 PM GMT Category: None

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #24, sr #106612 (project administration): Thanks, Sylvain! (As noted in bug #106632, it works for me when I test now too.) ___ Reply to this item at:

[Savannah-help-public] [sr #106632] Web access to bazaar repo is experimental

Follow-up Comment #5, sr #106632 (project administration): Tested; works for me. Thanks, Sylvain. ___ Reply to this item at: ___ Message sent via/

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #22, sr #106612 (project administration): Oh, looks like you're the one who noticed the duplication, so you're already aware of the code tweak! Sorry. -Karl ___ Reply to this item at:

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #21, sr #106612 (project administration): Sylvain, A fix is proposed in https://bugs.edge.launchpad.net/bzr/+bug/305995/comments/2 -- can you try it and see if it solves the problem on Savannah? (It turns out that the bug I filed, https://bugs.edge.launchpad.net/loggerhead/+bu

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #20, sr #106612 (project administration): In https://bugs.edge.launchpad.net/loggerhead/+bug/325505/comments/1 , Michael Hudson asks: Questions that spring to mind: 1) how are you starting loggerhead? 2) is paste.deploy installed? if so, what version?

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #19, sr #106612 (project administration): Done: https://bugs.edge.launchpad.net/loggerhead/+bug/325505 ___ Reply to this item at: _

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #17, sr #106612 (project administration): Thanks! I clicked on the 'gnash' link at lh/, and then on 'libsound' in the directory list that came up, but 'libsound' got me this error: "Firefox can't establish a connection to the server at bzr.savannah.gnu.org:8080" (It looks

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #15, sr #106612 (project administration): General switchover checklist started: http://www.red-bean.com/scriki/index.php/EmacsBzrSwitchover Sylvain, you don't really need to pay attention to that page, I'm just including it for reference. Items that are relevant to Savanna

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #14, sr #106612 (project administration): To be more specific: I didn't actually know, until now, that Savannah was volunteer-run. ___ Reply to this item at: _

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #13, sr #106612 (project administration): Ah, that clarifies things, okay. I'm currently making a list of all the things we (Emacs) need to do for the switchover. I'll make sure to list here anything that involves Savannah, and if any of them look problematic, we can figure ou

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #9, sr #106612 (project administration): In this context, "non-commit notification" is what we want (I think): it means notification on pushes to the master branch and any other branches we decide we should care about for commit-email purposes. This is all with bzr-email instal

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #7, sr #106612 (project administration): The reason to prefer more recent bzr is more for performance than feature reasons. As for the hook (trigger): I may have pointed you to the wrong thing, sorry. Let me ask around for the Right Way to do server-side commit emails. The go

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #5, sr #106612 (project administration): https://edge.launchpad.net/bzr-email/ To actually fetch it, this works: $ bzr branch lp:bzr-email bzr-email $ cd bzr-email $ ls emailer.py __init__.py README setup.py smtp_connection.py tests/ $ The RE

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #3, sr #106612 (project administration): > The thread you mentioned starts with some kind of bug report (about a CVS->bzr mirror??) and mentions git. Is this serious? Yes, it's serious. The thread goes through many twists and turns. Git is involved in the conversion process

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

Follow-up Comment #1, sr #106612 (project administration): I just learned from sr #106531 that we don't have a Loggerhead installation at Savannah. Can we? ___ Reply to this item at:

[Savannah-help-public] [sr #106531] Bazaar commit notification emails omit large diffs

Follow-up Comment #9, sr #106531 (project administration): Well, for some people even receiving a mail that big is troublesome (download time, for example). Ideally, this would be user-configurable, but I guess in practice that's hard, since the mails are going to mailing lists... ...though one

[Savannah-help-public] [sr #106612] Preparation for switching Emacs from CVS to bzr on Savannah.

URL: Summary: Preparation for switching Emacs from CVS to bzr on Savannah. Project: Savannah Administration Submitted by: kfogel Submitted on: Fri 23 Jan 2009 04:57:55 PM GMT Cate

[Savannah-help-public] [sr #106531] Bazaar commit notification emails omit large diffs

Follow-up Comment #7, sr #106531 (project administration): When the diff is large, just omit it and include a URL to a web-viewable version of the diff (via LoggerHead for example). I mean, there's no point mailing out 1MB diffs -- almost no one wants to receive those, even if when mailing list

[Savannah-hackers] Re: suddenly lost CVS access tosubversions.gnu.org

Okay, I did 'man ssh_config' and read up on the config file format. The key paragraph is: For each parameter, the first obtained value will be used. The configuration files contain sections bracketed by ``Host'' specifications, and that section is only applied for hosts that m

[Savannah-hackers] Re: suddenly lost CVS access tosubversions.gnu.org

Mathieu Roy <[EMAIL PROTECTED]> writes: > I'm puzzled as we got > Accepted rsa for kfogel from 65.42.95.175 port 37964 > in the logs. Wow. That's strange, yeah. > Can you provide the content of /etc/ssh/ssh_config Suer. Note that my system is not OpenBSD (I guess the file was inherited

[Savannah-hackers] Re: suddenly lost CVS access tosubversions.gnu.org

Mathieu Roy <[EMAIL PROTECTED]> writes: > >$ cat ~/.ssh/config > >Protocol 2,1 > >Host cvs.red-bean.com > > EscapeChar none > > ForwardX11 no > >Host subversions.gnu.org > > Protocol 1 > > Normally it should work. > Please replace > Host subversions.gnu.org by Host *gn

[Savannah-hackers] Re: suddenly lost CVS access tosubversions.gnu.org

Mathieu Roy <[EMAIL PROTECTED]> writes: > Can you provide the output of > cat ~/.ssh/config Sure: $ cat ~/.ssh/config Protocol 2,1 Host cvs.red-bean.com EscapeChar none ForwardX11 no Host subversions.gnu.org Protocol 1 $ (Yes, I noticed the last two lines. I

Re: [Savannah-hackers] Re: suddenly lost CVS access tosubversions.gnu.org

"Jaime E. Villate" <[EMAIL PROTECTED]> writes: > your first message arrived at a time when we were having some > strange behavior of the CVS server that we were trying to figure out > and that's probably why your message was not answered because it > seemed to be related to the CVS problem. > > Ple