vte-0.53.0 fails to download source.
Closed this issue · 10 comments
I am doing a fresh install and vte fails to download the source package. Could someone please update the ebuild with a new source url or provide vte-0.53.0.tar.xz so I can continue my installation?
>>> Emerging (1 of 21) x11-libs/vte-0.53.0::gnome-next
* Fetching files in the background.
* To view fetch progress, run in another terminal:
* tail -f /var/log/emerge-fetch.log
>>> Downloading 'http://distfiles.gentoo.org/distfiles/vte-0.53.0.tar.xz'
--2018-06-12 07:49:37-- http://distfiles.gentoo.org/distfiles/vte-0.53.0.tar.xz
Resolving distfiles.gentoo.org... 216.165.129.135, 156.56.247.195, 140.211.166.134, ...
Connecting to distfiles.gentoo.org|216.165.129.135|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-06-12 07:49:37 ERROR 404: Not Found.
>>> Downloading 'https://git.gnome.org/browse/vte/snapshot/vte-0.53.0.tar.xz'
--2018-06-12 07:49:37-- https://git.gnome.org/browse/vte/snapshot/vte-0.53.0.tar.xz
Resolving git.gnome.org... 209.132.180.184
Connecting to git.gnome.org|209.132.180.184|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://gitlab.gnome.org/GNOME/vte/snapshot/vte-0.53.0.tar.xz [following]
--2018-06-12 07:49:37-- https://gitlab.gnome.org/GNOME/vte/snapshot/vte-0.53.0.tar.xz
Resolving gitlab.gnome.org... 209.132.180.181
Connecting to gitlab.gnome.org|209.132.180.181|:443... connected.
HTTP request sent, awaiting response... 401 Unauthorized
Username/Password Authentication Failed.
!!! Couldn't download 'vte-0.53.0.tar.xz'. Aborting.
* Fetch failed for 'x11-libs/vte-0.53.0', Log file:
* '/var/tmp/portage/x11-libs/vte-0.53.0/temp/build.log'
>>> Failed to emerge x11-libs/vte-0.53.0, Log file:
>>> '/var/tmp/portage/x11-libs/vte-0.53.0/temp/build.log'
* Messages for package x11-libs/vte-0.53.0:
* Fetch failed for 'x11-libs/vte-0.53.0', Log file:
* '/var/tmp/portage/x11-libs/vte-0.53.0/temp/build.log'
A temporary workaround to get gnome to build is to install vte 0.48.4. However emerge -1 vte or emerge -NuvD world tries to upgrade it and fails. Also gnome-terminal will not build without the newer vte.
Looks like gnome changed to gitlab and that the file no longer exists.
well it redirects okay when it falls back to the second url, but it seems to be saying you now need a username and password to fetch it? is that a feature of gitlab, or is it just that repository?
I believe that the file is not there and that is why gitlab is throwing the username/password error. I checked the url in a browser and no vte-0.53.0.tar.xz at gitlab. Firefox just says file not found. If you go to https://gitlab.gnome.org/GNOME/vte it works but there is just source code there not snapshot directory and no tar.xz files.
vte release tarballs exist on GNOME mirror infrastructure. I have no idea why the ebuild in this overlay is using a git snapshot of a tag instead of the release. Maybe it was shortly delayed to get uploaded to the normal release place or something, shrug.
Just remove SRC_URI completely, and it should work fine from default gnome2.eclass -> gnome.org.eclass setup, just like in main tree versions, albeit the manifest might need updating as well, as the proper download location might be properly disted, while snapshots are not. Relatedly this proper tarball might not need eautoreconf and co, as these tend to be pregenerated in the proper tarball (if still autotools based)
Yep... removing the SRC_URI and doing an ebuild digest got it to build. Thanks.
yes, I don't remember the reason but possibly because of delay, they often forget to deplay things when they announce them, current problem (seems like) is because of motion to gitlab
send PR, I'm slightly busy this week
alright, i've made one, see #264 . (on a sidenote why all the changes to gitlab? it seems worse to use than github)
GNOME has never used GitHub, only some unofficial mirrors of which most even auto-close any PR's and issues filed against them (if even enabled, but I think one of them wasn't possible to fully disable or something).
They moved from bugzilla + cgit to gitlab, nothing to do with GitHub. GitHub was never in consideration due to its closed nature and unsuitability with free and open source software views. GitLab they use only the community edition stuff afaik, so only stuff anyone could setup for themselves as well.
Lots of other stuff might be migrating due to MS buyout and GitLab PR making use of it.
oh i know it wasn't in this case, just, the UI seems to be worse? i guess there's nothing stopping it improving over time though