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

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. In either case, I updated the source to use https on the offending link to (r1899280) so we should see another update tomorrow. /Daniel Den mån 28

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

This commit doesn't look correct. I executed the generate-upcoming-changes-log.sh manually yesterday and it created r1899244, removing a lot of log entries belonging to 1.14.1. This commit (which was executed by cron) restores them. The crontab entry is: [[[ # Puppet Name: Update our upcoming cha

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

Den mån 28 mars 2022 kl 02:33 skrev Daniel Shahaf : > Daniel Sahlberg wrote on Sun, 27 Mar 2022 23:30 +00:00: > > Den sön 27 mars 2022 kl 19:37 skrev Daniel Shahaf < > d...@daniel.shahaf.name>: > > > >> Thanks for these two changes! The information is duplicated in > >>

Re: davautocheck failing on 1.14.x

On Sun, Mar 27, 2022 at 5:47 PM Daniel Sahlberg wrote: > > Den sön 27 mars 2022 kl 22:18 skrev Mark Phippard : >> >> This backport broke this script for me: >> >> https://svn.apache.org/viewvc?view=revision&revision=1899256 >> >> davautocheck.sh: Adding groups for mod_authz_svn tests >> AH00526: S

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

On Mon, Mar 28, 2022 at 3:55 AM Daniel Sahlberg wrote: > This commit doesn't look correct. > > I executed the generate-upcoming-changes-log.sh manually yesterday and it > created r1899244, removing a lot of log entries belonging to 1.14.1. This > commit (which was executed by cron) restores them.

SVN 1.10.x and 1.14.x coming soon-ish ... cast votes in STATUS

I intend to start the release process for SVN 1.10.x and 1.14.x in the near future. It would be great if we could get the STATUS files cleaned out so we can include as many fixes as possible in these releases. It has been a long time since we did a release so we may as well make it count. I am not

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

Den mån 28 mars 2022 kl 13:29 skrev Nathan Hartman : > On Mon, Mar 28, 2022 at 3:55 AM Daniel Sahlberg < > daniel.l.sahlb...@gmail.com> wrote: > >> This commit doesn't look correct. >> >> I executed the generate-upcoming-changes-log.sh manually yesterday and it >> created r1899244, removing a lot

Re: davautocheck failing on 1.14.x

Den mån 28 mars 2022 kl 12:54 skrev Mark Phippard : > On Sun, Mar 27, 2022 at 5:47 PM Daniel Sahlberg > wrote: > > Oops, it turns out I fixed it in r1892121. Now nominated for backport > (r1899265), applies cleanly in 1.14.x. > > > > If it is also needed in 1.10.x it must be done via a branch, it

Veto added to r1899227

Just an fyi .. I went through STATUS and merged most of the items to a 1.14.x WC and then ran all tests. They all run, which is great. However, r1899227 does not merge clean. I had to manually resolve conflicts. So that needs to be addressed so we can backport it? Stefan, if you just want to man

Re: Veto added to r1899227

Uggh ... so in looking at 1.10.x it occurred to me you need to merge the branch specified. Nevermind, will remove the veto and put it back Mark On Mon, Mar 28, 2022 at 10:31 AM Mark Phippard wrote: > > Just an fyi .. > > I went through STATUS and merged most of the items to a 1.14.x WC and > th

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

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, removing a lot of log entries belonging to 1.14.1. This > commit (which was exec

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

Once again I've executed this manually to make sure it correctly reflects the upcoming changes between 1.14.1 and 1.14.2. I hope infra will be able to merge my PR before 04.00Z tomorrow when the cronjobs are executed. Den mån 28 mars 2022 kl 21:56 skrev : > Author: svn-role > Date: Mon Mar 28 19:

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

What is this file used for? Is it displayed on the website somewhere? It is just showing merged changes since the last release? So I guess could help us write CHANGES? Mark On Mon, Mar 28, 2022 at 4:01 PM Daniel Sahlberg wrote: > > Once again I've executed this manually to make sure it correct

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

Den mån 28 mars 2022 kl 22:04 skrev Mark Phippard : > What is this file used for? Is it displayed on the website somewhere? > Yes, it is included in the release-notes page (via an SSI #include): https://subversion.apache.org/docs/release-notes/ It is just showing merged changes since the last re