Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] git.videolan.org -> git.ffmpeg.org migration
Date: Sun, 3 Aug 2025 21:55:16 +0200
Message-ID: <92263802-3d47-4314-9133-45f4b4edcb35@rothenpieler.org> (raw)
In-Reply-To: <2c197ba4-e073-4079-ad2a-a0fe5c1e27ca@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2423 bytes --]

On 8/3/2025 9:12 PM, James Almer wrote:
> On 8/3/2025 3:55 PM, Marton Balint wrote:
>>
>>
>> On Thu, 31 Jul 2025, Timo Rothenpieler wrote:
>>
>>> Hi!
>>>
>>> We will migrate away from using git.videolan.org to hosting the two 
>>> repos there on our own infrastructure.
>>>
>>> To accomplish this, the source.ffmpeg.org domain will be shifted to 
>>> point to git.ffmpeg.org, which will result in a host key mismatch for 
>>> anyone having configured that domain.
>>>
>>> You can verify the hostkeys against these:
>>>
>>> RSA:
>>> ssh-rsa 
>>> AAAAB3NzaC1yc2EAAAADAQABAAABAQDLI6KmhvYyBuyjRLC1BgyMHqZzBkloPfnPKJfjVhlE/QsPIQndH1BvzDbCk8478Urhk0ItpeoQL7hXj5D0y1rX5T0GBG1mIZnJBv+Xt9SPbyPoKdw8PN2txCp7TQENg1O5hCNvoQlZwuWb6WKJUVeYLbOZ0RmLO/xIU+7qWA6Puzoh2XDqKeqOZPq6DYqQ54cu/wLgaad2dpt9/9bKG94FuRKjKoV69KIbNi7r1f61fvD+/VzlMFKAn8/exKti7Ri1Lou46ktWzeTiTZJcxlwVhlDCs4a7MLI3EGcFQfmQwp5+IboSbhEVJPG0cDvpBsPUWS2xDLwbTwpe7vCFRjvtSHA256:bhJ5vOolMErZDtjgCMsLJyIN5HjEaW7uKCcMG2NW9ac
>>>
>>> ECDSA:
>>> ecdsa-sha2-nistp256 
>>> AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBIgtTBIsJoRV8dmPZw0ts+aPWoghuiaZNwhwbll6fVdz/7PtiXnb3gZ1+wDOr5YlNwULWeC2G6DqO/Z3/Fcix1k=SHA256:kV8/ZHnh6ssUlwzlxfbnG/qw2wVDCmQ1bi20M2+7P1g
>>>
>>> ED25519:
>>> ssh-ed25519 
>>> AAAAC3NzaC1lZDI1NTE5AAAAIEaJh7gNDPaMtU7LFBIEi8ihgPv2i6SRenc1ZmO8oqojSHA256:U/sLwQbVywk3oeI1CP2h1yTs6keVtDLGx+CqEGmwq48
>>>
>>>
>>> If you have been pushing to git.videolan.org, you will need to change 
>>> that domain to source.ffmpeg.org. You can do that at any time, it 
>>> works before and after the shift. But will run into aforementioned 
>>> hostkey issues if you connect to it before the shift.
>>>
>>> This change is to enable a parallel use with code.ffmpeg.org, since 
>>> we have more flexibility to configure mirroring and forwarding 
>>> between our own servers.
>>>
>>> git.videolan.org will turn into a read-only mirror.
>>
>> Newer commits do not appear here as far as I see.
> 
> Someone pushed a commit to the new infra and the g.v.o hooks rejects it 
> (No new line at the end of some file) and obviously every commit after 
> it, so until that's disabled it can't be synced.

I've been trying to get ahold of videolan admins for days now, but no 
response, or just an "ok" but then no action.

Once they disabled the hooks, the repo should auto-sync near immediately 
again, at the latest with the next push.

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4742 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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-08-03 19:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31 18:35 Timo Rothenpieler
2025-07-31 19:03 ` Timo Rothenpieler
2025-07-31 20:16 ` Gyan Doshi
2025-07-31 21:49   ` Timo Rothenpieler
2025-07-31 21:26 ` Derek Buitenhuis
2025-07-31 21:57   ` Stephen Hutchinson
2025-07-31 22:49     ` Timo Rothenpieler
2025-08-03 18:55 ` Marton Balint
2025-08-03 19:12   ` James Almer
2025-08-03 19:55     ` Timo Rothenpieler [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=92263802-3d47-4314-9133-45f4b4edcb35@rothenpieler.org \
    --to=timo@rothenpieler.org \
    --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