Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] configure: Improve the check for the rsync --contimeout option
Date: Tue, 28 Jan 2025 19:56:19 +0200 (EET)
Message-ID: <ab292e51-6d2d-555c-7765-8a6eb3bbf792@martin.st> (raw)
In-Reply-To: <17B4C479-AC1A-4694-B79C-FD35445AFCD0@gmail.com>

On Tue, 28 Jan 2025, epirat07@gmail.com wrote:

> On 24 Jan 2025, at 22:40, Martin Storsjö wrote:
>
>> Traditionally, macOS has shipped an old version of rsync that lacked
>> support for this version, hence this check (added in
>> a8b3f0c5cf548f654e30c981988bb71981a3f8d3).
>>
>> However, in macOS 15.x, they have switched to providing rsync as a
>> different tool, openrsync. The version of openrsync in at least
>> macOS 15.2 does include "[--contimeout]" (note the lack of "=" after
>> the option), in the output of "rsync --help", but when used, the tool
>> errors out with "rsync: --contimeout=60: unknown option". So apparently
>> the tool erroenously lists the option as supported, while it really
>> isn't.
>>
>> The original rsync tool prints "--contimeout=SECONDS" in the output
>> of "rsync --help".
>>
>> It is unclear which version of openrsync this is; the latest upstream
>> openrsync from OpenBSD does support the option and includes
>> "[--contimeout=seconds]" in the output of "--help", and older versions
>> don't seem to include the option as listed at all.
>>
>> Therefore, check for "--conntimeout=" with the "=", this should
>> properly detect both new enough rsync and openrsync.
>>
>> This fixes running "fate-rsync" on macOS 15.x.
>
> Thanks, tested and can confirm that it fixes the rsync failure on macOS 15.x
> while not breaking macOS 14.x.
>
> LGTM

Thanks, pushed!

// Martin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

      reply	other threads:[~2025-01-28 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 21:40 Martin Storsjö
2025-01-25  9:47 ` Vittorio Giovara
2025-01-28 16:01 ` epirat07
2025-01-28 17:56   ` Martin Storsjö [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ab292e51-6d2d-555c-7765-8a6eb3bbf792@martin.st \
    --to=martin@martin.st \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git