[FFmpeg-devel] git.videolan.org -> git.ffmpeg.org migration
Timo Rothenpieler
timo at rothenpieler.org
Sun Aug 3 22:55:16 EEST 2025
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4742 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20250803/57973fcf/attachment.bin>
More information about the ffmpeg-devel
mailing list