[Fusionforge-commits] FusionForge branch master updated. v5.3-rc4-3041-gab3bcf6

Roland Mas lolando at libremir.placard.fr.eu.org
Fri May 29 17:38:09 CEST 2015


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "FusionForge".

The branch, master has been updated
       via  ab3bcf69dfd80c56fb7f161c05dcf82854833754 (commit)
       via  3e5223dd4cc69cc556a10ce9937d826f5ee69b91 (commit)
       via  df612ce2c112c54c6b99f4e9ee7ac7bb397d316e (commit)
       via  7675546c6152cde58f576e08c4494a4d2d2ef395 (commit)
       via  b20542504063848d4f397f207832760b68d51d67 (commit)
       via  7641cef095d1624c073e24ca96d22edc11371ef5 (commit)
      from  e070fe97ed37faa539d9d7bb4f703b7e95fe1637 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit ab3bcf69dfd80c56fb7f161c05dcf82854833754
Merge: e070fe9 3e5223d
Author: Roland Mas <lolando at debian.org>
Date:   Fri May 29 17:37:56 2015 +0200

    Merge branch '6.0'


-----------------------------------------------------------------------

Summary of changes:
 src/INSTALL.TXT             | 367 +-------------------------------------------
 src/NEWS                    | 198 ------------------------
 src/rpm/fusionforge.spec.in |   7 +-
 3 files changed, 7 insertions(+), 565 deletions(-)
 delete mode 100644 src/NEWS

diff --git a/src/INSTALL.TXT b/src/INSTALL.TXT
index c1bd273..8cde9d4 100644
--- a/src/INSTALL.TXT
+++ b/src/INSTALL.TXT
@@ -1,365 +1,2 @@
-Installation of FusionForge is a non-trivial undertaking, since it integrates
-with so many different components across your system. A skilled sysadmin 
-is required to pull it off, or at the least a great deal of patience.
-
-The result of a complete installation means automatic creation of CVS 
-and Subversion repositories, and having access to them controlled by 
-FusionForge and stats gathered from them. ViewCVS (used for CVS and
-Subversion browsing) are two additional integration points.
-
-BASICS OF INSTALLATION
-----------------------
-
-
-For Ubuntu/Debian system, you should use the debian packaging, see
-the fusionforge.org website for the correct instructions.
-
-For an installation on CentOS or Red Hat, use the following command.
-
-install.sh <hostname with domain>
-
-That will install the bulk of the system and even set up a site admin
-user account for you.
-
-
-****
-The information below may not be necessary if you succeeded installing
-using the above method. However this info may give you an overview 
-of how the installation is done.
-****
-
-
-
-
-OVERVIEW
---------
-
-FusionForge has a lot of different pieces touching a lot of different components
-in the system. Cronjobs are required to maintain the system, touching lots 
-of files on a daily and hourly basis, including /etc/* system files.
-
-The plugins that now manage the CVS and SVN functionality have made 
-installation slightly harder because even more files have to be moved into
-place during installation.
-
-The manual installation of fusionforge is documented below. Be sure to follow
-each step carefully, check the forums for frequently asked questions, 
-and ask your Apache, mailman, and postgresql installation questions in the
-corresponding mailing lists rather than on the gforge forums where little
-help is available.
-
-
-  CVS Overview
-  ------------
-  CVS is now managed via the scmcvs plugin which is included in the 
-plugins/ directory in the tarball downloaded from gforge.org. Most 
-of the files in scmcvs are intended for auto-installation on debian 
-systems and DO NOT APPLY to the majority of users. The scmcvs plugin 
-is activated by default in the gforge.sql database.
-
-  Cronjobs for CVS are included in cronjobs/crontab.in, but are commented 
-out by default for your security. cronjobs/cvs-cron/* contains the files 
-that are executed hourly to build permissions and create blank cvs trees.
-Make sure these files are executed as root, and have proper execution bits
-set.  Each of these cronjobs has configuration parameters which you may 
-have to edit manually the paths in those files for your specific system.
-
-
-  SVN Overview
-  ------------
-
-  If you want to use GForge's svn-over-DAV support and apache2 are 
-required.
-
-  SVN is also managed via plugin - the scmsvn plugin is included and 
-activated by default in gforge.
-
-  The sample etc/gforge-httpd.conf.example file in this tarball contains 
-a COMPLETE AND WORKING vhost for subversion-over-dav. The gforge-install.sh
-script will copy this to /etc/gforge/httpd.conf You may have to 
-alter the passwords and any other config options, but the sample config 
-shown has been used in dozens or even hundreds of installs and DOES WORK.
-
-
-  CVSTracker Overview
-  -------------------
-  The cvstracker plugin allows for some integration between CVS 
-commits and the bug tracker and task manager. So, for example, 
-when you commit, you can reference bug and task IDs in your 
-commit message and have the commit linked to the corresponding
-bug and task.
-
-  This works by having a script in the cvs server issue a POST 
-to the main website ( /plugins/cvstracker/newcommit.php )
-
-  See the plugins/cvstracker/README file for details. This 
-plugin is enabled by default in the gforge.sql database file. 
-As with the other plugins, you may manually place the config 
-files in /etc/gforge/plugins/cvstracker/ and uncomment the 
-cronjob in crontab.in.
-
-
-  PHP
-  ---
-  The cronjobs require the PHP CGI to be installed and the php.ini 
-file to be properly configured with your include_path OR edit the 
-crontab.in file to set your include path.
-
-  Mailman
-  -------
-
-  Mailman is needed to create and use mailing lists with gforge. 
-Mailman is frequently installed in /var/mailman/ and the sample 
-vhost shown below will work with this setup without any changes.
-
-  Cronjobs for mailman are located in cronjobs/mail/*
-
-  cronjobs/mail/mailing_lists_create.php is used obviously to 
-create new mailing lists. You may have to edit /etc/gforge/local.inc 
-to change the location of the mailman bin/ directory.
-
-  For all problems with mailman installation and use, contact 
-the mailman mailing lists for help.
-
-
-UPGRADING DATABASE - EXISTING INSTALL
--------------------------------------
-
-To migrate to a newer version of GForge, you must import 
-your old database, FRS files, mailing lists, cvs and svn trees
-into your new installation.
-
-1) Completely install your new system
-2) Move the mentioned files into place
-3) Import your old database
-4) go into the gforge/db directory and choose 'startpoint.php 4.0.2' 
-as the starting point of the installation (4.0.2 is an example)
-5) ./upgrade-db.php - this script will run the updates in order. 
-If any of them fail, it will prompt you to continue. Generally, 
-you should always continue. Most are minor or informational errors.
-
-
-WEB SETUP - MANUAL INSTALLATION
--------------------------------
-
-The following are sample commands commonly issued for a manual installation:
-
-tar -xjf gforge-X.X.tar.bz2
-cd gforge-X.X
-
-#
-#	BEFORE RUNNING THIS, determine your apacheuser/group 
-#	and pass it as an argument as shown below.
-#
-#	Argument 1: the main hostname you want to use.
-#	Argument 2: the apache user
-#	Argument 3: the apache group
-#	Argument 3: the IP address that you are listening on
-#
-./gforge-install.sh gforge.company.com apacheuser apachegroup
-
-Apache will need to have a line added to its httpd.conf:
-
-Include /etc/gforge/httpd.conf
-
-Restart apache when you are done editing the file so the 
-changes can be picked up.
-
-
-PHP setup
----------
-
-You may also add the include_path to the php.ini, as it will be
-necessary for your php cgi to run the cron jobs.
-
-register_globals = Off
-magic_quotes_gpc = Off
-file_uploads = On
-include_path = ".:/opt/gforge/gforge/:/opt/gforge/gforge/www/include/:/etc/gforge/"
-
-PHP CLI that is used by crontab.in may use different php.ini.  Find
-it by running the following command and add the above include_path
-directive there:
-
-$ /usr/bin/php -i | fgrep php.ini
-
-
-FRS - File Release System
--------------------------
-
-FRS has been radically simplified. Simply create a directory and make
-it owned by the webserver-user. Usually "chown -R apache:apache mydir"
-will do the trick.
-
-This directory will be referenced in the GForge Config File as $sys_upload_dir
-
-
-GForge Config File
---------------
-
-Edit the /etc/gforge/local.inc and set any specific variables 
-like sys_default_domain and any paths to files that are not right
-
-
-Site Admin
-----------
-
-Site admins are anyone who is an admin of group_id=1
-
-To give the first user "Site Admin" privileges, register a new user,
-and confirm it via the email link. Then enter the postgres command
-line and issue these commands:
-
-[gforge]# psql gforge
-
-psql> SELECT user_id FROM users WHERE user_name='******MY NEW USERNAME*********';
-
-The result of that query will be put into this next query:
-
-psql> insert into user_group (user_id,group_id,admin_flags) values (*****YOUR NEW NUMERIC USER ID*****,1,'A');
-
-
-Mail Aliases
-------------
-
-This alias was already added by the gforge-install script:
-
-noreply:        /dev/null
-
-
-PEER RATINGS
-------------
-
-Add yourself, and any others you wish, to the "Peer Ratings" project,
-which should be at /projects/peerrating/ on the website. Make yourself
-an "admin" of the project, and then proceed to "rate" other users on
-the website.
-
-Members of the "Peer Ratings" project, who are "admins" of the project
-become the first trusted users. This is the only way to prime the pump
-for the peer ratings system.
-
-
-CRON JOBS
----------
-
-Cron jobs are in the cronjobs/ directory and the README file contains
-a sample crontab. This gives you the basic cronjobs for updating
-certain statistics and data on the site.
-
-/cronjobs/cvs-cron/ contains scripts useful for creating blank cvs 
-trees and managing the /etc/groups /etc/passwd and /etc/shadow files.
-See /cronjobs/README.root for more info.
-
-/cronjobs/mail/ contains files useful for the creation of new mailing 
-lists in mailman and creating the /etc/aliases file.
-
-**************************************************************************
-WARNING!!! the following command will blow away any existing root crontab.
-**************************************************************************
-
-[root]# crontab cronjobs/crontab.in
-
-Now edit the paths to the cron scripts:
-
-[root]# crontab -e
-
-IMPORTANT!!!! - the cvs-cron/usergroup.php cron script will meddle 
-with your /etc/passwd, /etc/group, and /etc/shadow files. By default,
-this cron will save these files with a .new extension. You will have 
-to edit the cron script to remove the .new extension, but you must 
-make sure that it is properly generating your files or your server 
-could be unusable.
-
-Once you have manually run the usergroup.php file, look at the 
-/etc/*.new files and verify that they contain sensisble information.
-When you are confident they are right, you can edit usergroup.php 
-to remove the .new extension and uncomment the cronjobs.
-
-
-ADDITIONAL FILES
-----------------
-
-For XHTML validation against the DTD, the following files must be
-placed under the gforge/common/include/ directory:
-* xhtml-lat1.ent
-* xhtml-special.ent
-* xhtml-symbol.ent
-* xhtml1-strict.dtd
-* xhtml1-transitional.dtd
-They can be downloaded from http://www.w3.org/TR/xhtml1/dtds.html
-as tarball (xhtml1.tgz).
-
-Installation of xmlstarlet is also required.
-
-MOST COMMON PROBLEMS
---------------------
-
-Q: I get a blank page when I visit http://gforge.company.com/
-
-A: Most often you are missing the php-pgsql library that lets PHP
-talk to the postgres database. Find a php-pgsql RPM or recompile 
-php to have pgql support.
-
-If you're sure you have php-pgsql support, you can edit 
-common/include/database-pgsql.php and remove the @ symbol from
-this line:
-
-	$conn = @pg_connect( 
-
-So that it looks like:
-
-	$conn = pg_connect(
-
-This will let debug output dump to the screen and may let you find
-the problem. Search the forums for more solutions.
-
-
-Q: "Error Occurred In the Logger" or other database permission problems
-
-A: As stated in the installation instructions, the database must be created, 
-owned, and accessed by the gforge user. This user is the only one who will 
-have total acess to all the tables. Any other user would have to be specifically 
-granted permissions with the GRANT commands in postgres.
-
-
-Q: Reporting or time tracking doesn't work
-
-A: Go to the reporting tab and scroll down so you can choose 
-"Initialize/Rebuild Reporting Tables"
-
-Q: How do I upgrade my database?
-
-A: As stated above, you must apply the changes that are listed in date order 
-in the db/ directory to your database. Only the changes that are not already 
-in your old db/ directory should be applied, and they should be applied and 
-checked IN ORDER.
-
-
-Q: I'm getting an error about BaseLanguage.class not being found.
-
-A: Make sure your localization path is correctly specified in the local.inc 
-file and that it is readable AND writable by the apache user.
-
-
-Q: When I click on "/projects/" or "/users/" links, I get the source code
-instead of the page I expected.
-
-A: As shown in the example httpd.conf files above, you may have to switch 
-to using the <Files> or <Location> directives depending on your server
-version.
-
-
-Q: How do I backup GForge? 
-
-A: The only proper way to backup the gforge database is with pg_dump. 
-Any attempt to backup the filesystem while pgsql is running will result
-in a useless and corrupt backup. You can backup CVS trees using tar as 
-long as they are not actively and heavily used during the backup. 
-Mailman and the FRS uploads dir can also be backed up with tar.
-
-
-Q: Large uploads into FRS or the doc manager fail.
-
-A: Apache and the php.ini file need to have upload limits and possibly 
-memory limits increased.
+Please check
+https://fusionforge.org/plugins/mediawiki/wiki/fusionforge/index.php/Installing
diff --git a/src/NEWS b/src/NEWS
deleted file mode 100644
index f2548f7..0000000
--- a/src/NEWS
+++ /dev/null
@@ -1,198 +0,0 @@
-Release notes for FusionForge 5.2
----------------------------------
-
-FusionForge 5.2 is another incremental step over 5.1, with about 2600
-commits.
-
-There have been no in-depth rewrites this time, only a number of
-improvements to various parts of the code.  The document manager
-steadily grows in functionality, new widgets are available for users'
-personal pages, the SCM plugins grew new features for hooks (on
-supported systems), the trackers now offer a new view for roadmaps.
-New plugins include a Message plugin allowing to display a global
-message on the forge, and a MoinMoinWiki plugin.
-
-Many bugs were of course fixed during the course of this development
-cycle.
-
-As before, this release comes with packages for Red Hat and Debian
-systems (and derived distributions), as well as a rewritten installer
-script for users of other systems (and those who prefer more manual
-installations).  This release provides scripts to migrate what needs
-to be migrated to the new schemes (for the database schema).  Care
-should still be taken to check the results of these migrations, as a
-safety net.
-
-Release notes for FusionForge 5.1
----------------------------------
-
-FusionForge 5.1 is another incremental step over 5.0, although it's a
-large step in some regards, with about 3000 commits since version 5.0.
-
-The FusionForge team would like to dedicate this release to the memory
-of Alexandre Neymann, who passed away in March 2011.  Alexandre was
-one of the founding members of the FusionForge project in 2009, and
-one of its most active developers.  His death has meant a great loss
-to us all.
-
-On the user interface front, the project summary pages and users'
-personal pages are now built out of blocks called "widgets" that can
-be rearranged at will; these widgets (taken from Codendi) allow
-greater flexibility on how the pages look.  A new theme, called Funky,
-is now available, with a more modern feel (contributed by Capgemini).
-In the same field, the old help window has been replaced with a new
-unobtrusive tooltip system (Alcatel-Lucent).  A less visible aspect is
-that the generated webpages are now much closer to full XHTML
-compliance.
-
-Among the improvements in features, the document manager has been
-vastly rewritten (by Capgemini again), with more features and an
-improved usability; more improvements are planned for the next
-release, but this should bring the docman to something we're no longer
-ashamed of :-)
-
-Many improvements in the trackers have been contributed (by
-Alcatel-Lucent), including a progress bar and improvements in sorting.
-
-The permissions system has been enhanced and made more flexible, with
-the new ability to have several roles at once in the same project and
-to share roles across projects (contributed by Roland Mas as part of
-the Coclico project).
-
-New projects can now cloned from one of a set of configurable
-templates, thus allowing forges to have standard shapes for their
-common project organizations (Roland Mas, Coclico).
-
-New plugins have been written or merged from Codendi as part of the
-Coclico project: Mailman, Forumml, Hudson and SoapAdmin.  Not all are
-production-ready yet, but they're made available for the adventurous.
-Other new plugins include a gravatar plugin (Alain Peyrat) and a
-"blocks" plugin allowing to add free descriptions in several places
-(Alcatel-Lucent).
-
-Behind the scenes, the configuration system has also been made
-simpler, it now uses standard *.ini files that are taken into account
-immediately; the Apache configuration files are also splitted out into
-independent components, rather than a large generated file.  (Both by
-Roland Mas.)
-
-Another improvement making installation easier is the availability
-packages in RPM format for Red Hat Enterprise Linux and CentOS, in
-addition to the *.deb packages for Debian-based distributions.
-Installation from source is still supported, of course.
-
-As usual, this release provides scripts to migrate what needs to be
-migrated to the new schemes (in this case, for the database schema,
-the configuration variables and the existing permissions).  Care
-should still be taken to check the results of these migrations, as a
-safety net.
-
-Release notes for FusionForge 5.0
----------------------------------
-
-FusionForge 5.0 is still an incremental step over 4.8, but many
-changes have been made, some of which may require caution when
-upgrading.
-
-In particular, the rewriting of the version control subsystem created
-the possibility for many new VCS tools to be integrated, and indeed
-several new plugins were implemented (Arch, Bazaar, Darcs, Git and
-Mercurial).  To avoid crowding the chroot, all repositories are now
-hosted under a two-level subdirectory structure.  For instance, where
-you had a CVS repositories stored under
-/var/lib/gforge/chroot/cvsroot/<project>, you'll now have it under
-.../chroot/scmrepos/cvs/<project>.  As a consequence, you need to move
-the repositories by hand and/or add symlinks.  Previously existing
-symlinks will also have to be updated, as well as previously existing
-working copies obtained by users.
-
-Also, the Mediawiki plugin was rewritten to allow for each project to
-get their own independent wiki.  The wiki for project foo-bar is now
-stored in the plugin_mediakiki_foo_bar in the same database as the
-rest of the forge.  This means the data should be migrated from the
-existing database to this new location.  Depending on your setup and
-the amount of data involved, it might make sense to either cut and
-paste by hand or dump the tables and reload them in the new schema.
-
-On the internal side of things, access to the database has been
-converted from the db_query() abstraction layer to the
-db_query_params() one.  This means SQL queries are no longer built as
-strings with unwieldy and fragile escaping code, while ensuring no
-data coming from the user can be used for SQL injection attacks.  The
-db_query() function, while deprecated, is still present for the
-benefit of out-of-tree code that might use it.  It might be removed at
-some point in the future, so maintainers of local plugins or
-enhancements are encouraged to migrate their code to
-db_query_params().  For really complex queries that need to be built
-dynamically, there's also a db_query_qpa() abstraction, with a
-db_construct_qpa() method to manipulate "QPA" (query+params array)
-objects.
-
-On a more visible note, the default theme has been reworked to
-increase the accessibility of the web pages; this rewrite also brings
-better maintainability, easier customisation by CSS and more
-conformant XHTML.
-
-
-Release notes for FusionForge 4.8
----------------------------------
-
-FusionForge 4.8 is an incremental step from 4.7, and the changes are
-less far-reaching than the ones in 4.7.  Most notably, they include:
-- A new project classification system based on tags (with a tag cloud).
-- A new reporting page on the FRS displaying the number of downloads
-  per package.
-- The “Project List” can now display a list of all projects.
-- The “wiki” plugin now uses the latest PHPwiki code.
-
-The upgrade from 4.7 should be straightforward.
-
-
-Release notes for FusionForge 4.7
----------------------------------
-
-This is the first public release of FusionForge.  FusionForge is based
-on GForge, and started as an identical copy, with only a name change
-to avoid confusion with the proprietary versions of GForge (known as
-GForge Advanced Server or GForge AS).  As such, it benefits from
-mature code and known-good infrastructure, and builds on it for the
-future.
-
-This 4.7 release is focused on bringing the recent evolutions out to
-the community in an official stable release.  This should provide a
-solid base as a starting point for community-based development, making
-it easier for enhancements to be maintained.  The FusionForge name was
-chosen to reflect this: this is a community effort, and we hope to
-hear about your improvements.  Contributing these improvements would
-make their future long-term maintenance easier for everyone.
-
-Major changes since previous versions (of GForge) include:
-- Support for PHP5.
-- Support for PostgreSQL 8.x.
-- Translations are now managed by gettext.
-- Support for several configurations running on the same code.
-- Improved security, no need for PHP register_globals.
-- Available as full install CD.
-- New wiki plugins (using MediaWiki or phpWiki).
-- New online_help plugin.
-- New phpwebcalendar plugin.
-- New project hierarchy plugin.
-
-Things to keep in mind when installing:
-- FusionForge is based on GForge, and the renaming is quite recent.
-  So the code still contains lots of references to GForge.  This will
-  be fixed as time passes.
-- Full text search using the primitives provided by PostgreSQL 8.3
-  isn't quite complete yet.
-- Not all plugins are packaged for all distributions yet.
-
-Things to keep in mind when upgrading:
-- Since internationalisation was changed from a hand-made system to
-  standard gettext, locally customised translations will no longer
-  override standard ones.  This will be addressed in a future release.
-
-For more up-to-date information, please visit http://fusionforge.org/
-or http://fusionforge.fusionforge.org/ -- you can even join us on IRC
-from there!
-
- -- The FusionForge development team
diff --git a/src/rpm/fusionforge.spec.in b/src/rpm/fusionforge.spec.in
index 6adcab0..afc14d8 100644
--- a/src/rpm/fusionforge.spec.in
+++ b/src/rpm/fusionforge.spec.in
@@ -1,6 +1,6 @@
 Name: fusionforge
 Version: @rpm_version@
-Release: 0.2 at rpm_snapshot@%{?dist}
+Release: 1 at rpm_snapshot@%{?dist}
 Summary: Collaborative development tool
 
 Group: Development/Tools
@@ -278,7 +278,10 @@ This package controls the interaction between FusionForge and Mailman.
 
 
 %changelog
-* Fri May 30 2015 Roland Mas <lolando at debian.org> - @rpm_version at -0.2@rpm_snapshot@
+* Fri May 29 2015 Sylvain Beucler <beuc at beuc.net> - @rpm_version at -1@rpm_snapshot@
+- New upstream snapshot following the stable branch
+
+* Fri May 29 2015 Sylvain Beucler <beuc at beuc.net> - 6.0-1
 - New upstream release
 
 * Thu May 28 2015 Sylvain Beucler <beuc at beuc.net> - 6.0-0.2.rc4


hooks/post-receive
-- 
FusionForge



More information about the Fusionforge-commits mailing list