??changed:
-We run mirmon for mirrors of ftp.gnu.org and of dl.sv.nongnu.org.
We run mirmon for mirrors of ftp.gnu.org and of dl.sv.nongnu.org and, as a
favor, of ctan.org.
??changed:
-Mirror request page for both gnu and nongnu is
http://www.gnu.org/server/mirror.html.
-
-dl.sv also runs the m
++added:
gnu urls:
++added:
nongnu urls:
??changed:
-Special stuff:
-
-List of mirrors for mirmon automatically created from
``http://www.gnu.org/prep/ftp.html`` by ``/root/bin/gnu-mirmon.pl``
The list of mirrors for gnu mirmon is automatically created from
``http://www.gnu.org/prep/ftp.html
??changed:
-Note: there is at most a 1/2h delay between Git activation in the web
front-end, and its creation on the system.
You must activate git in the `Select Features' page for the project (as a
project administrator) for anything to work. There is at most a 1/2h delay
between Git activati
??changed:
-There is some work on the mail infrastructure to provide a finer-grained
control over the mail and better fight spam. But this is not yet done (it is
being implemented by the FSF sysadmins).
-
-Meanwhile, the best alternative is described in ListHelperAntiSpam.
-
The FSF mail servers
??changed:
-* Regarding Android phones
- * Provided Savannah's maintainers have the capacity, projects running on
Replicant may be hosted on Savannah. Projects having dependencies on non-free
software, such as proprietary software drivers or AndroidOS, are not
permissible.
* Regarding Android
??changed:
-/root/adminstration/mirrors-contacts.txt; 2) on sftp.in.sv.gnu.org, add the
mirror url(s) to 2a) /srv/download/00_MIRRORS.html (alphabetical, check
http://download.savannah.gnu.org/releases-noredirect/00_MIRRORS.html) and 2b)
/srv/download/00_MIRRORS.txt (no order).
/root/administ
??changed:
-Since we provide rsync read-only access to the CVS repository, one may expect
to also get write access.
-
-We do not provide direct write access to the CVS repository for several
reasons:
Since we provide rsync read-only access to the CVS repository, one may expect
to also get write
--removed:
-
-From microfirm Fri Mar 2 20:31:58 + 2012
-From: microfirm
-Date: Fri, 02 Mar 2012 20:31:58 +
-Subject: lwip client
-Message-ID: <20120302203158+0...@savannah.gnu.org/maintenance>
-
-
--
forwarded from
http://savannah.gnu.org/maintenance/FrontPage#msg20120313224625+0...@sava
??changed:
-SSH keys may be synced to the savannah virtual machines using the
"/root/vcs/administration/authorized_keys_replicate.sh" script, which copies
the /root/.ssh/vm_authorized_keys file to the other virtual machines.
SSH keys may be synced to the savannah virtual machines using the
/roo
??changed:
- # on internal
# run on internal:
??changed:
- # check if there's no error
# check if there's no error, then do:
??changed:
-This must be run on the internal subhost. (The old location was
administrationmaintenance/ml.pl on colonialone / mgt.)
This must be run on the internal subh
??changed:
-Savannah hackers: to handle such a request for CVS notifications, use
https://savannah.gnu.org/cvs/admin/?group=foo (only accessible to sv admins).
-For notifications for a subversion repository, see /root/infra/svn.txt.
Savannah hackers: to handle such a request for CVS notificatio
++added:
When accepted, you will be made an administrator of the administration project,
which will enable the "Become Superuser" option in the left-hand menu.
--
forwarded from
http://savannah.gnu.org/maintenance/HowToBecomeASavannahHacker#msg20111228010218+0...@savannah.gnu.org/maintenance
??changed:
-- gnu mirmon conf - /etc/mirmon-gnu.conf
- gnu mirmon conf - /etc/mirmon-gnu.conf
- gnu mirmon web page - http://download.savannah.gnu.org/mirmon/gnu/
??changed:
-- nongnu mirmon web page - http://dl.sv.gnu.org/mirmon/
-- nongnu multiplexor - http
??changed:
-Mirmon operates on download.savannah.gnu.org
Mirmon operates on download.savannah.gnu.org.
We run mirmon for mirrors of ftp.gnu.org and of dl.sv.nongnu.org.
In each case, there is a multiplexor so users can be automatically redirected.
- gnu mirror list - http://www.gnu.org/prep/ftp
??changed:
-attach the list to the given project using infra/maintenance/ml.pl::
-
- infra/maintenance/ml.pl -a adminsname -g project -l listname
attach the list to the given project using our convenience script ml.pl::
# on internal
/root/bin/ml.pl -a adminusername -g project -l listname
??ch
--removed:
-
-From john7334 Thu Nov 24 17:08:21 + 2011
-From: john7334
-Date: Thu, 24 Nov 2011 17:08:21 +
-Subject: NIce
-Message-ID: <2024170821+0...@savannah.gnu.org/maintenance>
-
-Thanks for this particularly useful information -
http://www.findacellphoneuser.com/
--
forwarded f
??changed:
- - savannah-help-pub...@gnu.org: alias to savannah-hack...@gnu.org;
sv-hackers was not renamed so that archives urls stay valid.
- savannah-help-pub...@gnu.org: alias to savannah-hack...@gnu.org; sv-hackers
was not renamed so that archive urls stay valid.
??changed:
- - system-h
??changed:
-If you want to import an existing SVN repository at Savannah (with multiple
revisions):
If you want to import your existing SVN repository at Savannah (preserving all
history):
++added:
Or anywhere else that is convenient.
--removed:
-
--
forwarded from
http://savannah.gnu.org
??changed:
-Packages' bzr repos are in /srv/bzr on vcs. Server log is /root/.bzr.log,
configuration /root/.bazaar (run bzr --version for this info). Apache logs for
the bzr vhost are in /var/log/apache2/bzr.
Packages' bzr repos are in /srv/bzr on vcs. Server log is
/var/lib/bzr/.bzr.log, con
??changed:
-Packages' bzr repos are in /srv/bzr on vcs.
Packages' bzr repos are in /srv/bzr on vcs. Server log is /root/.bzr.log,
configuration /root/.bazaar (run bzr --version for this info). Apache logs for
the bzr vhost are in /var/log/apache2/bzr.
bzr is ultimately invoked from /etc/xinet
??changed:
- chmod g+w -R /srv/svn/$proj/db/revs/*
- chmod g+w -R /srv/svn/$proj/db/revprops/*
chmod g+w -R /srv/svn/$proj/db/re*
--
forwarded from
http://savannah.gnu.org/maintenance/AdminSvnImport#msg20111012214438+0...@savannah.gnu.org/maintenance
??changed:
- mkdir -m 755 ~mharc/$listname
- cd ~mharc/$listname
mkdir -m 755 ~mharc/mbox/$listname
cd ~mharc/mbox/$listname
++added:
Then you can check http://lists.nongnu.org/archive/html/$listname.
--
forwarded from
http://savannah.gnu.org/maintenance/ImportMailingListArchive#msg2011101118
??changed:
- ~mharc/bin/mbox-month-pack
/var/mailman/archives/private/$listname.mbox/$listname.mbox
~mharc/bin/mbox-month-pack
/var/lib/mailman/archives/private/$listname.mbox/$listname.mbox
??changed:
- ~mharc/bin/web-archive -rebuild $listname $listname2 ... >/tmp/out
~mharc/bin/web-archive
??changed:
-When we are told of a new mirror, we should verify, and then 1) on
colonialone, add contact information to
-/root/mirrors-contacts.txt; 2) on sftp.in.sv.gnu.org, add the mirror url(s) to
2a) /srv/download/00_MIRRORS.html (alphabetical, check
http://download.savannah.gnu.org/releases
??changed:
-* Launch a curl to update www.gnu.org/software/PROJECT -- the appropriate
command from /root/curl.txt.
* Launch a curl to update www.gnu.org/software/PROJECT -- the appropriate
command from mgt:/root/administration/curl.txt.
--
forwarded from
http://savannah.gnu.org/maintenance/Non
??changed:
- bzcat myproject.dump.bz2 | svnadmin load /srv/svn/myproject/ >&
/tmp/svimport.out
proj=MYPROJECT
bzcat myproject.dump.bz2 | svnadmin load /srv/svn/$proj/ >&/tmp/svimport.out
??changed:
- chmod g+w -R /srv/svn/myproject/db/revs/*
- chmod g+w -R /srv/svn/myproject/db/revprops/*
chm
??changed:
-named PROJECTNAME-*, or {bug,info,help}-PROJECTNAME. This is done through the
normal
-savannah web admin interface, topic Mailing Lists.
named PROJECTNAME-*, or PROJECTNAME, or {bug,info,help}-PROJECTNAME. This is
done through the normal
savannah web admin interface, subpage Mailin
??changed:
-This is now done by default for lists created through savannah.
This is done by default for lists created through savannah.
The system is called listhelper, and its home page is
http://listhelper.nongnu.org.
++added:
Extensive suggestions and comments about many other Mailman configu
??changed:
-The following are not related to stats, but making a new page seemed worse.
Here are some queries to get a grip on the mysql databases for savannah:
-
-mysql savane # on the internal subhost
-show databases; # show all databases in the installation
-show tables from sav
??changed:
-As of 20051217.
The following are not related to stats, but making a new page seemed worse.
Here are some queries to get a grip on the mysql databases for savannah:
mysql savane # on the internal subhost
show databases; # show all databases in the installation
show tab
??changed:
-From andy Tue Aug 23 06:27:51 + 2011
-From: andy
-Date: Tue, 23 Aug 2011 06:27:51 +
-Subject:
-Message-ID: <20110823062751+0...@savannah.gnu.org/maintenance>
-
-Yes, you can do it exactly as with the HEAD file
-[http://phonyphonecalls.blogspot.com/ reverse phone lookup]
-
-Fro
??changed:
-Since the process can be long, it's recommended to start it in a screen::
-
- ssh vcs-noshell.in.sv.gnu.org
- screen
Since the process is usually long with lots of output, it's recommended to
start it in a screen or redirect as below, etc.::
ssh vcs
??changed:
- wget http://url/to/
++added:
The mail server configuration for the wiki is under Root folder -> Mailhost.
Changes to this wiki are sent to the savannah-cvs list.
--
forwarded from
http://savannah.gnu.org/maintenance/HowToAdminThisWiki#msg20110826165720+0...@savannah.gnu.org/maintenance
??changed:
- * Site Administration > Main page > Browse users > "[Delete]". (search
doesn't work as of jul11).
* As savannah super-user in the web interface, navigate to Site Administration
> Main page > Browse users > "[Delete]". (search doesn't work as of jul11).
--
forwarded from
http:/
++added:
* Site Administration > Main page > Browse users > "[Delete]". (search
doesn't work as of jul11).
--
forwarded from
http://savannah.gnu.org/maintenance/DeletingUserAccount#msg20110714212358+0...@savannah.gnu.org/maintenance
??changed:
-Non-free software is an ethical (and maybe even a social) problem so you
shouldn't release your free software under a non-free license, too.
Non-free software is an ethical (and social) problem so you shouldn't release
your free software under a non-free license, too.
--removed:
-Fr
??changed:
- * Double checking the user_name and user_id is good for security :)
-
-From AndyHunter Sat May 28 02:42:28 + 2011
-From: Andy Hunter
-Date: Sat, 28 May 2011 02:42:28 +
-Subject: HKEY_LOCAL_MACHINE\SOFTWARE\Avira\AntiVir Desktop\FACT
-Message-ID: <20110528024228+0...@savannah.g
??changed:
-Note: for an overview of how mail are _sent from_ Savannah, please check
InternalMailSystem.
Note: for an overview of how mail are sent _from_ Savannah, please check
InternalMailSystem.
??changed:
- There are no static Mailman aliases; instead, is looks at
'/var/mailman/lists/list_
??changed:
-Help from the Savannah administration may be obtained by using the Savannah
administration support tracker
(https://savannah.gnu.org/support/?group=administration).
Help from the Savannah administration may be obtained by using the Savannah
administration support tracker
(https://
++added:
Packages' bzr repos are in /srv/bzr on vcs-noshell.
--
forwarded from
http://savannah.gnu.org/maintenance/Bzr#msg20110429225922+0...@savannah.gnu.org/maintenance
??changed:
- * !OpenVPN (http://openvpn.net/download.html, which requires !LZO,
http://www.oberhumer.com/opensource/lzo/download/)
* !OpenVPN (http://openvpn.net/download.html, which requires LZO,
http://www.oberhumer.com/opensource/lzo/download/)
--
forwarded from
http://savannah.gnu.org
??changed:
- * !OpenVPN
* !OpenVPN (http://openvpn.net/download.html, which requires !LZO,
http://www.oberhumer.com/opensource/lzo/download/)
??changed:
- /etc/openvpn/savannah.conf (*change paths*)::
/wherever/savannah.conf (*change paths*)::
??changed:
- * To start a vpn connection
--removed:
-* Give access to group 'www' on the new GNU project -- ssh
vcs-noshell.in.sv.gnu.org, then see /etc/init.d/cvs_permissions for setfacl
stuff.
-
--
forwarded from
http://savannah.gnu.org/maintenance/NonGnuToGnuSysadmin#msg20110428220743+0...@savannah.gnu.org/maintenance
??changed:
-* Write a half-page technical description of your project: its goal, its
programming language and its dependencies (with !URLs).
* Write a short technical description of your project: its goal, its
programming language and its dependencies (with !URLs).
??changed:
-* GNU GPL-compati
??changed:
-Following that it will take approximately one hour for the cron jobs to run
and the project to be fully populated (for the sake of, e.g.,
ImportingCVSRepository): replicate Savannah DB groups into the 'accounts'
system, replicate the groups to other VServers, create repositories in
??changed:
-Licensing under "GNU GPL v2 only" (or v3 only) is problematic: since we have
published GNU GPL v3, it is important for GNU GPL-covered programs to advance
to v3, which deals with new flaws. But, v3 is incompatible with v2, because of
the nature of copyleft. The same issues will ari
??changed:
- Your license should be compatible with the GNU GPL, current version or
later. Exception: Affero GPL.
Your license should be compatible with the GNU GPL, current version or later.
(This includes LGPL*-only, since all LGPL versions can be converted to any
version of the GPL. Of
??changed:
-The official requirements list are located at
https://savannah.gnu.org/register/requirements.php . This page explains the
points in more details.
The official requirements list is at
https://savannah.gnu.org/register/requirements.php. This page explains the
points in more details.
??changed:
-How to become a savannah hacker (ie a savannah's website administrator) and
help savannah.
-
-Read "how to get your project approved quickly", which explains in detail what
a submitter should check, but also serves as a guide for the Savannah hackers
reviewing the project:
https://
??changed:
-Here are the details:
Here is how to set it up:
??changed:
-them.) Thus, you should pay attention to the once-a-day mailman
them.) Thus, you should pay attention to the once-per-day mailman
??changed:
-Shared moderation: lists @(non)gnu.org can use
listhelper-moderatedelet...@gnu.
??changed:
-You can simply setup your SSH key by typing in a terminal::
Set up your SSH key by typing in a terminal::
??changed:
-Then copy ``~/.ssh/id_rsa.pub`` at
https://savannah.gnu.org/my/admin/editsshkeys.php (once logged in).
Then copy ``~/.ssh/id_rsa.pub`` in
https://savannah.gnu.org/my
--removed:
-From utorme1 Mon Mar 14 01:54:32 + 2011
-From: utorme1
-Date: Mon, 14 Mar 2011 01:54:32 +
-Subject: loggerhead problems
-Message-ID: <20110314015432+0...@savannah.gnu.org/maintenance>
-
-have you just tried to upgrade your version of loggerhead from launchpad.net
The current v
++added:
High load
=
If a !DomU is experiencing heavy load, running these rwo commands will dump
some basic system state for possible post mortems:
d=`date +%F.%T`; cd ~
ps auxww>ps-$d & lsof>lsof-$d & netstat --numeric-hosts>netstat-$d &
We have often seen high loads due to vc brows
??changed:
-The new hardware has eth0 (leftmost when looking from back) orange loopback
cable to "old" savannah, eth1 (rightmost looking from back) black cable to port
22 of ge-sw1.qcy. The MACs end with :2c and :2d but there seem to be a
confusion/swap at boot time (e.g. pxeboot), so don't rel
??changed:
-We're rewriting Savane! See SavaneRewrite
We're rewriting Savane! See SavaneRewrite ...
++added:
The live checkout is /usr/src/savane on the frontend vhost.
--
forwarded from
http://savannah.gnu.org/maintenance/SavaneTasks#msg20110302014020+0...@savannah.gnu.org/maintenance
++added:
++added:
--
forwarded from
http://savannah.gnu.org/maintenance/RenamingProjectGroup#msg20110302005826+0...@savannah.gnu.org/maintenance
___
Savannah-cvs mailing list
Savannah-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/savannah-cvs
??changed:
-
-Renaming a Project Group
-
==
Renaming a Project (Group)
==
??changed:
-We here provide a Savannah-specific solution as a word-around. It's mainly
about running ``~/infra/maintenance/ren
??changed:
-When that CVS repository is updated, there is a commit hook to update the live
installation, but with the move from VServer to Xen, we won't have bind mounts
anymore, so we'll have to find a replacement.
-
When that CVS repository is updated, there was a commit hook to update the liv
??changed:
- ssh r...@savannah.gnu.org
ssh r...@savannah.gnu.org, then ssh frontend.in.sv.gnu.org
--
forwarded from
http://savannah.gnu.org/maintenance/SavaneConfiguration#msg20110217194315+0...@savannah.gnu.org/maintenance
___
Savannah-cvs mailing l
??changed:
-Actually doing it
-
- 'mysql savannah'
Actually doing it (running this on internal.in.sv.gnu.org is preferred):
'mysql savane'
--
forwarded from
http://savannah.gnu.org/maintenance/ManuallyChangeEMail#msg20110116234120+0...@savannah.gnu.org/maintenance
??changed:
- * To test a full system, QEMU and VirtualBox disk images are available at
http://download.savannah.gnu.org/releases/savane/test-install/
* To try a full system, QEMU and VirtualBox disk images are available at
http://download.savannah.gnu.org/releases/savane/test-install/
* Or, t
??changed:
- * The project fundations are ready, we're currently implementing all the user
interface screens
* The project foundations are ready, we're currently implementing user
interface screens
??changed:
-we'd like you to join this effort to make Savannah the best Free forge :)
We'd like
++added:
Working on Savannah Internals
=
The above is about helping as a Savannah administrator via the web interface.
If you are willing and able to hack on the Savannah (Savane) implementation
itself, see the SavaneRewrite page.
--
forwarded from
http://savann
??changed:
-+ rename on Savannah if attached to a Savannah project::
-
- UPDATE mail_group_list SET list_name='NEW' WHERE list_name='OLD';
+ rename in Savannah database if attached to a Savannah project (using
internal.in.sv.gnu.org for this is preferred)::
UPDATE savane.mail_group_list SET lis
++added:
Around Dec 18, 2010, Sylvain created a backup/dl.sh script whose task is to
download all the scripts and config files from the live Savannah that
cannot be included directly in the documentation because they are too
big, or change too often. The good surprise is that there aren't many su
??changed:
-very-conservatively-configured spamassassin, and 95+% of spam will be
conservatively-configured spamassassin, and 95+% of spam will be
??changed:
-The process does not affect messages from members and approved
The process does not affect messages from approved members and other approv
--removed:
-
++added:
**Public mailing lists**
??changed:
-Put the resulting mailboxes in::
-
- mkdir -m 755 ~mharc/mbox//
Put the resulting mailboxes in ~mharc/mbox/.
??changed:
-
mkdir -m 755 ~mharc/$listname
??changed:
- ~mharc/bin/web-archive -rebuild listname1 listname2 ...
-
-If you
++added:
Savannah hackers: to handle such a request for CVS notifications, use
https://savannah.gnu.org/cvs/admin/?group=foo (only accessible to sv admins).
For notifications for a subversion repository, see /root/infra/svn.txt.
--
forwarded from
http://savannah.gnu.org/maintenance/cvsemailon
??changed:
-Sometimes we use listhelper-moderatedelet...@gnu.org as the public
administrator name, for lists which are particular prone to forgery junk.
Hopefully users will know what to do.
Sometimes we use listhelper-moderatedelet...@gnu.org as the public
administrator name, to avoid some sp
??changed:
- ~mharc/bin/mbox-month-pack
/var/mailman/archives/private/$listname/$listname.mbox
~mharc/bin/mbox-month-pack
/var/mailman/archives/private/$listname.mbox/$listname.mbox
--
forwarded from
http://savannah.gnu.org/maintenance/importmailinglistarchive#msg20100907213655+0...@savannah.
++added:
* Admin notes for savannah: see infra/git.txt.
--
forwarded from
http://savannah.gnu.org/maintenance/usinggit#msg20100731233201+0...@savannah.gnu.org/maintenance
___
Savannah-cvs mailing list
Savannah-cvs@gnu.org
http://lists.gnu.org/mailman/
??changed:
-Also, some parts can't be managed by Savane directly, namely the webpages and
the mailing lists. Hence the scripts doesn't do anything on webpages and
mailing lists.
The last line of output from the script shows a curl invocation. You should
run that by hand, with the appropriate "
++added:
Q: RSA or DSA? A: RSA.
---
We recommend using only RSA keys, not DSA. Full details are at
http://meyering.net/nuke-your-DSA-keys/ (and its links); in short, on a system
with a buggy OpenSSL library, DSA keys (but not RSA keys) can be easily cracked
by an attacker
??changed:
-* A choice of !VCSes (version control systems) for your source code:
-
* A choice of !VCSes (version control systems) for your source code
(alphabetical order):
* GNU Arch (UsingGnuArch)
* GNU Bazaar (Bzr_)
--removed:
- * GNU Arch (UsingGnuArch)
- * Subversion (SubversionFAQs)
??
++added:
There is an hourly cron job that collects the "domains" information, so changes
are not instantaneous.
--
forwarded from
http://savannah.gnu.org/maintenance/listserver#msg20100426233806+0...@savannah.gnu.org/maintenance
___
Savannah-cvs mai
??changed:
-* Discuss with your fellow Savannah hackers about issues you face, and give
them time to answer. Often, a external point of view will help.
* Discuss with your fellow Savannah hackers about issues you face, and give
them time to answer. Often, an external point of view will help.
??changed:
-When communicating with Savannah users, keep in mind that you represent the
GNU project, and you need to give a good image of us :)
-
-It may sound silly to describe precisely what "politeness" is. However it is
very easier to forget about it when doing maintenance work day after day
??changed:
-Moving from non-GNU to GNU:
Moving from non-GNU to GNU (for savannah administrators):
--
forwarded from
http://savannah.gnu.org/maintenance/nongnutognusysadmin#msg20100422231902+0...@savannah.gnu.org/maintenance
___
Savannah-cvs mailing l
??changed:
-Files will appear at http://download.savannah.nongnu.org/releases/project/
Files will appear at http://download.savannah.nongnu.org/releases/project/.
This is multiplexed between all mirrors, hopefully picking a nearby and
up-to-date one. Please expect a delay of up to 24 hours for
??changed:
- This is in the left-hand menu, Site Administration / Main Page -> Browse
Groups List. Change to GNU and hit the update button. Do not use the icons at
the top (check mark and wrench+screwdriver).
This is in the left-hand menu, ``Site Administration / Main Page -> Browse
Groups
??changed:
-We are looking for mirrors of the nongnu download area. The webmasters may
inform us, or people may come to us directly. Information for new mirrors is
at http://www.gnu.org/server/mirror.html (GNU webmasters can edit). When we
are told of a new mirror, we should verify, and then
??changed:
-We are looking for mirrors of the nongnu download area. The webmasters may
inform us, or people may come to us directly. Information for new mirrorers is
at http://www.gnu.org/server/mirror.html (GNU webmasters can edit). When we
are told of a new mirror, we should verify, and th
??changed:
- This is in the left-hand menu, Site Administration / Main Page -> Browse
Groups List. Change to GNU and hit the green check mark. Do not "trigger
creation" (wrench and screwdriver).
This is in the left-hand menu, Site Administration / Main Page -> Browse
Groups List. Change to
??changed:
- This is in the left-hand menu, Site Administration / Main Page -> Browse
Groups List.
-
-* FTP access to ftp|alpha.gnu.org is made by the maintainer.
This is in the left-hand menu, Site Administration / Main Page -> Browse
Groups List. Change to GNU and hit the green check mark.
84 matches
Mail list logo
