Bandali reported that lists.gnu.org ran out of disk space, and
escalated that to sysadmin@.
There was a spike in spam on Monday as well .. so might be
afterquakes...
Thank you for this report. I don't know why but the permissions on
that one file were incorrect.
drwxrws--- 6 root gnueval 253 Nov 9 11:34 /srv/svn/gnueval/db
Yeah, I cannot explain it .. the gnueval repository is not heavily
used. I have one job that runs a `svn update' to send
E.g., https://svn.savannah.gnu.org/viewvc/?root=gnueval ->
An Exception Has Occurred
Python Traceback
Traceback (most recent call last):
File "/usr/lib/viewvc/lib/viewvc.py", line 4322, in main
request.run_viewvc()
File "/usr/lib/viewvc/lib/viewvc.py", line 268, in run_viewvc
Can we please turn this nuisance off? It is nothing related to the
AGPL in any shape or form.
You even get this utter garbage when doing an rsync?!
...
sv_membersh is part of Savane.
In order to download the corresponding source code of Savane, run
rsync -avz --cvs-exclude
> I believe users who authenticate do interact with sv_membersh
> in a way analogous to the frontend PHP code invoked through Apache.
>
> I don't agree that the AGPL requires this message to be shown on every
> cvs update. It's one possible interpretation, but not the only
Thank you for your help!
Happy hacking!
It looks like I need some coaching with CVS. It's been a long, long
time since I used it daily.
No worries, same here .. trying to recall.
> $ cvsu
> X manual/html_node
$ cvsu
cvsu: command not found
I assume you had a typo, but for what, I'm not sure.
>https://web.cvs.savannah.gnu.org/viewvc/groff/groff/manual/
If you open that URL you will find a directory:
https://web.cvs.savannah.gnu.org/viewvc/groff/groff/manual/html_node/
Yes, that directory exists.
alongside this one:
There is a stale directory in the GNU groff project's website.
https://www.gnu.org/software/groff/manual/html_node/
This corresponds to the groff 1.22.4 release, which is nearly 5 years
old.
The directory also shows up in ViewVC.
>> Savannah Hackers, would you please add Alfred?
>
>Alfred was added to gnustandards on 2023-06-18.
>
> Not as admin. Brandon is no longer active.
Done; I've also added you to the 'www' group where the generated output
is posted, in prep/.
Please be more
> Savannah Hackers, would you please add Alfred?
Alfred was added to gnustandards on 2023-06-18.
Not as admin. Brandon is no longer active.
> > And some rule on what can "automatically" go into the GCS without
your
> > explicit review and approval.
>
>Normally all changes in the GNU standards have to be approved by me,
>though it would be ok to fix a trivial typo.
>
> Fair enough. I'm still
[[[ To any NSA and FBI agents reading my email: please consider]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> And some rule on what can "automatically" go into the GCS without
> *waves hand as volunteer* I could do it, it isn't that much work.
Thank you for volunteering -- please take up the responsibility.
Do you need anyone else's help to do that?
Only admin access to https://savannah.gnu.org/projects/gnustandards --
CCing savannah hackers.
And some rule
That sounds reasonable to me. I would assume that if webmasters don't
have access to change robots.txt, it would just be the fsf tech team.
They do. It is in www.
I'm still sorta opposing this .. we have always been transparant.
That search engines "have no business" is as saying that
Might be worth noting that www.gnu.org is mostly usable locally from
the CVS checkout as well, if one needs to look things over.
So a patch to www-discuss@ or whatever for a unpublished article would
be sufficient in postponing any publishing. It would just be a matter
of applying the patch, and
Le 10/05/2023 à 20:50, Alfred M. Szmidt a écrit :
> > You've not explained the actual problem. What are you trying to
> > solve?
>
> "it" is the www-commits list, which registers all changes to the www
> directory, including
> You've not explained the actual problem. What are you trying to
> solve?
"it" is the www-commits list, which registers all changes to the www
directory, including to pages that are not published yet. I suspect most
of the other *-commits lists deal with source code repositories,
Because it registers every single commit to www,
What is "it"? How is this different from _any_ -commits list we have?
including to working directories that webmasters have disallowed,
for instance */po/, /server/staging/, */workshop/, /prep/gnumaint/,
etc.
Ok, and?
Please
I was searching for an article with DuckDuckGo, and guess what
appeared on top of the results...
https://lists.gnu.org/archive/html/www-commits/2023-05/msg00082.html
and
https://lists.gnu.org/archive/html/www-commits/2023-05/msg00062.html
!!
What is the problem?
I understand
Lately, mail delivery by gnu.org mailing lists intermittently suffers
from very long delays. For example, currently emacs-devel and
help-gnu-emacs mail is delivered with delays between 45 minutes and
1.5 hours (based on admittedly small and potentially
non-representative sample).
Sometimes, some of us subscribed here, can also ping the FSF admins in
other ways -- sysadmin@ is not a list that is easily subscribed to
AFAIK.
But the gripe about the FSF Status page is real: lately I find it less
and less useful in such cases. Which is too bad.
Just to give a small shout, I agree.
This is I think better directed to the FSF sysadmins. CCing.
> Date: Tue, 28 Jul 2020 09:54:28 +0200 (CEST)
> From: Angelo Graziosi
>
> I noticed that reading the post online
(https://lists.gnu.org/archive/html/emacs-devel/2020-07/index.html, for
example), the email address in
Why not simply use a reference repository?
git clone --mirror git://git.gnu.org/emacs.git ~/emacs-reference
And when cloning:
git clone --reference ~/emacs-reference git://git.gnu.org/emacs.git
the ~/emacs-reference place can be accessible where ever you are using
it. This will work
> Is there any reason we can't shutdown the old frontend now? I can't
> think of anything that is still using it. I think the time has come
> that we can now shutdown halt the old frontend.
I moved the content of frontend:/root
into frontend0:/root/old-frontend-root -
it had
I have forwarded this to the Chapters/Planet admin(s).
Comments, suggestions and improvements welcomed.
I like it. Maybe put it into the GNU maintainers guide as well?
Maybe incorperate it with the Free Software Directory somehow, there
could be an icon showing that a package is available in Guix; and
which version.
Itâs clear that CVS is a hindrance for such purposes so if thereâs
another possibility,
Ludo, why must we go through this yet again? Surely you know perfectly
well by now that there is no other possibility at present.
Not to mention that it isn't a problem with CVS;
Perhaps Savannah is not suited for the purpose of replacing Github,
but at the very least the FSF should sponsor sites like:
https://notabug.org/
which are based on free software and host exclusively free software
(unlike Github, which accepts proprietary programs).
It seems that
> It seems that http://notabug.org also accepts non-free programs, for
> example:
>
> https://notabug.org/nelis/hg-shopp-theme
>
> This has no license information what so ever. If this is in error or
> not, I don't know.
This should have not happened, according to
There is no license that limits commercial use and still compatible
with GPLv2 (and GNU savannah).
Or any free software license for that matter. All free software
licenses explicitly allow commercial use.
I'm getting the following error when trying to push, anyone know what
is wrong?
$ git push --verbose
Pushing to git://git.sv.gnu.org/womb/hacks.git
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 426 bytes | 0
Instead of getting emotional, have you tried doing `git commit
--amend'? That command is exactly created for situations like this!
My new project has been recently approved (gnu-social-mode), but due to
a new member's mistake there is a commit on the repository which is
malformed.
The proper way is to use `git commit -amend'; not rewrite history.
But what do you mean malformed? These are the few last commits to
Or you, if you're the only one working on that repository, you
could try to fix it using `git revert` (see the manual for that).
Yeah, I know about git-revert. But the wrong commit is so
small/simple that it doesn't take much to revert it.
Just use `git commit --amend' for that.
I assume this is known, but the savannah web site isn't answering and
neither is the git repo (git.sv.gnu.org).
Savannah (including all other GNU and FSF machines) are being moved to
a new colo.
| The GNU/FSF servers are moving between February 22nd and March 1st,
| 2012. There will be
The question is not whether Android requires aditional software to be
useful but whether it can be used with only free software, for otherwise
Android-specific projects can't run on a fully free enviroment which is
a requirement in GNU Savannah.
A simple approach might be to do what
I won't object the migration of #savannah to some other IRC network
if someone trustable first check than it doesn't have issues like
this one (Or precisely this one). But I'm definitively not that
someone.
I see no reason why you can't do it, could you do it so we can resolve
this
I haven't recived any updates on this, have you tried using Freenode
with TOR? Could you update me on the status?
We shouldn't confuse the discussion, it is about having #savannah on
irc.gnu.org, not about Freenode, OTFC or where to host it.
If TOR users have issues with Freenode it is better to solve the
problems with them, than changing networks every week. Could you
bring the issues you experienced with
Hi,
I find it immensly annoying that irc.gnu.org isn't hosting #savannah,
while I understand Sylvain's concerns regarding TOR, it does more harm
than good to have some IRC channels (specially ones as important as
#savannah, which has been invaluable when shit hits the fan) on random
servers.
If
Could someone look into this? We don't know what is wrong.
--- Start of forwarded message ---
Date: Thu, 18 Nov 2010 17:39:50 +0100
To: Sergey Poznyakoff g...@gnu.org.ua
Cc: Alfred M. Szmidt a...@gnu.org,
Jeff Bailey jbai...@raspberryginger.com,
Alain Magloire ala
It's a mostly-default one.
You can enable branch deletion by doing this on the server:
git --git-dir /vservers/vcs-noshell/srv/git/inetutils.git \
config hooks.allowdeletebranch true
I have enabled it. Sorry for not being able to react earlier.
Alfred, please
We're using contrib/hooks/post-receive-email from the Git release.
I would suggest sending patches to the Git project.
Can you send me a copy of this file?
It seems that `git diff' still gets immensly confused when producing
diff output, man/Makefile.am was not copied from Makefile.am. The
summary at the end if also confusing, the diff states that Makefile.am
was copied to man/Makefile.am, while the summary says
rexec/Makefile.am was copied to
47 matches
Mail list logo
