On Sun, May 05, 2024 at 11:20:28AM +0200, Daniel Sahlberg wrote:
> What about this new topic for #svn?
>
> [[[
> The Apache® Subversion® version control system (
> https://subversion.apache.org/) | Read the book: http://www.svnbook.org/ |
> FAQ: https://subversion.apache.org/faq.html | This
On Sat, May 04, 2024 at 09:24:58PM +0200, Daniel Sahlberg wrote:
> Hi,
>
> I’m personally not an IRC user but I try to keep an eye on the IRC logs.
> For personal reasons I haven’t had time to do since the start of the year
> but I spent some time tonight to browse the archives.
>
> Since
On Sun, Mar 10, 2024 at 07:59:38PM -0400, Nathan Hartman wrote:
> There is at least a week before I can begin working on it, so there is
> time for the dev community to respond.
I will be around to help with testing/signing. Thanks for picking this up!
On Wed, Jan 10, 2024 at 09:44:51AM +0100, Johan Corveleyn wrote:
> Interesting discussion. I agree it should at least be documented, and
> perhaps be made a bit more clear from the output of 'revert' (but not
> sure how far we can go without breaking compat). Changing the current
> behavior is
On Sat, Dec 09, 2023 at 11:00:00AM -0700, Nathan Hartman wrote:
> The 1.14.3 release artifacts are now available for testing/signing.
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there.
>
> Thanks!
Summary: +1 to release
Tested:
On Sat, Nov 11, 2023 at 05:08:28PM +0100, Daniel Sahlberg wrote:
> ne_openssl.o isn't built, the build fails already when running configure on
> neon.
Can you show the cofigure log? E.g. via paste.apache.org?
I am also in #svn-dev on Libera IRC if you want to chat there.
On Sat, Nov 11, 2023 at 04:34:07PM +0100, Stefan Sperling wrote:
> On Sat, Nov 11, 2023 at 04:23:52PM +0100, Daniel Sahlberg wrote:
> > As for the original problem, updating to the latest version of the Neon
> > library doesn't help, I still get the same linking e
On Sat, Nov 11, 2023 at 04:23:52PM +0100, Daniel Sahlberg wrote:
> As for the original problem, updating to the latest version of the Neon
> library doesn't help, I still get the same linking error. I''m sure there
> is something fishy with my Debian install...
Which libssl is your build trying
On Sat, Nov 11, 2023 at 04:07:52PM +0100, Stefan Sperling wrote:
> On Sat, Nov 11, 2023 at 04:00:58PM +0100, Stefan Sperling wrote:
> > On Sat, Nov 11, 2023 at 03:53:09PM +0100, Stefan Sperling wrote:
> > > If neon requests OPENSSL_API_COMPAT 0x1000L and also calls
>
On Sat, Nov 11, 2023 at 04:00:58PM +0100, Stefan Sperling wrote:
> On Sat, Nov 11, 2023 at 03:53:09PM +0100, Stefan Sperling wrote:
> > If neon requests OPENSSL_API_COMPAT 0x1000L and also calls
> > OPENSSL_init_ssl() then that is a bug in neon.
>
> The neon version
On Sat, Nov 11, 2023 at 03:53:09PM +0100, Stefan Sperling wrote:
> If neon requests OPENSSL_API_COMPAT 0x1000L and also calls
> OPENSSL_init_ssl() then that is a bug in neon.
The neon version used by Makefile.svn is quite old.
Newer releases are available here: https://notroj.github.i
On Sat, Nov 11, 2023 at 02:22:55PM +0100, Daniel Sahlberg wrote:
> Hi,
>
> I'm separating this out to a new thread since it doesn't relate to the
> upcoming release, but I'm doing the work trying to reproduce Nathan's
> problem.
>
> I've installed Debian Bullseye (on Hyper-V, but that shouldn't
On Fri, Oct 13, 2023 at 08:43:59AM +0200, Daniel Sahlberg wrote:
> Hi,
>
> There are quite a number of improvements waiting to be released. Can we
> muster the energy to do a new release?
>
> In trunk there are a lot of changes that warrant a 1.15, but before doing
> that I think we should also
On Fri, Oct 13, 2023 at 12:42:27AM -0500, Greg Stein wrote:
> Hey all,
>
> So I'm looking at incorporating a couple key svn-mailer (by Andre Malo)
> features into mailer.py. Specifically, the body-length limit and mail
> encoding, and in turn deferring to viewvc links to replace what would be
>
On Mon, Jan 09, 2023 at 11:19:48AM +0100, Johannes von Rotz wrote:
> Hello
>
> I was trying to compile subversion with the HP ANSI C compiler on HP-UX
> yesterday, which complained about the if-statement in question requiring a
> scalar value or something. Unfortunately, I'm unable to recite the
On Thu, Apr 28, 2022 at 01:29:43PM +, Daniel Shahaf wrote:
> Stefan Sperling wrote on Thu, 28 Apr 2022 09:55 +00:00:
> > I think it would be better to have such details spelled out in English
> > in a manner that is easy to understand for anyone, with illustrating
> &
On Wed, Apr 27, 2022 at 11:43:02PM -0400, Nathan Hartman wrote:
> On Wed, Apr 27, 2022 at 4:56 PM Daniel Sahlberg
> wrote:
> >
> > Den ons 27 apr. 2022 kl 21:02 skrev Daniel Shahaf :
> >>
> >> As to the general rule, I think we're missing a piece: the overlap
> >> period. We should say something
On Mon, Apr 25, 2022 at 10:05:58PM +0200, Daniel Sahlberg wrote:
> Hi,
>
> According to the Roadmap, How we plan releases[1], 1.10.0 is a LTS release
> that will receive support for 4 years. According to the News archive[2],
> 1.10.0 was released 2018-04-13.
>
> 1.10.0 was released approximately
On Thu, Apr 21, 2022 at 08:25:32PM +0300, Sergey Raevskiy wrote:
> I've noticed that in some cases a working copy can become inoperable
> after merge text conflict resolution with `svn_wc_conflict_choose_merged'
> option.
>
> The problem can occur in the following scenario:
>
> 1. There is a
On Thu, Apr 07, 2022 at 10:07:15AM -0400, Nathan Hartman wrote:
> > We should have enough signatures according to ASF rules (need 3 signatures
> > by PMC members), but not for our own cross-platform testing requirements
> > (there is only one windows signature so far).
> >
> > Should we fail to
On Thu, Apr 07, 2022 at 09:37:08AM -0400, Mark Phippard wrote:
> Just a reminder, the 1.10.8 and 1.14.2 releases are posted and
> available for testing and signatures. Please try to get them completed
> by this Sunday.
>
> The plan is to make the release available on Tuesday April 12.
>
> Thanks
On Sat, Apr 02, 2022 at 09:28:15AM -0400, Mark Phippard wrote:
> The 1.14.2 release artifacts are now available for testing/signing.
>
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there.
Summary: +1 to release
Tested: [bdb |
On Sat, Apr 02, 2022 at 09:27:18AM -0400, Mark Phippard wrote:
> The 1.10.8 release artifacts are now available for testing/signing.
>
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there.
>
> Thanks!
Summary: +1 to release
On Fri, Apr 01, 2022 at 06:08:14PM +0200, Johan Corveleyn wrote:
> I suppose the "modified for better performance" refers to some
> optimisations done by Morten Kloster, who then later submitted the
> patch adding this comment in r1128862. His optimisations were more
> related to the LCS algorithm
On Fri, Apr 01, 2022 at 05:04:49PM +0200, Johan Corveleyn wrote:
> Yes, I suppose this is the case: Patience feeds different (smaller)
> things to LCS. Because, as far as I understand, Myers' way of
> calculating the LCS is fundamentally "somewhat" quadratic (according
> to the Myers paper from
On Fri, Apr 01, 2022 at 10:16:41AM -0400, Mark Phippard wrote:
> I think we are all set for tomorrow. I updated CHANGES on trunk for
> both releases and backported to the branches. Feel free to review and
> make edits if you see fit. I will just go with whatever is on the
> branches tomorrow AM.
>
On Fri, Apr 01, 2022 at 04:17:45PM +0200, Johan Corveleyn wrote:
> - Perhaps the fundamental diff algorithm in SVN is fine, but it has a
> performance bug / low-level inefficiency? I think that should be
> explored first, because it might fix most of this problem without
> requiring a discussion
On Fri, Apr 01, 2022 at 12:44:24PM +0200, Johan Corveleyn wrote:
> On Tue, Jun 8, 2021 at 5:58 PM Johan Corveleyn wrote:
> > On Tue, Jun 8, 2021 at 3:24 PM Stefan Sperling wrote:
> > > On Tue, Jun 08, 2021 at 02:57:34PM +0200, Johan Corveleyn wrote:
> > > > Okay, I
On Thu, Mar 31, 2022 at 09:21:58AM -0400, Nathan Hartman wrote:
> On Thu, Mar 31, 2022 at 9:09 AM Nathan Hartman
> wrote:
> > My bad. Hopefully r1899430 fixes it.
> >
> > How do I manually run backport.pl?
>
> Let me rephrase that question: How do I manually trigger it so we
> don't have to
On Sun, Mar 27, 2022 at 09:35:51AM -0400, Nathan Hartman wrote:
> On Sun, Mar 27, 2022 at 9:05 AM Mark Phippard wrote:
> >
> > On Sun, Mar 27, 2022 at 8:50 AM Nathan Hartman
> > wrote:
> > >
> > > On Sun, Mar 27, 2022 at 7:05 AM Mark Phippard wrote:
> > >>
> > >> On Sun, Mar 27, 2022 at 7:00
On Mon, Mar 21, 2022 at 04:46:55PM -0400, Mark Phippard wrote:
> On Mon, Mar 21, 2022 at 4:31 PM Stefan Sperling wrote:
> > This might be a swig problem? Perhaps the version of swig and the
> > version of python don't work well together? Not sure.
>
> HACKING implies I s
On Mon, Mar 21, 2022 at 12:44:44PM -0400, Mark Phippard wrote:
> I have been toying with the idea of volunteering to be Release
> Manager. I am not ready to do so yet as I have run into numerous
> problems.
>
> The docs are decent but they are definitely written to an audience
> that knows a lot
On Fri, Feb 11, 2022 at 09:22:25AM +0100, Martin Obermeir wrote:
> Hi,
>
> When using `svn copy --pin-externals` to create a tag, svn:externals with a
> relative path get pinned a non existing path: They get pinned to the
> revision before the commit, but the path doesn't exist yet in that
On Thu, Feb 10, 2022 at 12:10:08AM -0600, Karl Fogel wrote:
> On 09 Feb 2022, Ruediger Pluem wrote:
> > When rebuilding my own Subversion build I stumbled across the following
> > patch that I add to my build:
> >
> > Index: subversion/libsvn_client/patch.c
> >
On Wed, Feb 09, 2022 at 08:01:26AM -0500, Mark Phippard wrote:
> Anyway, my feeling has been that one of the blockers to being RM is
> motivation. My feeling has been that it is a fair amount of work that
> might not go anywhere because we do not have enough interest in
> reviewing and signing the
On Wed, Feb 09, 2022 at 07:23:55AM -0500, Mark Phippard wrote:
> 2. We need a RM to produce the release. Only a handful of people have
> done this and I am not one of them so I cannot comment on how hard
> this is. It does feel like this entire process could be completely
> automated though. As
On Wed, Jan 19, 2022 at 08:08:06PM -0600, Karl Fogel wrote:
> ('svn authn' could also support a '--remove' flag to clear out the authn
> cache for a given repository.)
You may have missed that we have added the 'svn auth' command while
you were not looking :)
Removing cached creds can already be
On Tue, Jan 11, 2022 at 12:22:38AM -0500, Nathan Hartman wrote:
> On Mon, Jan 10, 2022 at 6:44 AM wrote:
> >
> > Author: stsp
> > Date: Mon Jan 10 11:44:46 2022
> > New Revision: 1896877
> >
> > URL: http://svn.apache.org/viewvc?rev=1896877=rev
> > Log:
> > Fix misleading -r option documentation
On Sun, Dec 05, 2021 at 11:21:48PM -0500, Nathan Hartman wrote:
> On Sun, Dec 5, 2021 at 12:55 PM James McCoy wrote:
> >
> > On Sun, Dec 05, 2021 at 12:41:30PM -0500, Nathan Hartman wrote:
> > > It's not dumping core on mine. I would like to debug this properly but
> > > am running into various
On Sun, Oct 03, 2021 at 12:38:48PM +0200, Daniel Sahlberg wrote:
> * Create an svn auth add command. This option has the advantage that
> one person has expressed interest to invest time to write the code.
> Based on the reasoning above I'm proposing:
> - Adding an svn auth add command
On Fri, Aug 27, 2021 at 06:01:21PM +0200, Stefan Sperling wrote:
> Consider an asymmetric home internet connection with more download
> than upload capacity. The server may well be able to send the
> original full text much faster than the client could upload it.
> So with a suffic
On Fri, Aug 27, 2021 at 06:42:34PM +0300, Evgeny Kotkov wrote:
> Mark Phippard writes:
>
> > Suppose I am using this feature for binaries, which I think is the
> > main use case. Using whatever tool I produce a modified version of my
> > binary file. At this point in time, there is nothing in
On Fri, Aug 27, 2021 at 11:38:57AM +, Daniel Shahaf wrote:
> The solution to "credentials can't be used to commit with" is not
> *necessarily* "cache a password for a different username". It could
> also be that the authz file has a business logic error («r» rather than
> «rw»), or that the
On Thu, Aug 26, 2021 at 04:08:34PM -0400, Nathan Hartman wrote:
> On Thu, Aug 26, 2021 at 6:30 AM Stefan Sperling wrote:
> > One consequence is that when Alice mistypes the --username option, or
> > mistypes the username or password at the prompt, invalid credentials will
>
On Thu, Aug 26, 2021 at 04:17:16PM +0200, Daniel Sahlberg wrote:
> Den tors 26 aug. 2021 kl 16:10 skrev Stefan Sperling :
>
> > On Thu, Aug 26, 2021 at 02:41:44PM +0200, Johan Corveleyn wrote:
> > > I get the feeling I'm missing something, but I still don't understand
>
On Thu, Aug 26, 2021 at 12:15:39PM +, Daniel Shahaf wrote:
> Stefan Sperling wrote on Thu, 26 Aug 2021 10:30 +00:00:
> > And while we are considering read-only vs. read-write access:
> > Plaintext passwords or not, in my contrived scenario Eve could always
> > t
On Thu, Aug 26, 2021 at 02:41:44PM +0200, Johan Corveleyn wrote:
> I get the feeling I'm missing something, but I still don't understand
> what authz has to do with the problem at hand here (i.e. detecting
> expired passwords so we can ask the user for the new one).
The problem is that some
On Thu, Aug 26, 2021 at 10:11:44AM +0200, Branko Čibej wrote:
> On 25.08.2021 21:01, Mark Phippard wrote:
> > On Wed, Aug 25, 2021 at 3:16 AM Johan Corveleyn wrote:
> >
> > > > Is there a way to test whether one has rw access without actually doing
> > > > a commit or a revprop edit? It's
On Tue, Aug 24, 2021 at 02:37:57AM -0700, Robby Zinchak wrote:
> Oh, hello all :)
>
> Yeah, between this cli obstacle, problems with rapidsvn corrupting local
> repo during file moves, and svn Apache frequently corrupting server repo
> unrecoverably in large check-ins (>200mb) and requiring a
On Tue, Aug 24, 2021 at 12:16:48PM +0200, Johan Corveleyn wrote:
> But: obviously I have disabled, in the runtime config area, the
> warning prompt that "Your password will be stored in plaintext" (I
> have disabled it system-wide, in /etc/subversion). Yes, we know this
> and we accept it. I would
On Mon, Aug 23, 2021 at 02:45:44PM +0200, Johan Corveleyn wrote:
> Thanks, those are good efforts (and thanks to both Daniels for writing
> them), but I'm afraid those workarounds are not good enough. The thing
> is: this is not for me alone. This needs to be handled in buildscripts
> that can be
nt. Not all communication with users
occurs via public channels.
> For reference, here is the e-mail where Stefan Sperling mentions the change
> in OpenBSD to re-enable support for plaintext passwords in OpenBSD: [2] I
> would encourage everyone to re-read that message since it has a good
> s
On Sat, Aug 21, 2021 at 09:38:56PM +0200, Daniel Sahlberg wrote:
> > @@ -3028,12 +3028,12 @@ conflict_tree_get_details_local_missing(
> >deleted_basename,
> >conflict->pool);
> >
On Sun, Aug 01, 2021 at 10:53:18PM +0200, Daniel Sahlberg wrote:
> Did anyone have the time to review this?
>
> I realise another way to do it would be to add an argument to
> location_common. Maybe a bit clearer, possibly even reducing to a single
> call to cat if the AuthzSVNAccessFile is put
On Tue, Jun 08, 2021 at 05:58:14PM +0200, Johan Corveleyn wrote:
> Also: one of the last things that Morten Kloster committed in 2011 was
> another performance improvement, namely "restarting the LCS" in some
> specific cases. At the time, I didn't have enough time to review this
> properly, and
On Wed, Jun 23, 2021 at 09:56:05PM +0200, Daniel Sahlberg wrote:
> Hi,
>
> I'm rebuilding TortoiseSVN to test some of the new performance enhancements
> in /trunk. The TSVN source tree fetch the sources of Subversion using
> svn:externals which is kind of neat. The build process creates a few
On Tue, Jun 08, 2021 at 02:57:34PM +0200, Johan Corveleyn wrote:
> Okay, I focused on the first revision causing the annotate to differ,
> and with some debug logging:
> - p went up to 139
> - length[0]=1942, length[1]=1817
>
> Now, 1942 lines on the left and 1817 on the right doesn't seem all
>
On Tue, Jun 08, 2021 at 01:45:00AM -0400, Nathan Hartman wrote:
> In order to do some testing, I needed some test data that reproduces
> the issue; since stsp can't share the customer's 100MB XML file, and
> we'd probably want other inputs or sizes anyway, I wrote a program
> that attempts to
On Sat, Jun 05, 2021 at 08:56:24PM +0200, Johan Corveleyn wrote:
> Hmm, I tried this patch with my "annotate large XML file with deep
> history test", but the result isn't the same as with 1.14. I'd have to
> investigate a bit more to find out where it took another turn, and
> what that diff looks
On Wed, Jun 02, 2021 at 02:20:12PM +0200, Stefan Sperling wrote:
> The patch below implements an effort limit for Subversion's LCS diff.
Here is an updated version of this patch. I took a closer look at
other diff implementations again, and realized that they don't use
a fixed limit but one wh
I've heard of several instances where users complain that 'svn update'
takes an extraordinary amount of time to run (in terms of hours).
At elego we have received files which reproduce such behaviour.
These files are XML files that are almost 100MB in size. While versioning
such data is not the
On Sun, May 30, 2021 at 09:30:58PM +0100, Julian Foad wrote:
> Stefan Sperling wrote:
> > Nathan Hartman wrote:
> >>> + http://libera.chat;>Matrix or
> >>
> >> How does this URL work? Does it have to be opened from within a Matrix app?
>
On Sun, May 30, 2021 at 09:26:25AM -0400, Nathan Hartman wrote:
> On Sun, May 30, 2021 at 3:40 AM wrote:
> > + http://libera.chat;>Matrix or
>
>
> How does this URL work? Does it have to be opened from within a Matrix app?
>
> (My browser doesn't know what to do with it, but I don't have
On Wed, May 26, 2021 at 05:29:49PM +0200, Daniel Sahlberg wrote:
> I can draft a short news item and put it on staging. I think it should be
> low key ("we have decided to move"), or does someone think we should make a
> statement ("we move because XXX is a [insert suitable invective]")?
We don't
On Wed, May 26, 2021 at 10:52:42AM +0200, Stefan Sperling wrote:
> On Wed, May 26, 2021 at 10:41:28AM +0200, Daniel Sahlberg wrote:
> > Considering latest development (the channel takeovers mentioned by Stefan
> > Sperling in another part of the thread), I'd suggest that we switch
On Wed, May 26, 2021 at 10:41:28AM +0200, Daniel Sahlberg wrote:
> Considering latest development (the channel takeovers mentioned by Stefan
> Sperling in another part of the thread), I'd suggest that we switch the
> website. I would go for a more drastic change than Nathan's patch (which
On Wed, May 26, 2021 at 09:42:36AM +0200, Stefan Sperling wrote:
> On Mon, May 24, 2021 at 08:10:40PM +, Daniel Shahaf wrote:
> > I've gone ahead and moved wayita to libera.
> >
> > I wanted to keep a copy on freenode, but forgot to change the pointer to
> > t
On Mon, May 24, 2021 at 08:10:40PM +, Daniel Shahaf wrote:
> I've gone ahead and moved wayita to libera.
>
> I wanted to keep a copy on freenode, but forgot to change the pointer to
> the sqlite database, and I'm not sure whether it's possible to use the
> same set of factoids for two
On Fri, May 21, 2021 at 03:02:08PM +0200, Branko Čibej wrote:
> Every time I hear (or read) someone explaining how "one of my companies is
> funding this free service", I grab my wallet and run away. "Monetizing"
> community-lead and -created services has been a thing since before the
> Internet.
On Thu, May 20, 2021 at 04:15:23PM +0100, Julian Foad wrote:
> For contrast:
> "The Panic Over Freenode Isn’t Justified and Its Reaction Mostly
> Disproportionate"
> http://techrights.org/2021/05/19/freenode-and-cancel-culture/
>
> It took me a while to find an article that covered the issue in
On Thu, May 20, 2021 at 11:43:43AM +0100, Julian Foad wrote:
> Stefan Sperling wrote:
> > Keeping a matrix bridge to the current freenode channels alive means we're
> > not actually leaving this network. To support the former freenode staff it
> > makes more sense
On Wed, May 19, 2021 at 07:23:43PM +0100, Julian Foad wrote:
> Looks like we might want to move our channels, bots, and so on?
> Libera.chat [2] has been posited as a direct replacement.
> However, the sane replacement these days is Matrix [1].
I understand Matrix has more modern technology,
On Sun, Apr 11, 2021 at 07:55:33AM +0200, Stefan Sperling wrote:
> Just adding another thing: It looks like task.c has undefined symbols
> during linking if APR is built without support for threads:
I see that this has been fixed now. Thank you!
On Thu, Apr 08, 2021 at 08:01:43PM +, Daniel Shahaf wrote:
> Good morning Stefan,
>
> stef...@apache.org wrote on Thu, Apr 08, 2021 at 14:35:52 -:
> > Initial, single-theaded implementation of the svn_task__t API.
>
> I've committed some minor fixes in r1888533. Most of them are
>
On Tue, Feb 16, 2021 at 08:18:04PM +, Daniel Shahaf wrote:
> Stefan Sperling wrote on Tue, Feb 16, 2021 at 12:12:35 +0100:
> > On Mon, Feb 15, 2021 at 07:47:48PM +, Daniel Shahaf wrote:
> > > s...@apache.org wrote on Fri, Feb 12, 2021 at 10:40:16 -:
> > >
On Tue, Feb 16, 2021 at 01:05:32PM +0100, Daniel Sahlberg wrote:
> Den tis 16 feb. 2021 kl 11:34 skrev Stefan Sperling :
> > On Mon, Feb 15, 2021 at 07:46:08PM +, Daniel Shahaf wrote:
> > > The entity referred to by the tag wasn't created in 2021. So,
> > > I
On Mon, Feb 15, 2021 at 07:47:48PM +, Daniel Shahaf wrote:
> s...@apache.org wrote on Fri, Feb 12, 2021 at 10:40:16 -:
> > Author: stsp
> > Date: Fri Feb 12 10:40:16 2021
> > New Revision: 1886460
> >
> > URL: http://svn.apache.org/viewvc?rev=1886460=rev
> > Log:
> > Add a test for the
On Mon, Feb 15, 2021 at 07:46:08PM +, Daniel Shahaf wrote:
> s...@apache.org wrote on Wed, Feb 10, 2021 at 20:39:23 -:
> > Author: stsp
> > Date: Wed Feb 10 20:39:22 2021
> > New Revision: 1886396
> >
> > URL: http://svn.apache.org/viewvc?rev=1886396=rev
> > Log:
> > site/publish: Merge
On Sun, Feb 14, 2021 at 05:28:06PM -0600, Greg Stein wrote:
> Hey all,
>
> This is a very strange error that we're seeing in Infra, on the ASF svn
> server. It appears that the presence of a particular file in a commit
> causes a failure.
>
> Please see:
>
On Sat, Feb 13, 2021 at 04:50:10PM +0100, Branko Čibej wrote:
> On 13.02.2021 15:32, Evgeny Kotkov wrote:
> > My attempt to fix this is by making checkout stream data to both pristine
> > and
> > the (projected) working file, so that the actual install would then happen
> > as
> > just an atomic
On Thu, Feb 11, 2021 at 11:02:32AM +, Private List Moderation wrote:
> Irrelevant.
Given that this discussion doesn't seem to be going anywhere and the
same arguments from May 2020 are just being rehashed, I guess we will
simply stop using the announce@ mailing list.
On Thu, Feb 11, 2021 at 10:31:24AM +0100, Daniel Sahlberg wrote:
> Den tors 11 feb. 2021 kl 10:11 skrev Stefan Sperling :
>
> > On Thu, Feb 11, 2021 at 09:57:23AM +0100, Daniel Sahlberg wrote:
> > > It is indeed a chicken-and-egg problem. However I would suggest to split
On Thu, Feb 11, 2021 at 09:57:23AM +0100, Daniel Sahlberg wrote:
> It is indeed a chicken-and-egg problem. However I would suggest to split
> this "updating the website" into two separate parts:
> 1. Updating the download page and possibly also adding a news item (with a
> placeholder link to the
On Wed, Feb 10, 2021 at 11:03:39PM -0500, Nathan Hartman wrote:
> On Wed, Feb 10, 2021 at 7:51 PM Private List Moderation <
> mod-priv...@gsuite.cloud.apache.org> wrote:
> > When I checked the download page, there were no links for versions 1.10.7
> > or 1.14.1.
> > i.e. the 2 announce mails were
On Wed, Feb 10, 2021 at 08:30:52PM +0100, Daniel Sahlberg wrote:
> *grabbing a commit in the pile*
>
> Is it intentional that the download page still links to 1.14.0 (and 1.10.6)?
>
> (I'm not familiar with the relase workflow and I realise this may be a soak
> for all mirrors to pick up the
contain links for the version in the
> email.
>
> Also, the standard name for the KEYS file is KEYS - no prefix, no suffix.
> Please correct the download page, check it, and submit a corrected announce
> mail.
>
> Thanks,
> Sebb.
> <<<<<
es not contain links for the version in the
email.
Also, the standard name for the KEYS file is KEYS - no prefix, no suffix.
Please correct the download page, check it, and submit a corrected announce
mail.
Thanks,
Sebb.
<<<<< <<<<<
Date
subversion-1.10.7.zip.asc
For this release, the following people have provided PGP signatures:
Stefan Sperling [2048R/4F7DBAA99A59B973] with fingerprint:
8BC4 DAE0 C5A4 D65F 4044 0107 4F7D BAA9 9A59 B973
Branko Čibej [4096R/1BCA6586A347943F] with fingerprint:
BA3C 15B1 337C F0FB 222B
subversion-1.14.1.zip.asc
For this release, the following people have provided PGP signatures:
Stefan Sperling [2048R/4F7DBAA99A59B973] with fingerprint:
8BC4 DAE0 C5A4 D65F 4044 0107 4F7D BAA9 9A59 B973
Branko Čibej [4096R/1BCA6586A347943F] with fingerprint:
BA3C 15B1 337C F0FB
On Thu, Feb 04, 2021 at 01:57:16PM +0100, Stefan Sperling wrote:
> The 1.10.7 release artifacts are now available for testing/signing.
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there.
Summary: +1 to release
Tested:
On Thu, Feb 04, 2021 at 01:56:21PM +0100, Stefan Sperling wrote:
> The 1.14.1 release artifacts are now available for testing/signing.
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there.
>
> Thanks!
Summary: +1
On Tue, Feb 09, 2021 at 09:58:10AM +0100, Daniel Roßberg wrote:
> Python 3 compatibility:
> Update a raise statement probably missed in revision 873411 changes.
>
> * tools/hook-scripts/svnperms.py
> (Permission.parse_groups): Use 'raise exception("string")' instead of
> 'raise exception,
On Fri, Feb 05, 2021 at 09:20:52AM -0500, Nathan Hartman wrote:
> On Fri, Feb 5, 2021 at 12:07 AM wrote:
>
> > The Buildbot has detected a new failure on builder svn-bb-openbsd while
> > building . Full details are available at:
> > https://ci.apache.org/builders/svn-bb-openbsd/builds/621
>
The 1.10.7 release artifacts are now available for testing/signing.
Please get the tarballs from
https://dist.apache.org/repos/dist/dev/subversion
and add your signatures there.
Thanks!
The 1.14.1 release artifacts are now available for testing/signing.
Please get the tarballs from
https://dist.apache.org/repos/dist/dev/subversion
and add your signatures there.
Thanks!
On Fri, Jan 29, 2021 at 04:13:15PM -0500, Nathan Hartman wrote:
> On Fri, Jan 29, 2021 at 3:46 PM Stefan Sperling wrote:
> > It is already listed as a known problem in 1.10:
> > http://subversion.apache.org/docs/release-notes/1.10.html#issue-svn-4762
>
> It is already there
On Fri, Jan 29, 2021 at 09:29:52PM +0100, Johan Corveleyn wrote:
> I was wondering whether the change in authz behavior, by fixing #4762,
> should be called out explicitly in the 1.14 release notes (maybe
> somewhere in the "Known issues" section, describing the issue of
> 1.14.0, and how it is
On Fri, Jan 22, 2021 at 02:36:56PM +0100, Stefan Sperling wrote:
> I am volunteering to prepare release artifacts for new 1.14 and
> 1.10 releases soon. Hopefully, these artifacts will be up for
> testing and signing by the end of next week (January 29), to be
> released within the fir
On Tue, Jan 26, 2021 at 11:57:50PM +0100, Johan Corveleyn wrote:
> Yes, I agree we should stick to our established policy here.
>
> We recently loosened our backport-voting policy a bit for non-LTS
> (Regular) releases, but we didn't for LTS releases (no time to dig up
> the thread, but ISTR we
On Tue, Jan 26, 2021 at 04:45:32PM -0500, Nathan Hartman wrote:
> On Tue, Jan 26, 2021 at 4:28 PM Daniel Shahaf
> wrote:
>
> > Stefan Sperling wrote on Fri, Jan 22, 2021 at 14:36:56 +0100:
> > > [...] I will allow myself to merge any nominations which received at
>
1 - 100 of 2510 matches
Mail list logo
