How about it?
>>> Emerging (1 of 1) sci-electronics/gwave-20120229-r1::gentoo >>> Failed to emerge sci-electronics/gwave-20120229-r1, Log file: >>> '/var/tmp/portage/sci-electronics/gwave-20120229-r1/temp/build.log' >>> Jobs: 0 of 1 complete, 1 failed Load avg: 0.83, 0.31, 0.12 >>> Downloading 'http://mirrors.tds.net/gentoo/distfiles/gwave-code-r249-trunk.zip' --2018-08-23 10:08:33-- http://mirrors.tds.net/gentoo/distfiles/gwave-code-r249-trunk.zip Resolving mirrors.tds.net... 216.165.129.134 Connecting to mirrors.tds.net|216.165.129.134|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2018-08-23 10:08:33 ERROR 404: Not Found. >>> Downloading 'https://sourceforge.net/code-snapshots/svn/g/gw/gwave/code/gwave-code-r249-trunk.zip' --2018-08-23 10:08:33-- https://sourceforge.net/code-snapshots/svn/g/gw/gwave/code/gwave-code-r249-trunk.zip Resolving sourceforge.net... 216.105.38.13 Connecting to sourceforge.net|216.105.38.13|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-08-23 10:08:33 ERROR 404: Not Found. !!! Couldn't download 'gwave-code-r249-trunk.zip'. Aborting. * Fetch failed for 'sci-electronics/gwave-20120229-r1', Log file: * '/var/tmp/portage/sci-electronics/gwave-20120229-r1/temp/build.log'
I had previously built gwave-20120229 and had the zipfile downloaded for that in /usr/portage/distfiles, but it was named gwave-code-249-trunk.zip (not gwave-code-r249-trunk.zip). Digest verification failed. Going to https://sourceforge.net/p/gwave/code/249/tarball will regenerate the file for download, but (again) digest verification fails. Manifest should be updated: DIST gwave-code-r249-trunk.zip 418899 BLAKE2B 763f5087d2a564272576ef88dc1f29e7bc62c39c220e89ee67c19cb98e5acd6ce71281cd26cc72d5f321a2d476080dad66b73b532e5c0605416702337942947d SHA512 ede4d85c8ba46cdc9553d725a651c9221c48cfacdb6ae548d36d083afad6bc5a40ce0b6c2a8838d40f63462524290662c0776992f55d9b7dd64af1fe543ea7e8
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=12d8000851fe56574097946cc503d7efae20ca62 commit 12d8000851fe56574097946cc503d7efae20ca62 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2018-08-25 22:43:02 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2018-08-25 22:53:00 +0000 sci-electronics/gwave: Revert back to old tarball This reverts 5dfa4f57d8fa86f4eb7ccea80088a025c72f177f and faulty SRC_URI to use the existing tarball from GENTOO_MIRRORS. Bug: https://bugs.gentoo.org/664230 Package-Manager: Portage-2.3.48, Repoman-2.3.10 sci-electronics/gwave/Manifest | 2 +- sci-electronics/gwave/gwave-20120229-r1.ebuild | 22 +++++++++------------- sci-electronics/gwave/gwave-20120229.ebuild | 2 +- 3 files changed, 11 insertions(+), 15 deletions(-)
An automated check of this bug failed - repoman reported dependency errors (63 lines truncated): > dependency.bad sci-electronics/gwave/gwave-20120229-r1.ebuild: DEPEND: amd64(default/linux/amd64/17.0) ['x11-libs/guile-gtk'] > dependency.bad sci-electronics/gwave/gwave-20120229-r1.ebuild: RDEPEND: amd64(default/linux/amd64/17.0) ['x11-libs/guile-gtk'] > dependency.bad sci-electronics/gwave/gwave-20120229-r1.ebuild: DEPEND: amd64(default/linux/amd64/17.0/desktop) ['x11-libs/guile-gtk']
Okay, considering bug 647536 and bug bug 577630 this probably will not lead anywhere. bug 647114 is super confusing. Should old gwave simply be dropped and consequently put back to ~arch? Does a newer version not depend on guile-gtk anymore?
(In reply to Andreas Sturmlechner from comment #5) > Okay, considering bug 647536 and bug bug 577630 this probably will not lead > anywhere. bug 647114 is super confusing. > > Should old gwave simply be dropped and consequently put back to ~arch? Does > a newer version not depend on guile-gtk anymore? Correct, newer version doesn't depend on guile-gtk or even guile-gnome-platform. I just bumped it, so I guess we'll let this bake a little before cc'ing arches.
Let's do it.
amd64 stable
x86 stable. Closing.
