--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+<TITLE>rsync bug-tracking</TITLE>
+</HEAD>
+<!--#include virtual="header.html" -->
+
+<H2 align="center">rsync bug-tracking</H2>
+
+<p> Please use this checklist combined with the help on the
+<a href="issues.html">issues and debugging</a> page before
+reporting a bug. Thanks!
+
+<ul>
+
+<li> If you're not using the latest released version, please upgrade before
+reporting a bug.
+
+<li> If you're using the latest released version, consult the
+<a href="https://github.com/WayneD/rsync/blob/master/NEWS.md">NEWS file from the git repository</a> to see if what
+you're seeing has already been handled in the version under development.
+
+<li> It is also helpful to search the bug reports at both the new
+<a href="https://github.com/WayneD/rsync/issues">GitHub issues tracker</a> and the old
+<a href="https://bugzilla.samba.org/buglist.cgi?product=rsync&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED">bugzilla database</a>
+to see if the problem is already known.
+
+<li> See also the <a href="issues.html">issues and debugging</a> page to
+help you figure out if what you're seeing is a known bug and perhaps to
+help diagnose what is going wrong.
+
+<li> Discuss the bug on the
+<a href="https://lists.samba.org/mailman/listinfo/rsync">rsync mailing list</a>
+(which is at <tt>rsync@lists.samba.org</tt>) to help you figure out if what
+you're seeing is really a bug or a mistake.
+
+<li>There are several patches for features that are under consideration that
+can be found in the <a href="https://github.com/WayneD/rsync-patches">rsync-patches repo</a>.
+
+<li> If you haven't already done so, please take a couple of minutes to read Simon Tatham's
+<a href="https://www.chiark.greenend.org.uk/~sgtatham/bugs.html">advice on how to report bugs</a>.
+
+</ul>
+
+<p> To report a bug or make suggestions, use one of these methods:
+
+<ul>
+
+<li> The mailing list (mentioned above) is a good resource for discussing
+bugs and suggesting new features. It accepts patches (typically as MIME
+attachments), but for fixes is often easier to attach a patch to an
+appropriate GitHub issue report or use a pull request. Note that there is
+no mandate to use pull requests for patches, as that can be a pretty high
+bar of git know-how that not everyone needs to be familiar with.
+
+<li> If you'd like to see a bug-report or feature-request get officially noted,
+<a href="https://github.com/WayneD/rsync/issues">create an issue on GitHub</a>
+(this does require that you have created a GitHub account). If you want to
+stay abreast of what's going on with the issues, make use of the GitHub
+subscriptions to pick and choose what kind of notifications you want to
+receive (e.g. just a single issue, all issues, all rsync activity, etc.).
+
+</ul>
+
+<p> Thanks for helping out!
+
+<!--#include virtual="footer.html" -->
<HEAD>
<TITLE>rsync bug-tracking</TITLE>
</HEAD>
-<!--#include virtual="header.html" -->
-<H2 align="center">rsync bug-tracking</H2>
-
-<p> Please use this checklist combined with the help on the
-<a href="issues.html">issues and debugging</a> page before
-reporting a bug. Thanks!
-
-<ul>
-
-<li> If you're not using the latest released version, please upgrade before
-reporting a bug.
-
-<li> If you're using the latest released version, consult the
-<a href="https://download.samba.org/pub/unpacked/rsync/NEWS.md">NEWS file from the git repository</a> to see if what
-you're seeing has already been handled in the version under development.
-
-<li> It is also helpful to
-<a href="https://bugzilla.samba.org/buglist.cgi?product=rsync&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED">search the bugzilla database</a>
-to see if the problem is already known.
-
-<li> See also the <a href="issues.html">issues and debugging</a> page to
-help you figure out if what you're seeing is a known bug and perhaps to
-help diagnose what is going wrong.
-
-<li> Discuss the bug on the
-<a href="https://lists.samba.org/mailman/listinfo/rsync">rsync mailing list</a>
-(which is at <tt>rsync@lists.samba.org</tt>) to help you figure out if what
-you're seeing is really a bug or a mistake.
-
-<li>There are several patches for features that are under consideration that
-can be found in the <a href="https://gitweb.samba.org/?p=rsync-patches.git">rsync-patches repo</a>.
-
-<li> If you haven't already done so, please take a couple of minutes to read Simon Tatham's
-<a href="https://www.chiark.greenend.org.uk/~sgtatham/bugs.html">advice
-on how to report bugs</a>.
-
-</ul>
-
-<p> To report a bug or make suggestions, use one of these methods:
-
-<ul>
-
-<li> The mailing list (mentioned above) is a good resource for discussing
-bugs and suggesting new features. It accepts patches (typically as MIME
-attachments), but for fixes is often easier to attach a patch to an
-appropriate bugzilla report.
-
-<li> If you'd like to see a bug-report or feature-request get officially noted,
-<a href="https://bugzilla.samba.org/enter_bug.cgi?product=rsync">create a
-report via bugzilla</a> (this does require that you have created a bugzilla
-account, but that is a very simple process). All new items and changes to
-existing items generate email to the mailing list, so the list naturally stays
-up-to-date with what is happening in the bug-tracking database.
-
-</ul>
-
-<p> Thanks for helping out!
-
-<!--#include virtual="footer.html" -->
+<meta http-equiv="refresh" content="0;URL='https://rsync.samba.org/bugtracking.html'" />
<ul>
-<li> An html version of the <a href="https://download.samba.org/pub/rsync/rsync.1.html">rsync man page</a>.
+<li> An html version of the <a href="https://download.samba.org/pub/rsync/rsync.1">rsync man page</a>.
<li> An html version of the
-<a href="https://download.samba.org/pub/rsync/rsync-ssl.1.html">rsync-ssl man page</a>.
+<a href="https://download.samba.org/pub/rsync/rsync-ssl.1">rsync-ssl man page</a>.
<li> An html version of the
-<a href="https://download.samba.org/pub/rsync/rsyncd.conf.5.html">rsyncd.conf man page</a>.
+<a href="https://download.samba.org/pub/rsync/rsyncd.conf.5">rsyncd.conf man page</a>.
<li> The <a href="FAQ.html">FAQ</a> (frequently asked questions list).
<img src="https://github.com/WayneD/rsync/workflows/C%20CI/badge.svg">
</a></div>
-<h2>Source-code releases (tar files)</h2>
+<h2>Source-code releases</h2>
-<p>You can grab the latest source code tar file, its gpg signature, and other
-related files in a variety of ways:
+<p>You can grab the latest source code and other related files in a variety of ways:
<ul>
-<li><p>via <a href="https://download.samba.org/pub/rsync/">http</a> (the standard web-browser protocol)
+<li><p>The latest version is linked on the <a href="https://rsync.samba.org/">main page</a>.
-<li><p>via <i>anonymous rsync</i> from:
-<code><small>rsync://download.samba.org/rsyncftp/</small></code> (though this now requires an SSL helper script)
+<li><p>A directory listing of these latest files and various historical release and diff files
+are available via <a href="https://download.samba.org/pub/rsync/">this web page</a> and
+via <i>anonymous SSL rsync</i> using this command:
+<p><code><small>rsync-ssl rsync://download.samba.org/rsyncftp/</small></code></p>
-</ul>
+<li><p>You can also get .zip and .tar.gz versions of the various git repo's release
+tags via the <a href="https://github.com/WayneD/rsync/releases">rsync GitHub releases page</a>
+and the associated patches via the
+<a href="https://github.com/WayneD/rsync-patches/releases">rsync-patches GitHub releases page</a>.
+Keep in mind that these git-derived files do NOT come with the extra generated files that are included
+in the official release tar files.
+
+<li><p>You can browse the very latest source files, clone the source using git, or download a .zip file of the latest
+master branch from <a href="https://github.com/WayneD/rsync">rsync's GitHub page</a>.
-<p>Also, an unpacked copy of the latest development version can be
-<a href="https://download.samba.org/pub/unpacked/rsync/">browsed on the web</a> or obtained via
-<i>anonymous rsync</i>, as described in the Source Repository section.
+<li><p>The <a href="https://git.samba.org/?p=rsync.git">Samba git repo</a> is also available,
+though it might lag behind the GitHub repo every now and then.
<h2>The GPG Signing Key</h2>
-The GPG signing key that is used to sign the release files and the postings to
-the rsync-announce mailing list is available from the public pgp key-server
+The GPG signing key that is used to sign the release files is available from the public pgp key-server
network. If you have automatic key-fetching enabled, just running a normal
"gpg --verify" will grab my key automatically.
Or, feel free to grab <a href="https://opencoder.net/WayneDavison.key">the gpp
</ul>
-<h2>The latest version via GitHub</h2>
-
-<p>Rsync's <a href="https://github.com/WayneD/rsync">GitHub page</a> has an
-easy way to grab the very latest source as a zip file (via the green button).
-Or, updating a git repository can automatically merge your local changes with
-our version. However, keep in mind that the git version does not come with
-various generated files that are present in a release tar file, such as the man
-pages, configure.sh, etc. <b>but</b> there is a way to fetch them if you can't
-generate them (see below).
-
-<h2>Source repository</h2>
+<h2>Git source vs Release files</h2>
-<p> The rsync development tree is publicly available by various methods so that
-you can try out the latest changes and give feedback to the developers.
+The release tar files come with a few generated files that are not checked in to git.
+These mainly include the man pages and the configure related files. To make use of
+the git-derived files you will need autoconf, autoheader, and a version of python3
+that has the commonmark lib (OR cmarkgfm). If you have trouble with setting up the
+those required files, you can try running "./prepare-source fetchgen" to grab the
+very latest generated files that were created from the latest commit into the master
+branch.
<p> <b>Note:</b> Since the source repository is a work in progress it may, at
times, not compile or fail in various ways, though it is usually pretty good.
-<p>Anyone can browse the development history through
-<a href="https://gitweb.samba.org/?p=rsync.git">the Samba-hosted gitweb</a>
-page or on its <a href="https://github.com/WayneD/rsync">GitHub home</a>.
-
-<p>You may also use the git version-control system to check out the latest
-development version, especially if you want to make local changes. The
-following command will check-out the latest version into a directory named
-"rsync":
-
-<blockquote><pre>git clone git://git.samba.org/rsync.git
-git clone https://github.com/WayneD/rsync.git</pre></blockquote>
-
-<p>You'll also need
-autoconf and autoheader installed for the "prepare-source" command to succeed
-unless you use either the "fetch" or "fetchgen" option (these options can only
-fetch the most recent generated file that goes with the latest git version):
-
-<blockquote><pre>cd rsync
-./prepare-source # might need fetch or fetchgen arg</pre></blockquote>
-
-<p>Updating your git checkout with the latest source is very easy:
-
-<blockquote><pre>git pull</pre></blockquote>
-
-<p>Those wanting to just obtain the latest source without the entire git
-repository can either use a zip (see above)
-or use an <i>anonymous rsync</i> copy of the unpacked source files:
-
-<blockquote><pre>rsync-ssl -av --exclude=.git/ rsync://download.samba.org/ftp/unpacked/rsync /dest/dir/</pre></blockquote>
-
<h2>Source repository patches</h2>
-<p>There are also various patch files in the "rsync-patches.git" repository that
+<p>There are also various patch files in the "rsync-patches" repository that
represent either some work-in-progress features or features that are considered
-to be a little too fringe-interest for the main release. You can use
-gitweb to <a href="https://gitweb.samba.org/?p=rsync-patches.git">browse the
-latest patches</a>. Each branch in the patches repository matches the branch
-of the same name in the <a href="https://gitweb.samba.org/?p=rsync.git">main
-repository</a>, so "master" matches "master", and "b3.0.x" matches "b3.0.x".
-
-<p>Use the
-<a href="https://gitweb.samba.org/?p=rsync-patches.git;a=tree;h=refs/heads/master;hb=master">tree
-view of the master branch</a> or the
-<a href="https://gitweb.samba.org/?p=rsync-patches.git;a=tree;h=refs/heads/b3.0.x;hb=refs/heads/b3.0.x">tree
-view of the b3.0.x branch</a> to get to the contents of individual files (i.e. click
-on the "raw" link for the file you want).
-
-<p>Each release of rsync also has an associated sync-patches-VERSION.tar.gz
-file with the patches as they existed at the time of the release.
+to be a little too fringe-interest for the main release. See the github link
+above for how to look around at what is available, or snag a release tar file.
+The maintainer like to put the rsync-patches dir into his rsync checkout as a
+directory named "patches" and has some helper scripts for how to use local git
+branches to test and update the diffs.
<!--#include virtual="footer.html" -->
or (3) a version of rsync older than 2.6.6, please see the
<a href="security.html" class=security>rsync security advisory page</a>.</i>
-<!--
-
-<p><hr>
-<h3>The latest development version</h3>
-
-<p>If you're curious about the changes going into the next version of rsync,
-you can view the <a href="https://download.samba.org/pub/unpacked/rsync/NEWS.md">NEWS file from the source
-repository</a> to see a summary of the current changes. Also available are the
-<a href="https://download.samba.org/pub/rsync/nightly/rsync.1">repository's rsync manpage</a> and the
-<a href="https://download.samba.org/pub/rsync/nightly/rsyncd.conf.5">repository's rsyncd.conf
-manpage</a>. See the <a href="/download.html">download page</a> for more info
-on grabbing the development version.
-
--->
-
<p><hr>
-<h3>Rsync version 3.2.0pre2 released</h3>
-<i class=date>June 15th, 2020</i>
+<h3>Rsync version 3.2.0 released</h3>
+<i class=date>June 19th, 2020</i>
-<p>Rsync version 3.2.0pre2 is now available for release testing. This is a feature relase with lots of bug-fixes.
-If no blocking issues are found, this will be released as 3.2.0 soon.
+<p>Rsync version 3.2.0 has been released.
+This release has a good number of a few new features and various bug fixes.
-<p>For a full list of what changed since 3.1.3, see the
-<a href="https://download.samba.org/pub/rsync/src-previews/rsync-3.2.0pre2-NEWS">NEWS file</a>.
+<p>See the <a href="https://download.samba.org/pub/rsync/src/rsync-3.2.0-NEWS">release NEWS</a>
+for the details of what changed since 3.1.3.
The latest manpages are also available for
<a href="https://download.samba.org/pub/rsync/rsync.1">rsync</a>,
-<a href="https://download.samba.org/pub/rsync/rsync-ssl.1">rsync-ssl</a> and
+<a href="https://download.samba.org/pub/rsync/rsync-ssl.1">rsync-ssl</a>, and
<a href="https://download.samba.org/pub/rsync/rsyncd.conf.5">rsyncd.conf</a>.
<p>The source tar is available here:
-<b><a href="https://download.samba.org/pub/rsync/src-previews/rsync-3.2.0pre2.tar.gz">rsync-3.2.0pre2.tar.gz</a>
-(<a href="https://download.samba.org/pub/rsync/src-previews/rsync-3.2.0pre2.tar.gz.asc">signature</a>),</b>
+<b><a href="https://download.samba.org/pub/rsync/src/rsync-3.2.0.tar.gz">rsync-3.2.0.tar.gz</a>
+(<a href="https://download.samba.org/pub/rsync/src/rsync-3.2.0.tar.gz.asc">signature</a>),</b>
with a tar file of the "patches" directory released in a separate file:
-<b><a href="https://download.samba.org/pub/rsync/src-previews/rsync-patches-3.2.0pre2.tar.gz">rsync-patches-3.2.0pre2.tar.gz</a>
-(<a href="https://download.samba.org/pub/rsync/src-previews/rsync-patches-3.2.0pre2.tar.gz.asc">signature</a>),</b>
+<b><a href="https://download.samba.org/pub/rsync/src/rsync-patches-3.2.0.tar.gz">rsync-patches-3.2.0.tar.gz</a>
+(<a href="https://download.samba.org/pub/rsync/src/rsync-patches-3.2.0.tar.gz.asc">signature</a>),</b>
and the diffs from version 3.1.3 are available here:
-<b><a href="https://download.samba.org/pub/rsync/src-previews/rsync-3.1.3-3.2.0pre1.diffs.gz">rsync-3.1.3-3.2.0pre1.diffs.gz</a>
-(<a href="https://download.samba.org/pub/rsync/src-previews/rsync-3.1.3-3.2.0pre1.diffs.gz.asc">signature</a>)</b>
-and
-<b><a href="https://download.samba.org/pub/rsync/src-previews/rsync-3.2.0pre1-3.2.0pre2.diffs.gz">rsync-3.2.0pre1-3.2.0pre2.diffs.gz</a>
-(<a href="https://download.samba.org/pub/rsync/src-previews/rsync-3.2.0pre1-3.2.0pre2.diffs.gz.asc">signature</a>)</b>
+<b><a href="https://download.samba.org/pub/rsync/src-diffs/rsync-3.1.3-3.2.0.diffs.gz">rsync-3.1.3-3.2.0.diffs.gz</a>
+(<a href="https://download.samba.org/pub/rsync/src-diffs/rsync-3.1.3-3.2.0.diffs.gz.asc">signature</a>)</b>.
<p><hr>
<h3>Rsync version 3.1.3 released</h3>
<p>See the <a href="https://download.samba.org/pub/rsync/src/rsync-3.1.3-NEWS">release NEWS</a>
for the details of what changed since 3.1.2.
-The latest manpages are also available for both
-<a href="https://download.samba.org/pub/rsync/rsync.1">rsync</a> and
-<a href="https://download.samba.org/pub/rsync/rsyncd.conf.5">rsyncd.conf</a>.
-
-<p>The source tar is available here:
-<b><a href="https://download.samba.org/pub/rsync/src/rsync-3.1.3.tar.gz">rsync-3.1.3.tar.gz</a>
-(<a href="https://download.samba.org/pub/rsync/src/rsync-3.1.3.tar.gz.asc">signature</a>),</b>
-with a tar file of the "patches" directory released in a separate file:
-<b><a href="https://download.samba.org/pub/rsync/src/rsync-patches-3.1.3.tar.gz">rsync-patches-3.1.3.tar.gz</a>
-(<a href="https://download.samba.org/pub/rsync/src/rsync-patches-3.1.3.tar.gz.asc">signature</a>),</b>
-and the diffs from version 3.1.2 are available here:
-<b><a href="https://download.samba.org/pub/rsync/src-diffs/rsync-3.1.2-3.1.3.diffs.gz">rsync-3.1.2-3.1.3.diffs.gz</a>
-(<a href="https://download.samba.org/pub/rsync/src-diffs/rsync-3.1.2-3.1.3.diffs.gz.asc">signature</a>)</b>.
<p><hr>
<h3>Rsync version 3.1.2 released</h3>
git.samba.org / rsync-web.git / commitdiff