Please refer to : https://pastebin.com/q55ywLTY
Architecture used: Linux kali 4.14.0-kali3-amd64 0000001 SMP Debian 4.14.17-1kali1 (2018-02-16) x86_64 GNU/Linux
The system was runnning in a VirtualBox Virtual Machine with 3.2GHz 4 Cores Intel CPU/ 7.5GB RAM/ 32GB SSD
klimt
2018-03-02 21:45
reporter ~0008838
Initially observed during building a custom Kali ISO with the 'kali-all' meta-package defined. Please refer to attached 'build.log' file.
g0tmi1k
2018-03-03 09:18
administrator ~0008841
Last edited: 2018-03-03 11:39
Guessing its due to an issue with sourceforge for the last few weeks:
Migrating data centeres --- 13th February ~ https://twitter.com/sfnet_ops/status/963523793489743873 --- 14th February ~ https://twitter.com/sfnet_ops/status/963594035712708609 --- 15th February ~ https://twitter.com/sfnet_ops/status/963995439224836096 --- 16th February ~ https://twitter.com/sfnet_ops/status/964338087907266560 --- 18th February ~ https://twitter.com/sfnet_ops/status/965055907557269504
"Technical issues" --- 24th February ~ https://twitter.com/sfnet_ops/status/967263989393772545
DDoS --- 25th February ~ https://twitter.com/sfnet_ops/status/967809090545180672 --- 26th February ~ https://twitter.com/sfnet_ops/status/967960888027373568
"Technical issues" --- 1st March ~ https://twitter.com/sfnet_ops/status/969017161686626304 --- 2nd March ~ https://twitter.com/sfnet_ops/status/969377360129773568 --- 3rd March ~ https://twitter.com/sfnet_ops/status/969743281922936832
rhertzog
2018-03-04 21:21
administrator ~0008852
Issues are resolved on sourceforge's side. The package installs fine again.
2018-05-08 07:57
administrator ~0009137
Service is back up
