autoconf out-of-tree builds broken (was: svn commit: r1920955 - in /subversion/trunk: configure.ac subversion/tests/cmdline/ subversion/tests/cmdline/svneditor.sh subversion/tests/cmdline/svneditor.sh

rin...@apache.org wrote on Thu, 26 Sep 2024 13:22 +00:00: > Fix command-line tests on Linux by removing configuration of svneditor.sh > script. > > See also 'Removing configuration of svneditor.sh script?' thread on dev@ [1]. The log message says "Fix", but neither the log message nor the thread e

Re: Apply tree-processor (was: Binary Patch (xpatch))

Timofei Zhakov wrote on Sat, 23 Nov 2024 21:39 +00:00: > [...] > >> However, there are some technical limitations in the current merge >> implementation, which prohibit it to be used outside of the merge >> command, but the merge implementation can be split onto two files; the >> merge itself and t

Re: Binary Patch (xpatch)

Timofei Zhakov wrote on Sat, 23 Nov 2024 10:26 +00:00: > Hi! > Nice to meet you :) > I am using patches frequently, however, 'svn diff' and 'svn patch' > commands currently have several limitations: > > 1. They do not track tree changes (like copies and moves) > 2. Binary file modifications are n

Re: svntest.verify.compare_dump_files() under Python3

Daniel Sahlberg wrote on Sat, 23 Nov 2024 16:14 +00:00: > Den fre 22 nov. 2024 kl 14:33 skrev Daniel Shahaf : > > If I force an svnsync test to fail: > > > > [[[ ⋮ > > TypeError: 'in ' requires string as left operand, not int > > FAIL: svnsync_tests.

CI jobs for backport.py? (was: [PATCH] Unbreak backport.py unit tests)

Daniel Shahaf wrote on Fri, 22 Nov 2024 14:43 +00:00: > Any issues with the backport_tests.py aside, one of the unittest tests > fails as well. > > Patch attached. I'd commit it directly, but I'd have to reset my apache.org > password first. In the meantime, Daniel (or a

[PATCH] Unbreak backport.py unit tests

Any issues with the backport_tests.py aside, one of the unittest tests fails as well. Patch attached. I'd commit it directly, but I'd have to reset my apache.org password first. In the meantime, Daniel (or anyone else), feel free to go ahead and commit it if doing so would unblock your workflow.

svntest.verify.compare_dump_files() under Python3

If I force an svnsync test to fail: [[[ Index: subversion/tests/cmdline/svnsync_tests.py === --- subversion/tests/cmdline/svnsync_tests.py (revision 1922016) +++ subversion/tests/cmdline/svnsync_tests.py (working copy) @@ -481,7 +

Re: Performance of 'svnlook changed' is O(revsize)

Johan Corveleyn wrote on Fri, 18 Oct 2024 14:33 +00:00: > Haven't looked into the code yet, but this might be an nice > "bite-sized" issue to investigate, if someone has time and inclination > to do so: > > Seen on a FSFS f8 repository (on Linux) with a 200 MB revision: > > Apparently 'svnlook chan

Re: [DISCUSS] backport.pl or backport.py

Nathan Hartman wrote on Wed, 20 Nov 2024 21:17 +00:00: > I notice that you write: tools/backport/*.py rather than > tools/dist/*.py or tools/dist/backport/*.py. If that's intentional, I > like this idea. Currently, tools/dist contains a mix of tools for > managing backports and release management;

Re: [DISCUSS] backport.pl or backport.py

Daniel Sahlberg wrote on Wed, 20 Nov 2024 17:56 +00:00: > There was two minor issues which I fixed in r1921977-r1921978. The tests > now PASS for both Perl and Python versions. Nice, thanks! Might want to update README.backport lines 55:63 now, since the "not the same language" comment is no long

Re: [DISCUSS] backport.pl or backport.py

Nathan Hartman wrote on Wed, 20 Nov 2024 21:21 +00:00: > On Wed, Nov 20, 2024 at 12:16 PM Daniel Sahlberg < > daniel.l.sahlb...@gmail.com> wrote: >> Den ons 20 nov. 2024 kl 14:50 skrev Daniel Shahaf >> B. Would more maintainers use the interactive functions if they [the &

Re: [DISCUSS] backport.pl or backport.py

Nathan Hartman wrote on Tue, 19 Nov 2024 16:00 +00:00: > Looking through the backports stuff in tools/dist, currently it's a > little bit messy. I wonder if things can be simplified with a minimal > amount of effort. > > What if we had just one script, actually called backport.py, with > subcommand

Re: [DISCUSS] backport.pl or backport.py

Daniel Sahlberg wrote on Mon, 18 Nov 2024 08:52 +00:00: > backport.pl is a heavy user of "given ... when ..." and given that these > constructs will be removed[1] when Perl 5.42 is released (pun intended), we > need to take some action. I'm guessing we have about one year before > hitting a brick w

Re: svn commit: r1908812 - /subversion/branches/pristine-checksum-salt/BRANCH-README

[Replying to the most recent commit to BRANCH-README:] kot...@apache.org wrote on Thu, 30 Mar 2023 19:04 +00:00: > Author: kotkov > Date: Thu Mar 30 19:04:13 2023 > New Revision: 1908812 > > URL: http://svn.apache.org/viewvc?rev=1908812&view=rev > Log: > On the 'pristine-checksum-salt' branch: Upd

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

Karl Fogel wrote on Wed, 03 Jan 2024 22:13 +00:00: > On 01 Apr 2023, Evgeny Kotkov via dev wrote: > > Daniel Shahaf writes: > > > > > What's the question or action item to/for me? Thanks. > > > > I'm afraid I don't fully understand your que

Re: mbox archives

Daniel Sahlberg wrote on Mon, 08 Jan 2024 12:21 +00:00: > Den mån 8 jan. 2024 kl 10:08 skrev Daniel Shahaf : > >> How is an interested community member supposed to get this list's archives >> in mbox format? >> >> Those on svn.haxx.se can be obtained from

mbox archives

How is an interested community member supposed to get this list's archives in mbox format? Those on svn.haxx.se can be obtained from there, but what about the others? gmane is down, lists.a.o has a download feature that seems to require either downloading one month at a time manually or using

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

Karl Fogel wrote on Wed, 03 Jan 2024 22:13 +00:00: > On 01 Apr 2023, Evgeny Kotkov via dev wrote: >>Daniel Shahaf writes: >> >>> What's the question or action item to/for me? Thanks. >> >>I'm afraid I don't fully understand your question. A

Re: Backport bot not running?

Daniel Sahlberg wrote on Mon, 18 Dec 2023 10:44 +00:00: > Den mån 18 dec. 2023 kl 09:40 skrev Daniel Shahaf : >> To prevent recurrence, options include (1) make the cron job use the .py >> implementation; (2) add a regression test to backport_tests.py [sic] and >> then fix

Re: Backport bot not running?

Daniel Sahlberg wrote on Thu, 30 Nov 2023 07:00 +00:00: > Den ons 29 nov. 2023 kl 17:25 skrev Nathan Hartman >: > >> On Wed, Nov 29, 2023 at 8:40 AM Daniel Sahlberg >> wrote: >> > >> > Den ons 29 nov. 2023 kl 06:55 skrev Daniel Sahlberg < >> daniel.l.sahlb...@gmail.com>: >> >> >> >> >> >> ons 29 n

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

Evgeny Kotkov via dev wrote on Wed, 22 Mar 2023 15:23 +00:00: > This change is still being blocked by a veto, but if danielsh changes his > mind and if there won't be other objections, I'm ready to complete the few > remaining bits and merge it to trunk. What's the question or action item to/for m

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

Evgeny Kotkov via dev wrote on Sun, Jan 29, 2023 at 16:37:20 +0300: > Daniel Shahaf writes: > > > > (I'm not saying that the above rules have to be used in this particular > > > case > > > and that a veto is invalid, but still thought it’s worth mentioni

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

Karl Fogel wrote on Mon, Jan 30, 2023 at 17:26:03 -0600: > On 29 Jan 2023, Evgeny Kotkov via dev wrote: > > I have *absolutely* no idea where "being railroaded through" comes > > from. Really, it's a wrong way of portraying and thinking about the > > events that have happened so far. > > > > Reit

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

Evgeny Kotkov via dev wrote on Sun, Jan 29, 2023 at 16:36:12 +0300: > Daniel Shahaf writes: > > > > That could happen after a public disclosure of a pair of executable > > > files/scripts where the forged version allows for remote code execution. > > > Or ma

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

Karl Fogel wrote on Mon, 30 Jan 2023 23:26 +00:00: > Daniel, given what's in Evgeny's branch now, could you summarize > your current technical objections if any? Certainly, but I won't have time to do so today.

Glossary of attacks (was: Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format)

h(), p₁, and p₂, find m₁, m₂ such that h(m₁) == h(m₂) and m₁.startswith(p₁) and m₂.startswith(p₂). Daniel Shahaf wrote on Thu, Jan 26, 2023 at 09:33:59 +: > Evgeny Kotkov via dev wrote on Mon, Jan 23, 2023 at 02:28:50 +0300: > > However, with the feasibility of chosen-prefix attac

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

Evgeny Kotkov via dev wrote on Mon, Jan 23, 2023 at 02:28:50 +0300: > Daniel Shahaf writes: > > > > I can complete the work on this branch and bring it to a production-ready > > > state, assuming there are no objections. > > > > Your assumption is

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

[ tl;dr: See last paragraph for a concrete question about ra_serf. ] Karl Fogel wrote on Fri, 20 Jan 2023 17:18 +00:00: > Yes. A hash is considered "broken" the moment security researches > can generate a collision. Consider the following uses of hash functions in our code: - FSFS rep-cache us

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

[See below a proposal that libsvn_wc not use any fixed hash function.] Martin Edgar Furter Rathod wrote on Sat, 21 Jan 2023 05:22 +00:00: > On 20.01.23 22:48, Karl Fogel wrote: >> On 20 Jan 2023, Nathan Hartman wrote: >>> We already can't store files with identical SHA1 hashes, but AFAIK the >>> o

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

; pristineless working copies available in an official release as > soon as we can. > > Best regards, > -Karl > > On 21 Jan 2023, Daniel Shahaf wrote: >>Karl Fogel wrote on Fri, Jan 20, 2023 at 11:09:11 -0600: >>> On 20 Jan 2023, Daniel Shahaf wrote: >>> > Evg

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

Karl Fogel wrote on Fri, Jan 20, 2023 at 11:18:56 -0600: > On 20 Jan 2023, Nathan Hartman wrote: > > Taking a step back, this discussion started because pristine-free WCs > > are IIUC more dependent on comparing hashes than pristineful WCs, and > > therefore a hash collision could have more impact

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

Karl Fogel wrote on Fri, Jan 20, 2023 at 11:09:11 -0600: > On 20 Jan 2023, Daniel Shahaf wrote: > > Evgeny Kotkov via dev wrote on Thu, 19 Jan 2023 18:52 +00:00: > > > I can complete the work on this branch and bring it to a > > > production-ready > > > sta

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

Nathan Hartman wrote on Fri, 20 Jan 2023 14:51 +00:00: > 1. Pros/cons of switching from SHA1 to another hash. ⋮ > Do we need to switch from SHA1 to another hash? One con that was > already mentioned [1] is that we'll never really be able to switch > away from SHA1, as there are existing clients, se

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

Evgeny Kotkov via dev wrote on Thu, 19 Jan 2023 18:52 +00:00: > I can complete the work on this branch and bring it to a production-ready > state, assuming there are no objections. Your assumption is counterfactual: https://mail-archives.apache.org/mod_mbox/subversion-dev/202301.mbox/%3C202301191

Re: Escape sequences in log messages [etc]

Nathan Hartman wrote on Wed, Jan 18, 2023 at 01:10:47 -0500: > On Tue, Jan 17, 2023 at 3:02 PM Doug Robinson > wrote: > > > Daniel, et. al.: > > > > On Mon, Jan 2, 2023 at 5:14 PM Daniel Sahlberg < > > daniel.l.sahlb...@gmail.com> wrote: > > > >> In a thread started by Vincent Lefevre in October

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format

Karl Fogel wrote on Thu, Dec 29, 2022 at 17:35:44 -0600: > On 29 Dec 2022, Evgeny Kotkov wrote: > > Karl Fogel writes: > > > > > Now, how hard would this be to actually implement? > > > > I plan to take a more detailed look at that, but I'm currently on > > vacation for the New Year holidays. >

Re: Switching from SHA1 to a checksum type without known collisions in 1.15 working copy format (was: Re: Getting to first release of pristines-on-demand feature (#525).)

Evgeny Kotkov via dev wrote on Tue, Dec 20, 2022 at 11:14:00 +0300: > [Moving discussion to a new thread] > > We currently have a problem that a working copy relies on the checksum type > with known collisions (SHA1). A solution to that problem Why is libsvn_wc's use of SHA-1 a problem? What's

Re: Getting to first release of pristines-on-demand feature (#525).

Nathan Hartman wrote on Wed, Dec 07, 2022 at 20:29:11 -0500: > On Wed, Dec 7, 2022 at 12:11 PM Evgeny Kotkov via dev < > dev@subversion.apache.org> wrote: > > > > > I think that the `pristines-on-demand-on-mwf` branch is now ready for a > > merge to trunk. I could do that, assuming there are no o

Re: [BUG] svn tries to read a directory on a different filesystem and hangs

Daniel Shahaf wrote on Mon, Oct 31, 2022 at 10:02:14 +: > Vincent Lefevre wrote on Mon, 24 Oct 2022 13:57 +00:00: > > "svn" goes up in the directory hierarchy to look for a .svn directory. > > The issue is that it doesn't stop at filesystem and/or owner change. &g

Re: [BUG] svn tries to read a directory on a different filesystem and hangs

Vincent Lefevre wrote on Mon, 24 Oct 2022 13:57 +00:00: > "svn" goes up in the directory hierarchy to look for a .svn directory. > The issue is that it doesn't stop at filesystem and/or owner change. Why should the upwards scan stop at mount points? Because accessing /home/.svn on a random machin

Re: svn commit: r1902590 - /subversion/trunk/tools/client-side/store-plaintext-password.py

Nathan Hartman wrote on Thu, Jul 14, 2022 at 10:45:07 -0400: > On Thu, Jul 14, 2022 at 10:02 AM Daniel Sahlberg > wrote: > > > > Den tors 14 juli 2022 kl 15:52 skrev Daniel Shahaf > > : > >> > >> Nathan Hartman wrote on Wed, 13 Jul 2022 15:29 +00:0

Re: svn commit: r1902722 - in /subversion/trunk/tools/dist: make-keys.sh release.py

dsahlb...@apache.org wrote on Thu, Jul 14, 2022 at 19:40:58 -: > Author: dsahlberg > Date: Thu Jul 14 19:40:57 2022 > New Revision: 1902722 > > URL: http://svn.apache.org/viewvc?rev=1902722&view=rev > Log: > Follow-up to r1902582: Improvements to the release.py script > > Suggested by: daniel

Re: svn commit: r1902723 - /subversion/site/staging/docs/community-guide/releasing.part.html

dsahlb...@apache.org wrote on Thu, 14 Jul 2022 19:51 +00:00: > +++ subversion/site/staging/docs/community-guide/releasing.part.html Thu Jul > 14 19:51:28 2022 > @@ -827,8 +827,7 @@ time pass. > To run this script, you'll need a Subversion trunk working > -copy (or a shallow trunk w

Re: svn commit: r1902590 - /subversion/trunk/tools/client-side/store-plaintext-password.py

Nathan Hartman wrote on Wed, 13 Jul 2022 15:29 +00:00: > On Wed, Jul 13, 2022 at 10:55 AM Daniel Shahaf > wrote: >> Should the entry link to the zsh script >> (https://mail-archives.apache.org/mod_mbox/subversion-dev/202008.mbox/%3C20200816130713.6abca815%40tarpaulin.shahaf.loc

Re: svn commit: r1902590 - /subversion/trunk/tools/client-side/store-plaintext-password.py

Daniel Shahaf wrote on Wed, 13 Jul 2022 14:54 +00:00: > Nathan Hartman wrote on Wed, 13 Jul 2022 13:43 +00:00: >> On Wed, Jul 13, 2022 at 9:33 AM Daniel Shahaf >> wrote: >> >>> dsahlb...@apache.org wrote on Fri, Jul 08, 2022 at 23:39:14 -: >>> > A ne

Re: svn commit: r1902590 - /subversion/trunk/tools/client-side/store-plaintext-password.py

Nathan Hartman wrote on Wed, 13 Jul 2022 13:43 +00:00: > On Wed, Jul 13, 2022 at 9:33 AM Daniel Shahaf > wrote: > >> dsahlb...@apache.org wrote on Fri, Jul 08, 2022 at 23:39:14 -: >> > A new script to store/update a password in the plain text password store >> &g

Re: svn commit: r1902582 - /subversion/trunk/tools/dist/release.py

Daniel Sahlberg wrote on Fri, Jul 08, 2022 at 23:07:08 +0200: > Den fre 8 juli 2022 kl 22:47 skrev : > > > Author: dsahlberg > > Date: Fri Jul 8 20:47:42 2022 > > New Revision: 1902582 > > > > URL: http://svn.apache.org/viewvc?rev=1902582&view=rev > > Log: > > ASF no longer provide a aggregated K

Re: svn commit: r1902582 - /subversion/trunk/tools/dist/release.py

dsahlb...@apache.org wrote on Fri, Jul 08, 2022 at 20:47:42 -: > +++ subversion/trunk/tools/dist/release.py Fri Jul 8 20:47:42 2022 > @@ -980,7 +979,12 @@ def roll_tarballs(args): > # from a committer's LDAP profile down the road) > basename = 'subversion-%s.KEYS' % (str(args

Re: svn commit: r1902590 - /subversion/trunk/tools/client-side/store-plaintext-password.py

dsahlb...@apache.org wrote on Fri, Jul 08, 2022 at 23:39:14 -: > A new script to store/update a password in the plain text password store > > * tools/client-side/store-plaintext-password.py > As above > > Discussed on dev@: > https://lists.apache.org/thread/jfd0f5n2qpgnyc30dst6ycnkphcwf6mm

Command-line tool for applying deltas? (was: Re: svnadmin: E16004: Invalid r4422 footer. How to investigate deeper?)

Good morning dev@, Anyone has a script that takes as input a file and an svndiff and emits to stdout the result of applying the latter to the former? This came up on users@ in the context of reconstructing a truncated rev file. I've checked tools/. Cheers, Daniel Daniel Shahaf wrote o

Re: Subversion 1.10.0 end-of-life

Daniel Sahlberg wrote on Fri, 27 May 2022 10:40 +00:00: > Den tors 26 maj 2022 kl 14:14 skrev Daniel Shahaf : >> +0.5 to post to announce@ (and users@). Might want to post the full >> draft here (including subject, etc.) first, though? > > I propose to reuse the news article,

Re: Subversion 1.10.0 end-of-life

Daniel Sahlberg wrote on Sun, 22 May 2022 21:07 +00:00: > Den mån 9 maj 2022 kl 14:12 skrev Nathan Hartman : > >> On Mon, May 9, 2022 at 7:38 AM Daniel Sahlberg < >> daniel.l.sahlb...@gmail.com> wrote: >> >>> Den sön 8 maj 2022 kl 02:21 skrev Daniel Shahaf

Re: svn commit: r1900883 - /subversion/branches/1.14.x/STATUS

Nathan Hartman wrote on Sun, May 15, 2022 at 03:36:05 -0400: > On Sat, May 14, 2022 at 8:57 AM wrote: > > +++ subversion/branches/1.14.x/STATUS Sat May 14 12:57:32 2022 > > @@ -39,6 +39,15 @@ Candidate changes: > > votes: > > +1: rhuijben > > > > + * r1900882 > > + Replace a call to a

Re: svn commit: r1900649 - in /subversion/site/publish: ./ docs/community-guide/releasing.part.html roadmap.html

dsahlb...@apache.org wrote on Sat, 07 May 2022 09:52 +00:00: > Merge from site/staging: 1900404, 1900405, 1900528, 1900532, 1900561, 1900562 > > Document the revised release policy as discussed on dev@ [1]. > > * publish/docs/community-guide/releasing.part.html, > publish/roadmap.html: > Change

Re: Subversion 1.10.0 end-of-life

Daniel Sahlberg wrote on Sat, 07 May 2022 18:37 +00:00: > Den lör 7 maj 2022 kl 14:17 skrev Daniel Shahaf : > >> Daniel Sahlberg wrote on Sat, 07 May 2022 09:53 +00:00: >> > I've committed the changes in r1900649. >> >> I wonder if this merits a news entry o

Re: Subversion 1.10.0 end-of-life

Daniel Sahlberg wrote on Sat, 07 May 2022 09:53 +00:00: > I've committed the changes in r1900649. I wonder if this merits a news entry on /index.html? Just "1.10.x is EOL; please upgrade to 1.14".

Re: svn commit: r1900404 - in /subversion/site/staging: docs/community-guide/releasing.part.html roadmap.html

Daniel Sahlberg wrote on Mon, 02 May 2022 20:12 +00:00: > Thanks to everyone for discussing this and moving it forward! I'm sorry I > wasn't able to be more active last week but life got in the way. > > One small point below... > > Den lör 30 apr. 2022 kl 00:04 skrev : > [...] > >> +LTS releases ar

Re: Subversion 1.10.0 end-of-life

Nathan Hartman wrote on Thu, Apr 28, 2022 at 15:25:55 -0400: > if we start releasing more frequent LTS .0 versions, we would end up > promising to support too many lines simultaneously. I hadn't > considered that because I was working from the assumption that we > aren't releasing new lines frequen

Re: Subversion 1.10.0 end-of-life

Nathan Hartman wrote on Thu, Apr 28, 2022 at 15:25:55 -0400: > the explanation about support periods should be easy to understand. Index: staging/roadmap.html === --- staging/roadmap.html(revision 1900368) +++ staging/roadmap.

Re: Subversion 1.10.0 end-of-life

act thinking to figure out. I'm unable to interpret this charitably. More below. > 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 D

Re: Subversion 1.10.0 end-of-life

Nathan Hartman wrote on Tue, 26 Apr 2022 13:58 +00:00: > On Tue, Apr 26, 2022 at 5:57 AM Stefan Sperling wrote: >> >> 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 receiv

Re: svn commit: r1899945 - /subversion/trunk/subversion/tests/cmdline/svntest/__init__.py

Daniel Sahlberg wrote on Wed, Apr 20, 2022 at 13:20:15 +0200: > Den ons 20 apr. 2022 kl 05:57 skrev Branko Čibej : > > > On 18.04.2022 19:46, Nathan Hartman wrote: > > > On Sun, Apr 17, 2022 at 9:30 AM wrote: > > >> Author: danielsh > > >> Date: Sun Apr 17 13:30:40 2022 > > >> New Revision: 18999

Re: Pristines-on-demand: printing progress notifications

Karl Fogel wrote on Wed, Mar 30, 2022 at 17:58:55 -0500: > On 30 Mar 2022, Julian Foad wrote: > > Karl Fogel wrote: > > > I think printing these messages to stderr makes the most sense. > > > There are plenty of programs out there that parse the stdout of > > > 'svn'; we don't want to interfere wit

Re: Pristines-on-demand: authz denied during textbase sync (#4888)

Julian Foad wrote on Wed, Apr 06, 2022 at 13:07:43 +0100: > > Filed as issue #4888, https://subversion.apache.org/issue/4888 > > I have just been looking back over this issue. Clearly there is more to > it than a quick fix. Summary, based on reviewing the email thread: > > - FAIL: authz_tests.py

Re: Pristines-on-demand: OK to merge to trunk?

Julian Foad wrote on Thu, Apr 07, 2022 at 12:43:03 +0100: > TL;DR: are we OK to merge the pristines feature > ('pristines-on-demand-on-mwf' branch) to trunk soon, like early next week? > > As said in "A status review" [1] in the long thread "A two-part vision > for Subversion and large binary obje

Re: svn commit: r1899276 - /subversion/site/publish/upcoming.part.html

Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 21:55:36 +0200: > Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg < > daniel.l.sahlb...@gmail.com>: > > > This commit doesn't look correct. > > > > I executed the generate-upcoming-changes-log.sh manually yesterday and it > > created r1899244, remo

Re: Question on release announcement mail

Mark Phippard wrote on Sun, Apr 10, 2022 at 16:02:07 -0400: > On Sun, Apr 10, 2022 at 3:27 PM Daniel Shahaf wrote: > > > > Mark Phippard wrote on Sun, Apr 10, 2022 at 15:16:58 -0400: > > > So I was wondering how, using the gpg command. I can get the other > > &g

Re: Question on release announcement mail

Mark Phippard wrote on Sun, Apr 10, 2022 at 15:16:58 -0400: > So I was wondering how, using the gpg command. I can get the other > elements we include .. such as: Stefan Sperling > [2048R/4F7DBAA99A59B973] They're generated by release.py:get_siginfo() which is called by write_announcement(), so, «

Re: Question on release announcement mail

Mark Phippard wrote on Sun, 10 Apr 2022 16:30 +00:00: > Looking at past release announcements, they include a section on who > signed the release that looks like this: > >Stefan Sperling [2048R/4F7DBAA99A59B973] with fingerprint: > 8BC4 DAE0 C5A4 D65F 4044 0107 4F7D BAA9 9A59 B973 >Bra

Re: svn commit: r1899311 - /subversion/branches/1.14.x/STATUS

Daniel Shahaf wrote on Fri, 01 Apr 2022 00:02 +00:00: > Daniel Sahlberg wrote on Thu, Mar 31, 2022 at 17:16:49 +0200: >> One thing to note is that merge-approved-backports.py have no interactive >> features. But I think it you are expected to run the other Python scripts >>

Re: Impediments to release

Nathan Hartman wrote on Thu, Mar 31, 2022 at 14:49:36 -0400: > In fact, the last couple of days, I have sifted through hundreds and > hundreds of changes (basically the list of merge-eligible changes from > trunk -- a LOT of work was committed in the past 14 months!!) That sounds very much like wh

Re: svn commit: r1899311 - /subversion/branches/1.14.x/STATUS

Daniel Sahlberg wrote on Thu, Mar 31, 2022 at 17:16:49 +0200: > Den tors 31 mars 2022 kl 16:12 skrev Daniel Sahlberg < > daniel.l.sahlb...@gmail.com>: > > > Den tors 31 mars 2022 kl 15:45 skrev Stefan Sperling : > > > >> On Thu, Mar 31, 2022 at 09:21:58AM -0400, Nathan Hartman wrote: > >> > On Thu

A New Feature[:] Film About Subversion

[ Follow-ups to dev@ only, please. ] Hi, everybody! As y'all may recall, issue #525 concerns implementing working copies that need not store an unmodified copy ("pristine", formerly "text-base") of every versioned file: https://subversion.apache.org/issue/525 Our currently-envisioned de

Re: svn commit: r1899311 - /subversion/branches/1.14.x/STATUS

Daniel Sahlberg wrote on Thu, Mar 31, 2022 at 16:51:33 +0200: > Den tors 31 mars 2022 kl 16:29 skrev Nathan Hartman < > hartman.nat...@gmail.com>: > > > On Thu, Mar 31, 2022 at 10:12 AM Daniel Sahlberg > > wrote: > > > > > > Den tors 31 mars 2022 kl 15:45 skrev Stefan Sperling : > > >> > > >> On

Re: What to do about PGP KEYS for release?

Mark Phippard wrote on Wed, Mar 30, 2022 at 08:01:32 -0400: > I am still a little unsure what to do about the KEYS file when we > produce this release. > > Our release.py script no longer works for whatever it used to do and > throws an error. I do not know if more errors will happen when I get >

Re: svn commit: r1899373 - /subversion/branches/1.14.x/STATUS

Daniel Sahlberg wrote on Wed, Mar 30, 2022 at 07:45:01 +0200: > So.. backports failed today as well. After some digging I realised > backport.pl didn't pick up the branch in this nomination due to a > whitespace issue in STATUS. I removed one space character on each line and > the backport worked.

Re: svn commit: r1899275 - /subversion/site/publish/.message-ids.tsv

Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 09:19:19 +0200: > Anyone got an idea why the URL list was sorted in a different way on the > new svn-qavm? Not that it is a big difference, but I don't like loose ends. > Probably the locale: [[[ % <1 LC_ALL=C sort http://svn.haxx.se/dev/archive-201

Re: svn commit: r1899247 - /subversion/branches/1.13.x/STATUS

Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 10:01:26 +0200: > Den mån 28 mars 2022 kl 02:33 skrev Daniel Shahaf : > > Daniel Sahlberg wrote on Sun, 27 Mar 2022 23:30 +00:00: > > > I also made some additional changes in roadmap.html (r1899268). This could > > > proba

Re: svn commit: r1899247 - /subversion/branches/1.13.x/STATUS

Daniel Sahlberg wrote on Sun, 27 Mar 2022 23:30 +00:00: > Den sön 27 mars 2022 kl 19:37 skrev Daniel Shahaf : > >> Thanks for these two changes! The information is duplicated in >> <https://subversion.apache.org/docs/release-notes/#supported-versions>; >> anyone

Re: Backports "bot" not running?

Mark Phippard wrote on Sun, Mar 27, 2022 at 13:56:51 -0400: > On Sun, Mar 27, 2022 at 1:45 PM Daniel Sahlberg > wrote: > > > > Den sön 27 mars 2022 kl 19:33 skrev Daniel Shahaf : > >> > >> It's not mutually exclusive; someone can run the script locall

Re: svn commit: r1899247 - /subversion/branches/1.13.x/STATUS

Thanks for these two changes! The information is duplicated in ; anyone wants to fix that, too? (Also, 1.14.x is absent from there.) dsahlb...@apache.org wrote on Sun, 27 Mar 2022 16:14 +00:00: > Author: dsahlberg > Date: Sun

Re: Backports "bot" not running?

Mark Phippard wrote on Sun, 27 Mar 2022 14:06 +00:00: > On Sun, Mar 27, 2022 at 9:53 AM Nathan Hartman > wrote: >> >> On Sun, Mar 27, 2022 at 9:46 AM Stefan Sperling wrote: >>> >>> On Sun, Mar 27, 2022 at 09:35:51AM -0400, Nathan Hartman wrote: >>> > On Sun, Mar 27, 2022 at 9:05 AM Mark Phippard

Re: Questions on Release Management Process

Mark Phippard wrote on Wed, 23 Mar 2022 11:36 +00:00: > On Tue, Mar 22, 2022 at 11:51 PM Daniel Shahaf > wrote: >> >> Mark Phippard wrote on Mon, Mar 21, 2022 at 16:46:55 -0400: >> > On Mon, Mar 21, 2022 at 4:31 PM Stefan Sperling wrote: >> > > On Mon,

Re: multi-wc-format: upgrading externals

Daniel Shahaf wrote on Fri, Mar 18, 2022 at 01:16:48 +: > Daniel Shahaf wrote on Thu, 17 Mar 2022 23:02 +00:00: > > Daniel Shahaf wrote on Tue, Mar 08, 2022 at 10:57:17 +: > >> Julian Foad wrote on Wed, Mar 02, 2022 at 13:04:51 +0000: > >> > Daniel Shahaf w

Re: Questions on Release Management Process

d the KEYS file our script is trying to fetch. > > See http://people.apache.org/keys/ where it says "Project group files are > > no longer created." > > > > It looks like what the script wants to do here is obtain a copy of > > the Subversion project's K

Re: svn commit: r1899014 - /subversion/trunk/subversion/tests/cmdline/upgrade_tests.py

Jun Omae wrote on Fri, Mar 18, 2022 at 11:27:16 +0900: > Hi, > > On Fri, Mar 18, 2022 at 9:44 AM Daniel Shahaf wrote: > > > > Could someone test this on Windows, please? I suspect read_wc_formats() > > (added in r1899012) returns paths with os.sep, but the expectatio

Re: multi-wc-format: upgrading externals

Daniel Shahaf wrote on Thu, 17 Mar 2022 23:02 +00:00: > Daniel Shahaf wrote on Tue, Mar 08, 2022 at 10:57:17 +: >> Julian Foad wrote on Wed, Mar 02, 2022 at 13:04:51 +0000: >> > Daniel Shahaf wrote: >> > > multi-wc-format/BRANCH-README mentioned this: >> >

Re: svn commit: r1899014 - /subversion/trunk/subversion/tests/cmdline/upgrade_tests.py

Could someone test this on Windows, please? I suspect read_wc_formats() (added in r1899012) returns paths with os.sep, but the expectations added in this commit use '/', so something will need to convert. Thanks, Daniel danie...@apache.org wrote on Fri, 18 Mar 2022 00:40 +00:00: > Author: danie

Re: multi-wc-format: upgrading externals

Daniel Shahaf wrote on Tue, Mar 08, 2022 at 10:57:17 +: > Julian Foad wrote on Wed, Mar 02, 2022 at 13:04:51 +: > > Daniel Shahaf wrote: > > > multi-wc-format/BRANCH-README mentioned this: > > > > > >> [*] New externals working copies must inherit

Re: multi-wc-format: svn_wc__format_from_version()

Julian Foad wrote on Thu, 17 Mar 2022 20:33 +00:00: > That's an old function. "Characteristic" previously meant the only > format supported by a given client version. We should change the word > now. What should the function return now? The newest, I think: its > callers are upgrade and checkout

multi-wc-format: svn_wc__format_from_version()

Here's the docstring: [[[ /** * Convert @a version to that version's characteristic working copy * format, returned in @a format. * * A NULL @a version translates to the library's default version. ⋮ */ svn_error_t * svn_wc__format_from_version(int *format, const s

Re: multi-wc-format review

Julian Foad wrote on Thu, Mar 17, 2022 at 11:10:32 +: > Daniel Shahaf wrote: > > + The upgraded working copy will be compatible with Subversion 1.8 and > > + newer (this default may change ... > > Sure, +1, a bit clearer. > Committed. > Also see Nathan's o

Re: Issue #525/#4892: on only fetching the pristines we really need

Julian Foad wrote on Wed, Mar 16, 2022 at 21:03:28 +: > Daniel Shahaf wrote: > >Also, unrelated: have we verified that all the temporary files we create > >are created in a crash-safe way? I.e., that if libsvn_wc is SIGKILL'd > >partway through hydrating someth

Re: Issue #525/#4892: on only fetching the pristines we really need

Julian Foad wrote on Wed, Mar 16, 2022 at 20:44:08 +: > We're free to continue design discussions but I've limited time and > need to focus. To me it appears we've moved far enough along this path > of "some of our users want to do X" leading to "let's see how far we > can implement an alternat

Re: Issue #525/#4892: on only fetching the pristines we really need

Julian Foad wrote on Wed, Mar 16, 2022 at 06:52:48 +: > Daniel Shahaf wrote: > >Julian Foad wrote: > >> exploration was enough to show that an initial release based on the > >> original approach has possibilities of being improved, incrementally, in > >> th

Re: Issue #525/#4892: on only fetching the pristines we really need

Julian Foad wrote on Wed, Mar 16, 2022 at 19:49:38 +: > Daniel Shahaf wrote: > > [...]I suspect I'm still missing something. > > I suggest you re-read the issue 4892 use case: > https://svn.apache.org/repos/asf/subversion/branches/pristines-on-demand-issue4892/notes/

Re: Issue #525/#4892: on only fetching the pristines we really need

Julian Foad wrote on Wed, Mar 16, 2022 at 07:03:43 +: > Daniel Shahaf wrote: > >This implies the wc won't be uniform revision. This might break user > >expectations; might [...], > I'm not sure how your clarification helps us progress. The point is: > > It

Re: Issue #525/#4892: on only fetching the pristines we really need

> >> [...] next a similar pattern applies to the "normal" part of the > >> update (everything it does after "restore"). Obviously we need the > >> normal part of update > > > >Yes, but for the "deltas" part of update we already mostly DTRT, don't we? > > > >- If the file is not modified, [...] > >

Re: Issue #525/#4892: on only fetching the pristines we really need

Julian Foad wrote on Wed, Mar 16, 2022 at 07:27:49 +: > Daniel Shahaf wrote: > >I'll also mention asciinema. It's basically script(1) into a video > >hosted online. It might be instructive for us to watch an asciinema > >session of someone trying this branch

Re: Issue #525/#4892: on only fetching the pristines we really need

Daniel Shahaf wrote on Wed, Mar 16, 2022 at 04:43:19 +: > Julian Foad wrote on Mon, Mar 14, 2022 at 20:23:29 +: > > Daniel Sahlberg wrote: > > >[...] I will try to build a release for myself and use it for dev work. > > Thank you Daniel. > > > > I'

  1   2   3   4   5   6   7   8   9   10   >