After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 790501 - recipes/fribidi: archive not found, build from sources not working
recipes/fribidi: archive not found, build from sources not working
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: cerbero
git master
Other Mac OS
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-11-17 13:34 UTC by Andrew Achkar
Modified: 2018-05-04 13:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andrew Achkar 2017-11-17 13:34:00 UTC
The fribidi recipe https://github.com/GStreamer/cerbero/blob/master/recipes/fribidi.recipe refers to a source tarball: http://fribidi.org/download/fribidi-0.19.7.tar.bz2, which no longer exists (returns Not Found). 

Unfortunately just swapping out that archive for the source archive on github https://github.com/fribidi/fribidi/archive/0.19.7.tar.gz doesn't work. The build fails with the github source. 

The previous release tarball (.bz2) includes in it some pre-bootstrapped files which are not included in the github source, as I found out by asking about it upstream:  issue upstream: https://github.com/fribidi/fribidi/issues/28. 

I do not yet have a solution for how to fix the recipe to build from the github source and have resorted to using a previously downloaded version of the release tarball, but it would be best to figure out how to get the recipe building properly from the github non-release source.
Comment 1 Tim-Philipp Müller 2017-11-18 16:12:07 UTC
Could you try again?

I've put the .tar.bz2 from debian into our source mirror, which it should fall back to if there's a problem with the original url.
Comment 2 Edward Hervey 2017-11-19 17:59:05 UTC
stupid github ... Instead of returning a 404 error code it returns ... a file with "Not Found" in it *sigh*
Comment 3 Edward Hervey 2017-11-20 08:05:08 UTC
Temporarily forced the tarball location to our mirror until this gets properly fixed.
Comment 4 Sebastian Dröge (slomo) 2017-11-20 08:09:00 UTC
Did you or someone else report this to GitHub?
Comment 5 Andrew Achkar 2017-11-20 13:17:45 UTC
I am seeing a 404 error from github:

wget https://github.com/fribidi/fribidi/download/fribidi-0.19.7.tar.bz2
--2017-11-20 08:15:17--  https://github.com/fribidi/fribidi/download/fribidi-0.19.7.tar.bz2
Resolving github.com... 192.30.253.113, 192.30.253.112
Connecting to github.com|192.30.253.113|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-11-20 08:15:17 ERROR 404: Not Found.


Also in Chrome, I see in the console:
Failed to load resource: the server responded with a status of 404 (Not Found)
Comment 6 Andrew Achkar 2017-11-20 14:12:14 UTC
Just to be clear, my last comment is not a new issue, just noting that I don't think github.com is doing anything wrong. From what I can tell, they are returning error 404 on the missing archive link.
Comment 7 Sebastian Dröge (slomo) 2018-05-04 13:32:04 UTC
commit dbbd47b842df2438f7ba7ca872b60766b60abc6d
Author: Edward Hervey <edward@centricular.com>
Date:   Wed Feb 21 09:53:57 2018 +0100

    recipes/fribidi: Upstream fixed the archive issue

commit 53fb985cdf9f33ffd48270cf1b7806cbd0ba42a1
Author: Edward Hervey <edward@centricular.com>
Date:   Mon Nov 20 09:05:17 2017 +0100

    recipes/fribidi: Use our mirror
    
    https://bugzilla.gnome.org/show_bug.cgi?id=790501