Re: URL's of revisions on http://svn.apache.org/viewvc/

[Vincent Lefevre]

On 2015-08-19 23:36:15 +, Daniel Shahaf wrote:
> Stefan Sperling wrote on Wed, Aug 19, 2015 at 18:35:55 +0200:
> > On Wed, Aug 19, 2015 at 05:36:16PM +0200, Vincent Lefevre wrote:
> > > Hi,
> > > 
> > > It seems that in the past, URL's of the following form were used:
> > > 
> > >   http://svn.apache.org/viewvc?view=revision&revision=r1686988
> > > 
> > > This now gives an "Invalid revision" error / 404 Not Found. The URL's
> > > now have the following form:
> > > 
> > >   http://svn.apache.org/viewvc?view=revision&revision=1686988
> > > 
> > > This is quite annoying to break all the past links...
> > 
> > Wrong list. Talk to ASF infra.
> 
> (see https://www.apache.org/dev/infra-contact)
> 
> Support for leading "r" in revnums was implemented upstream in issues
> #441 and #488.  The implementation was a one-line patch, which should be
> trivial to cherry-pick onto Infra's ViewVC installation if upgrading the
> viewvc installation to a release that includes those patches isn't an
> option.

Thanks. I've sent a mail to infrastructure.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: detach.py script isn't updated for 1.8/1.9

[Julian Foad]

Stefan Sperling wrote:
> On Wed, Aug 19, 2015 at 10:34:19PM +0200, Stefan wrote:
>> In the light of this script surviving the release of 1.10 I'd though suggest
>> to add the known issue as a comment to the top of the file:
>>
>> # Note: This script has a hardcoded check for a 1.7 WC format. It won't work
>> # with 1.8+ WCs.
>> # As stated in the  exception it's unfinished and not ready for use.

I added this note, with a bit more detail and a link to this thread,
in r1696722.

> I would still prefer just deleting the script.
> Anyone sufficiently interested can find it in our repository history.

I deleted it in r1696742. The note will be useful to anyone who
resurrects the latest (deleted) version.

Other observations:

We first included this script in the 1.8.0 release, and listed it in
the 'CHANGES' file as a "new w/c subtree duplication tool". Oops!

This script is mentioned as a temporary solution in issue #2884,
http://subversion.tigris.org/issues/show_bug.cgi?id=2884 "Implement
'svn detach' for copying partial working copies".

- Julian

Re: upcoming MaxSVN Subversion distribution (for review)

[Branko Čibej]

On 18.08.2015 02:02, Stefan wrote:
> Hi,
>
> as mentioned on IRC already a few weeks ago, I'm about to release a
> Windows distribution of Subversion named 'MaxSVN'.
> I'm looking here for feedback/concerns/requests/requirements from any
> of the Subversion developers for publishing this distribution.
> Especially with regards (but not limited) to the readme-file contained
> in the distribution and the introduction of the product on the
> webpage. Please note that none of your concerns/requests need to be
> seconded by any legal statement. Just name whatever you think should
> be added/removed/changed and I'll make sure it gets done.


One minor nit: the readme.txt file on the site is in Windows CP1252, but
your HTTP server doesn't tell the browser that; my browser defaults to
UTF-8, so in stead of the ® symbols I just see �.

Also, the lines in that file are very long, which makes it sort of hard
to read.

-- Brane

RE: JavaHL, 1.9: "Bad file descriptor", "Stream doesn't support thiscapability" errors

[bert]

Hi Thomas,

The Subversion version of the fix is nominated for 1.9.1
[[
+ * r1696222, r1696225
+   Implement polling on named pipes on Windows to resolve svn+ssh:// problems
+   Justification:
+ Without this patch operations like checkout just fail with an error.
+ This is a regression as older Subversion releases ignored the error.
+   Votes:
]]

Apr just returns EBADF on any attempt to poll on a file or pipe on Windows. 
This workaround on the Subversion side makes us support polling on pipes. (In 
Subversion < 1.8 we always assumed that there was no data waiting, because we 
never bothered to check for an error)

The apr version of the patch is harder than I expected, because the poll 
function supports many flags of which we can really only implement one new 
variant, that can’t really be combined with any other flags.


We need one more vote on this, before we can start the release process on 1.9.1.

I would hope we can also get r1696695 in the release, as that problem appears 
to break Subversion for at least some Linux distributions.



We might want to consider also fixing the polling in 1.8 (and 1.7?), as that 
would allow exiting much earlier when a commit fails. Currently Subversion 
(when using svn+ssh:// on Windows) just goes on trying to commit on Windows and 
only notices that svnserve returned an error when done.


Bert

Sent from Mail for Windows 10



From: Thomas Singer
Sent: donderdag 20 augustus 2015 08:23
To: dev@subversion.apache.org
Subject: Re: JavaHL, 1.9: "Bad file descriptor", "Stream doesn't support 
thiscapability" errors


Hi Bert,

> I'll see if I can properly fix this (preferably in both Subversion and Apr), 
> without reverting to just ignoring errors.

Did you have any success fixing it yet? Is there already a bug entered 
in the issue tracker? I'd rate it as blocker priority.

--
Best regards,
Thomas Singer
=
syntevo GmbH
http://www.syntevo.com
http://www.syntevo.com/blog

Re: detach.py script isn't updated for 1.8/1.9

[Stefan Sperling]

On Wed, Aug 19, 2015 at 10:34:19PM +0200, Stefan wrote:
> >Stefan  writes:
> >
> >>2. add some documentation to the script to point out it's an
> >>experiment and can be used as a starting point, if someone needs the
> >>functionality and cannot use a different approach
> >When run the only thing the script does is print:
> >
> >   Exception: This script is unfinished and not ready to be used on live 
> > data.
> >   Trust us.
> >
> >I don't really see how we could make it clearer.
> Oops. That part I overlooked. Yes this certainly reduces the issue I
> initially saw here and therefore I guess unless s/o supports solution 1 or
> 3, nothing would be worth to add for no 2.
> 
> In the light of this script surviving the release of 1.10 I'd though suggest
> to add the known issue as a comment to the top of the file:
> 
> # Note: This script has a hardcoded check for a 1.7 WC format. It won't work
> # with 1.8+ WCs.
> # As stated in the  exception it's unfinished and not ready for use.

I would still prefer just deleting the script.
Anyone sufficiently interested can find it in our repository history.