libav.org is not resolving

John Neffenger john at status6.com
Wed Jan 4 16:11:19 UTC 2023


I've been unable to get the GitHub archive working as a replacement. I 
think the problem is due to the lack of the file name in the URL, which 
our Gradle build file expects:

   https://github.com/libav/libav/archive/v12.1.tar.gz
   ==> content-disposition: attachment; filename=libav-12.1.tar.gz

   <component group="" name="libav-12.1" version="">
     <artifact name="libav-12.1-.tar.gz">
       <sha256 value="f08d48bf...2a4527e1" origin="Generated by Gradle"/>
     </artifact>
   </component>

I notice we're building both Libav and FFmpeg, but I think we can drop 
Libav now. I know it's gone back and forth even in the Linux 
distributions between the original and fork, but it seems the forking 
battle is finally over. Wikipedia says:

   "As of 2022, Libav is an abandoned software project, with Libav 
developers either returning to FFmpeg, moving to other multimedia 
projects like the AV1 video codec,[17] or leaving the multimedia field 
entirely."
https://en.wikipedia.org/wiki/Libav#Fork_from_FFmpeg

Maybe that's why the domain name is no longer resolving: nobody is 
around to fix it anymore. Can we remove it from the build?

John

On 1/4/23 3:00 AM, Johan Vos wrote:
> Hi John,
> 
> Thanks for pointing this out. Our automated builds are failing for the 
> same reason. It's not the first time that this dependency on the libav 
> website hits us, and I agree it's better indeed to depend on the github 
> repositories (which are also not guaranteed to be available though).
> 
> - Johan



More information about the openjfx-dev mailing list