Phil Crooker | 30 May 08:38 2016
Picon

view log problem with path authorisation

I posted this query to the users list but had no response. To me, this is not behaviour I would expect.

Authenticated users with read or r/w authorisation are unable to view logs, eg:

    # svn --username whatever --password xxxxx log svn://svn/repos/project/yada.txt
    svn: Item is not readable

After authentication, users are able to check out files, etc, just not see the logs. For anyone to view logs, I must grant anonymous read access in authz and then it works:

    [/]
        * = r 

I've seen this reported earlier but no answer:

    http://svn.haxx.se/users/archive-2011-02/0141.shtml
    http://stackoverflow.com/questions/6651997/svn-show-log-not-working


Is this a bug or is it expected behaviour?


thanks, Phil

-- --

Please consider the environment before printing this e-mail

This message from ORIX Australia may contain confidential and/or privileged information. If you are not the intended recipient, any use, disclosure or copying of this message (or of any attachments to it) is not authorised. If you have received this message in error, please notify the sender immediately and delete the message and any attachments from your system. Please inform the sender if you do not wish to receive further communications by email.

The ORIX Australia Privacy Policy outlines what kinds of personal information we collect and hold, how we collect and handle it and your rights in regards to your personal information. Our Privacy Policy is available on our website.

We do not accept liability for any loss or damage caused by any computer viruses or defects that may be transmitted with this message. We recommend you carry out your own checks for viruses or defects.

Pavel Lyalyakin | 26 May 22:15 2016

`svn help` output in SVN 1.8 and 1.9

Hello,

I'm reading through the nightly SVNBook 1.8 and make more or less
necessary changes to complete it and begin the work on SVNBook 1.9.
I've just noticed that the output of `svn help` is slightly different
in SVN 1.8 and 1.9 command-line clients.

SVN 1.8 shows the version number (take a look at the second line):
[[[
usage: svn <subcommand> [options] [args]
Subversion command-line client, version 1.8.13.
Type 'svn help <subcommand>' for help on a specific subcommand.
]]]

SVN 1.9 does not show the version number:
[[[
usage: svn <subcommand> [options] [args]
Subversion command-line client.
]]]

Was there any special reason to hide the version number here? Or is it a bug?

--

-- 
With best regards,
Pavel Lyalyakin
VisualSVN Team

Stefan | 16 May 15:44 2016
Picon

[PATCH] clean up release notes - pass 3

Hi,

the attached patch fixes some remaining XHTML validation issues in the release notes.

This is expected to be the last patch for this run. The remaining errors
seem to be related to the use of HTML5-specific features (error, since
the DOCTYPE points to XHTML 1.1) and warnings in some files since they
also contain a BOM (which is said to be potentially problematic with
some rather old browsers).
I'm not planning to touch any of these atm.

[[[
Some more tweaks to make the release XHTML 1.1 standard compliant.

* docs/release-notes/1.7.html
  (atomic-revprops): properly encode & in href

* docs/release-notes/1.8.html
  (auto-reintegrate): close p-tag before ul
  (fsfs-stats): same
  (svnlook-diff): same
  (svn-diff): same
  (issues): rename section id so it doesn't start with a number
]]]

Regards,
Stefan

Attachment (smime.p7s): application/pkcs7-signature, 3564 bytes
Stefan | 16 May 13:19 2016
Picon

[PATCH] clean up release notes

Hi,

following patch fixes some more W3C validation issues inside the release
notes

[[[
Make the release notes more compliant with the XHTML 1.1 standard.

* docs/release-notes/1.6.html
  (Testsuite fails): add missing closing p-tag

* docs/release-notes/1.7.html
  (svn diff can show git-style diff annotations): close p-tag before ul

* docs/release-notes/1.8.html
  (Skelta style updates are now the default): drop invalid p-section

* docs/release-notes/1.9.html
  (fsvnadmin pack): correct typo (missing / for closing tag)
  (svnadmin setrevprop --transaction): fix incorrect closing tag
]]]

Regards,
Stefan

Attachment (w3c-validation.patch): text/x-diff, 6282 bytes
Attachment (smime.p7s): application/pkcs7-signature, 3564 bytes
Stefan | 15 May 02:00 2016
Picon
Picon

[PATCH] add FAQ section about "bad request" errors

Hi,

following patch adds a new entry to the FAQ's trouble shooting section, 
documenting the known problem with large headers, exceeding Apache 
httpd's LimitRequestFieldSize setting.

[[[
Document known issue about long header sections causing problems with 
Apache httpd.

* docs/faq.html
   (Table of Contents): add link to new http-400 section
   (http-400): new trouble shooting section about http-400-error
]]]

Regards,
Stefan

Attachment (faq.html.patch): text/x-diff, 2676 bytes
Stefan | 15 May 01:21 2016
Picon
Picon

[PATCH] clean up 1.9 release notes - part 2

Hi,

following patch fixes two more minor issues in the 1.9 release notes

[[[
Clean up 1.9 release notes html to improve XHTML1.1 compliance a bit.

* docs/release-notes/1.9.html
   (format7-comparison): add missing closing tr-tag
   (svnfsfs-issues): move pre-section into li-section
]]]

Regards,
Stefan

Attachment (1.9.html.patch): text/x-diff, 1484 bytes
Stefan | 15 May 01:13 2016
Picon
Picon

[PATCH] troubleshooting http-pipelining for 1.9 release notes

Hi,

following patch adds the troubleshooting section to the 1.9 release 
notes including a section about lock/unlock issues related to 
old/ancient proxies.

I'd appreciate, if the actual description could be reviewed by someone 
with a deeper knowledge on the underlying issue than I have.

[[[
Add a troubleshooting section to 1.9 to help users tracing down problems 
related to proxies when locking/unlocking multiple files.

* docs/release-notes/1.9.html
   (troubleshooting): Add new section including http-pipelining issue
                      description.
]]]

Regards,
Stefan

Attachment (1.9.html.patch): text/x-diff, 3864 bytes
Stefan | 14 May 22:52 2016
Picon
Picon

[PATCH] clean up 1.9 release notes

Hi,

following patch removes a commented out section (left over from the 
pre-release time) and adds a missing closing p-tag.

[[[
Clean up 1.9 release notes html to improve XHTML1.1 compliance a bit.

* docs/release-notes/1.9.html
   (Compatibility Concerns): Drop commented out section.
   (FSFS improvements): add missing closing p-tag
]]]

Regards,
Stefan

Attachment (1.9.html.patch): text/x-diff, 2242 bytes
Stefan Fuhrmann | 13 May 05:44 2016
Picon

Python 3 support

Hi all,

Under Linux, /trunk has now support for running our test suite
with Python 3. I tested various parameter combinations, ra layers
as well as backends and I call it quits.

On Windows, Python 3 will not work b/c win-tests.py has not been
adapted. Furthermore, there are fundamental issues with the EOL
handling that may be require significant work. Any other platform
that does not use '\n' natively may be affected as well.

Scripts outside /build and /subversion/tests have been partially
adapted (as part of global search and replace) but not received
any testing. We might either keep, improve or revert them.

-- Stefan^2.

Stefan | 12 May 02:27 2016
Picon
Picon

[PATCH] Troubleshooting section for release template

Hi,

the idea of adding a troubleshooting section to release notes was 
discussed shortly on IRC a few days ago between brane and myself (Bert 
was following the discussion too) in light of a user who ran into 
problems due to (presumably) some proxy issue with http-pipelining support.

To him, it seemed like it was a bug in SVN 1.9, since the same operation 
(locking multiple files) worked fine using SVN 1.8.

Ivan pointed out it's most likely a problem with the proxy (maybe it's 
not correctly supporting http pipelining).

Looking for a way to record such known issues, we concluded on IRC that 
the best way would be to document these things in a new troubleshooting 
section on the release notes pages.

Following is a patch against 1.10.html with the suggested section 
layout. If that passes, I'm planning to provide another patch for the 
1.9 release notes covering problems due to the increased 
http-header-section size and issues with proxies (the two known cases 
atm which could cause users to run into problems when using 1.9 which 
wouldn't be encountered using 1.8).

[[[
Add a new troubleshooting section covering known issues which can be
encountered with the new version but are not directly bugs in Subversion
itself.

* docs/release-notes/1.10.html
   (troubleshooting): Add new section including a placeholder entry.
   (news): Add link to new troubleshooting section.
]]]

Regards,
Stefan
Vincent Lefevre | 8 May 15:55 2016
Picon

random, unpredictable sort of svn diff

Hi,

The output of "svn diff" is still in random order (not even
pseudo-random, completely unpredictable). There had been discussions
in the past to fix this, e.g.

  https://mail-archives.apache.org/mod_mbox/subversion-users/201203.mbox/%3C1332298973.3028.17.camel <at> segulix%3E

What's the status?

I haven't found a bug on this subject on Jira.

--

-- 
Vincent Lefèvre <vincent <at> vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


Gmane