Bug 649624 – net-misc/gns3-server-2.3.1 should depend on dev-python/prompt_toolkit =dev-python/aiohttp-cors-0.5.3

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description needle 2018-03-05 10:01:50 UTC]

First of all thank you for bumping the gns3 ebuild.

Running the 2.3.1 version of (gns-server and gns3-gui) resulted in 2 missing dependencies. It does not run without these both.

1. dev-python/prompt_toolkit
2. =dev-python/aiohttp-cors-0.5.3

The aiohttp-cors-0.6.0 is to new for this gns3-server version. It asks explicitely for a version:

"The 'aiohttp-cors<0.6.0,>=0.5.3' distribution was not found and is required by gns3-server"

After both ebuilds have been installed. 
The application runs correctly.

[Comment 1 needle 2018-03-05 10:04:19 UTC]

Created attachment 522434 [details]
error logging gns3 console

[Comment 2 needle 2018-03-05 10:06:59 UTC]

Created attachment 522436 [details]
ebuild for the requested aiohttp-cors version

This ebuild is the same as the aiohttp-cors 0.6.0. 
The version has been changed to 0.5.3.

[Comment 3 needle 2018-03-09 09:26:23 UTC]

Seems the problem has been fixed with the gns3-server-2.1.3-r1 and net-misc/gns3-gui-2.1.3-r1 version that has appeared some days ago.
The aiohttp-cors-0.5.3 has been added to portage and it installs also prompt_toolkit.

now "emerge gns3-gui" command pulls following:

[ebuild  N     ] dev-python/prompt_toolkit-1.0.15::gentoo  USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 python3_5 -python3_6" 0 KiB
[ebuild  N    ~] dev-python/aiohttp-cors-0.5.3::gentoo  USE="{-test}" PYTHON_TARGETS="python3_4 python3_5 -python3_6" 0 KiB
[ebuild  N    ~] net-misc/gns3-server-2.1.3-r1::gentoo  PYTHON_TARGETS="python3_4 python3_5 -python3_6" 0 KiB
[ebuild  N    ~] net-misc/gns3-gui-2.1.3-r1::gentoo  PYTHON_TARGETS="python3_4 python3_5 -python3_6" 0 KiB

The bug is fixed and gns3 works out of the box over here.

[Comment 4 needle 2018-03-09 09:27:06 UTC]

Created attachment 523080 [details]
emerge --info output

[Comment 5 needle 2018-03-09 09:27:47 UTC]

Bug has been fixed. Please close this bug.