2020-11-19 16:20:31 ERROR 503: Service Unavailable. !!! Couldn't download 'FLASH-1.2.9.tar.gz'. Aborting. * Fetch failed for 'sci-biology/FLASH-1.2.9', Log file: * '/var/log/portage/sci-biology:FLASH-1.2.9:20201119-152030.log' ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no-multilib-libressl_science-20201116-220441 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.2.0 * /usr/lib/llvm/11 11.0.0 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) [4] python2.7 (fallback) The following VMs are available for generation-2: *) AdoptOpenJDK 8.272_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Thu Nov 19 02:35:38 PM UTC 2020 /var/db/repos/libressl Sat Nov 7 03:06:11 PM UTC 2020 emerge -qpvO sci-biology/FLASH [ebuild N ] sci-biology/FLASH-1.2.9
Created attachment 673153 [details] emerge-info.txt
Created attachment 673156 [details] emerge-history.txt
Created attachment 673159 [details] etc.portage.tbz2
Created attachment 673162 [details] sci-biology:FLASH-1.2.9:20201119-152030.log
Created attachment 689559 [details] emerge --info
Created attachment 689562 [details] ebuildtester emerge log
Created attachment 689565 [details] emerge.log
Created attachment 689568 [details] etc/portage
Created attachment 689571 [details] emerge-history.txt
This bug is either obselete or WORKSFORME. This bug was reported for FLASH version 1.2.9. The current version 1.2.11 compiles and runs correctly on a clean and current gentoo stage3 image created using ebuildtester. It also compiles and runs correctly on a regular machine. Therefore, it could have been fixed in an ebuild update. However, when I locally changed the ebuild from current version 1.2.11 to 1.2.9, it still installed correctly. I cannot get this bug to happen even when reverting to an older version. So maybe sourceforge/the bug reporter's internet was down? I noticed the reporter posted many similar bug reports. Either way it seems fixed.
Could we get an update on this bug? The reporter could not fetch the package successfully; however, my tests show the package can be fetched successfully, and even installs successfully. Since I am new please let me know of any advice or constructive criticism you would be able to give.
Created attachment 712050 [details] build.log of hardened profile and without fortran flag
Created attachment 712053 [details] config.log of hardened profile and without fortran flag
Created attachment 712056 [details] emerge-history.txt of hardened profile and without fortran flag
Created attachment 712059 [details] emerge-info.txt of hardened profile and without fortran flag
Created attachment 712062 [details] enviroment of hardened profile and without fortran flag
Created attachment 712065 [details] etc/portage of hardened profile and without fortran flag
I uploaded attachments on this bug report on accident, I am sorry for the mistake.
