From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 316ED449F0 for ; Mon, 31 Oct 2022 17:51:35 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 633DF68BE0E; Mon, 31 Oct 2022 19:51:32 +0200 (EET) Received: from milliways.cryptomilk.org (milliways.cryptomilk.org [78.46.21.5]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id DDD4768BC47 for ; Mon, 31 Oct 2022 19:51:25 +0200 (EET) Received: from milliways.cryptomilk.org (localhost [127.0.0.1]) by milliways.cryptomilk.org (Postfix) with ESMTPS id 22C17B304E5A; Mon, 31 Oct 2022 18:51:25 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptomilk.org; s=dkim; t=1667238685; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+tDGV15n/NcsHF1SLEyQJ7BSIS6IbaUQU40kHNz4Ef4=; b=GWuBAvuH5guJVKcGn4odH6rr3KiXOUQkJi5IKIUxXQQoj8Jq/wJvy4A7/wOBGReG5boTHX /X1X1CIjHeVdSHwaU6gEKUPClSa30jpK0lWhvDZiIv4FvLiI/8iiGzL4sOaiwnt581Cwkr iGYeys64uyUpUmA2K3BP2T7CqaTcqWDUldQOzuHdraS921dTPNhlf7kViLGy8g/zCi8LDJ jEWKZjVvON0i+9u8OTIO7WWHCoHmB3lBD8OreDZFyUJbW3J5mh/PY/exUZjxp9FdZfZ1vg kEhqSJu/PlFIdMMfqJzO/OA7Sa/EdK++oPfLIdKy5Zqb5x9YrujofSl04yaLosUFSfioIN 2gDtJHh+OuRONfuaaP9kHL005kAM9dDUDhQqNCwRRuYdTkuIFJDaTlAte/cKHtLmzBbsQE rBsLaplbivhcBdz6O4z5NsOywWZ8yqviudy6lt30/AsdOLgJtWCMwFOCqqiR8vrd51rUcG 6iv8yYsefQM9iYA0DqlaEwD95tw/Fk6IEdWsR39vqsJnWO+Y9657rB4w4BEhq7hi0EbXSo CUHpiEupW6l4T3SuTHbnViGmlzoinKMw/iB6JNe56y4JjiHB6yyZ7PJFsbAfhCJX1uAx95 RlbcxUgtBRc5TeCTCA00ke1YS8uAIu/n3+K3bRJv+tgVcAC7bS8RI= Received: from magrathea.localnet (unknown [IPv6:2001:a61:25fb:9001:3c66:5737:e4b5:d10e]) by milliways.cryptomilk.org (Postfix) with ESMTPSA id EF1FDB304E59; Mon, 31 Oct 2022 18:51:24 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptomilk.org; s=dkim; t=1667238685; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+tDGV15n/NcsHF1SLEyQJ7BSIS6IbaUQU40kHNz4Ef4=; b=GWuBAvuH5guJVKcGn4odH6rr3KiXOUQkJi5IKIUxXQQoj8Jq/wJvy4A7/wOBGReG5boTHX /X1X1CIjHeVdSHwaU6gEKUPClSa30jpK0lWhvDZiIv4FvLiI/8iiGzL4sOaiwnt581Cwkr iGYeys64uyUpUmA2K3BP2T7CqaTcqWDUldQOzuHdraS921dTPNhlf7kViLGy8g/zCi8LDJ jEWKZjVvON0i+9u8OTIO7WWHCoHmB3lBD8OreDZFyUJbW3J5mh/PY/exUZjxp9FdZfZ1vg kEhqSJu/PlFIdMMfqJzO/OA7Sa/EdK++oPfLIdKy5Zqb5x9YrujofSl04yaLosUFSfioIN 2gDtJHh+OuRONfuaaP9kHL005kAM9dDUDhQqNCwRRuYdTkuIFJDaTlAte/cKHtLmzBbsQE rBsLaplbivhcBdz6O4z5NsOywWZ8yqviudy6lt30/AsdOLgJtWCMwFOCqqiR8vrd51rUcG 6iv8yYsefQM9iYA0DqlaEwD95tw/Fk6IEdWsR39vqsJnWO+Y9657rB4w4BEhq7hi0EbXSo CUHpiEupW6l4T3SuTHbnViGmlzoinKMw/iB6JNe56y4JjiHB6yyZ7PJFsbAfhCJX1uAx95 RlbcxUgtBRc5TeCTCA00ke1YS8uAIu/n3+K3bRJv+tgVcAC7bS8RI= From: Andreas Schneider To: FFmpeg development discussions and patches , Jan Engelhardt , Andreas Schneider Date: Mon, 31 Oct 2022 18:51:23 +0100 Message-ID: <12093289.O9o76ZdvQC@magrathea> In-Reply-To: <166722140107.12287.4175132527138383610@lain.khirnov.net> References: <20221028182333.GJ4048598@pb2> <166722140107.12287.4175132527138383610@lain.khirnov.net> MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] FFmpeg 5.0 X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On Monday, 31 October 2022 14:03:21 CET Anton Khirnov wrote: > Quoting Neal Gompa (2022-10-30 22:04:42) > > > On Sun, Oct 30, 2022 at 4:10 PM Michael Niedermayer > > > > wrote: > > > On Sat, Oct 29, 2022 at 02:29:56PM -0400, Neal Gompa wrote: > > > > On Fri, Oct 28, 2022 at 2:23 PM Michael Niedermayer > > > > > > > > wrote: > > > > > Hi > > > > > > > > > > According to our > > > > > https://trac.ffmpeg.org/wiki/Downstreams > > > > > > > > > > Noone and nothing is using 5.0 > > > > > should i make another release of 5.0 ? > > > > > should i move 5.0 to olddownloads ? > > > > > > > > > > does anyone use it ? plan to use it or know of someone using it ? > > > > > > > > Fedora 36 still uses FFmpeg 5.0 as I discovered there was an ABI break > > > > that made upgrading to FFmpeg 5.1 not possible for F36. FFmpeg 5.1 is > > > > used for Fedora 37, though. > > > > > > > > This had apparently been also discovered by openSUSE some time ago: > > > > https://build.opensuse.org/package/view_file/multimedia:libs/ffmpeg-5/ > > > > work-around-abi-break.patch?expand=1> > > > > You can replace 5.0 by 5.1 but not 5.1 by 5.0, The compatibility is only > > > in one way. > > > Iam assuming here you talk about the addition of functions and there is > > > not some other issue iam not aware of. > > > > My understanding is that when using symbol versions, modifying the > > symbol table creates a breakage on its own. > > Do you have some authoritative source for this claim? So far all the > arguments I've seen were along the lines of "because I say so". > > > > > Do we have ABI testing in place for submitted patches? I haven't seen > > > > any evidence of CI testing of patches submitted to the mailing list, > > > > but maybe I'm looking in the wrong place? If there is, maybe we can > > > > consider adding some kind of ABI testing for release branches, using > > > > tools like libabigail[1] with abidiff[2]? > > > > > > > > [1]: https://sourceware.org/libabigail/ > > > > [2]: https://www.mankier.com/1/abidiff > > > > > > iam not sure there is agreement between you and others of what is a ABI > > > break so the tool maybe will not help. > > > > > > I have generaly done testing with replacing old libraries by new when > > > doing > > > releases. But for me a ABI break is if replacing a library by another > > > breaks some binary that is not rebuild and linked to the new lib. > > > > > > More testing is always good and welcome of course. > > > > Yeah, I think that qualifying how ABI is validated in a reproducible > > way would be useful. The abigail tooling can help here, In Fedora, > > every update runs through abigail validation too. I vaguely recall > > that it warned me when I did the update in Rawhide, which is how I wound > > up talking to Jan in openSUSE and RPM Fusion maintainers, who both > > didn't refresh FFmpeg on stable branches with 5.0 to 5.1. > > > > It's also entirely possible that I was *too* cautious, and I'm okay > > with having a conversation that leads me to do differently in the future. > > Having automated ABI testing would be definitely a good idea, not all > developers understand how ABI compatibility works and there have been > breakages (according to our definition) recently. > > I also have https://github.com/lvc/abi-compliance-checker/ on my > to-look-at list, but as always time is lacking. At libssh we use https://github.com/ansasaki/abimap for symbol versioning. Ask if master could be added to ABI Laboratory: https://abi-laboratory.pro/index.php?view=timeline&l=ffmpeg Just my 2c. Andreas -- Andreas Schneider asn@cryptomilk.org GPG-ID: 8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D _______________________________________________ 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".