subversion

Checkout Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates

Changeset 1864950 is being indexed.

Remove a step for updating the 'upcoming changes' branch for a new minor release.

Reverts r1864042, as it is now done a different way:

https://issues.apache.org/jira/browse/SVN-4823 "site: upcoming.py script

should automatically show changes for the latest stable branch".

* STATUS: Nominate r1864440.

* STATUS: Nominate r1864440.

Fix 'svn patch' setting UNIX permissions to 0600 on patched files with props.

* subversion/libsvn_client/patch.c

(init_patch_target): Use the working copy's own temp directory to store

temporary files for patching, instead of using the system-wide temp dir.

With a system-wide dir, permission paranoia in svn_io_open_unique_file3()

may kick in and result in patched files with permissions not matching the

umask. Generally, any temp files that may end up as user-visible files

in the working copy should be created in the working copy's temp dir.

Reported by: Doug Robinson at wandisco com

* upcoming.part.html: Automatically regenerated
* publish/.message-ids.tsv: Automatically regenerated.
site: Auto-update the link the the current release's STATUS file to always

point to the current stable branch.

* publish/docs/release-notes/index.html

(#upcoming-patch-release): Move a sentence from here..

* publish/upcoming.part.html: .. to here, which is automatically generated ..

* tools/generate-upcoming-changes-log.sh: .. here.

* tools/upcoming.py

(Version.__str__): New.

(get_reference_version): Add comment.

* upcoming.part.html: Automatically regenerated
site: tools/upcoming.py: Remove the last remnant of working copy usage: use of

the short URL syntax.

For SVN-4823.

* site/tools/upcoming.py:

(REPOS_ROOT_URL): New.

(copyfrom_revision_of_previous_tag_of_this_stable_branch):

Don't use the short URL syntax.

(get_merges_for_range): Change argument type.

(main): Update caller.

* upcoming.part.html: Automatically regenerated
site: upcoming.py: When cwd is not a stable branch working copy root, show

changes of the newest branch.

Fixes SVN-4823.

* site/tools/upcoming.py

(__doc__): Expand.

(get_reference_version__from_working_copy): Add TODO.

(get_reference_version__latest_stable_release): New.

(get_reference_version): New.

(main): Update caller.

site: upcoming.py: Continue removing uses of the cwd.

No functional change.

* site/tools/upcoming.py

(relative_url): Remove.

(get_merges_for_range): Change signature.

Stop calling relative_url(), which, incidentally, removes a fork() from

each iteration of the loop.

(main): Instead of calling relative_url(), just compute the URL directly.

* site/tools/upcoming.py

(get_reference_version__from_working_copy): New function, split from..

(copyfrom_revision_of_previous_tag_of_this_stable_branch): .. here.

(main): Update caller.

site: upcoming.py: Refactor the computation of an interim quantity (the tag

that defines the older end of the 'svn log' output to generate).

No functional change.

In preparation for SVN-4823.

* site/tools/upcoming.py

(collections): Import.

(Version, versions_on_dist_release): New.

(copyfrom_revision_of_previous_tag_of_this_stable_branch):

Refactor with the new helper.

* site/tools/upcoming.py: Fix syntax error.

Follow-up to r1864159.

Follow-up to r1864159:

* site/tools/upcoming.py

(relative_url): Add an optional parameter that will be needed when

this script learns to run without a working copy, as requested in SVN-4823.

* site/tools/upcoming.py

(get_merges_for_range): Add an optional parameter that will be needed when

this script learns to run without a working copy, as requested in SVN-4823.

(copyfrom_revision_of_previous_tag_of_this_stable_branch): Add escaping, though

it's unlikely to ever be needed here.

* site/tools/upcoming.py

(get_merges_for_range): Update docstring to match current implementation.

* tools/buildbot/slaves/bb-openbsd/svncheck.sh: Stop testing BDB.

* tools/dev/unix-build/Makefile.svn: Provide a way to override repository

backends tested during 'make svn-check'.

* upcoming.part.html: Automatically regenerated
* site/tools/upcoming.py

(__doc__): Expand.

Disclose CVE-2018-11782 and CVE-2019-0203.
    • ?
    /site/publish/security/CVE-2018-11782-advisory.txt
* upcoming.part.html: Automatically regenerated
* upcoming.part.html: Automatically regenerated
Document a step for updating the 'upcoming changes' branch for a new minor release.
Make the 'upcoming changes' script tell which branch it's reporting, and remove that info from the prose.
* upcoming.part.html: Automatically regenerated
* STATUS: Nominate r1864025.
fsfs, fsx: Make an error message clearer to developers.

* subversion/libsvn_fs_fs/low_level.c

(svn_fs_fs__parse_footer),

* subversion/libsvn_fs_x/low_level.c

(svn_fs_x__parse_footer):

Make the output radix explicit, so the values aren't mistaken for decimal.

(Actually, I wonder why the values aren't printed in decimal to begin with.)