** Summary changed: - Dependency cycle: g++-4.1 and libstdc++6-4.1-dev + Dependency cycle: g++-4.x and libstdc++6-4.x-dev
** Description changed: - Binary package hint: g++-4.1 + The package g++-4.1 depends on libstdc++6-4.1-dev, but + libstdc++6-4.1-dev depends on g++-4.1. Such loops should not be allowed + since they prevent usage of non-repository-based package installation + procedures like gdebi and dpkg -i. People who do not have internet + connections may need to use such non-repository-based procedures after + downloading from elsewhere. Dependency cycles shut out such users so + they should not be allowed. - In feisty, the package g++-4.1 depends on libstdc++6-4.1-dev, but - libstdc++6-4.1-dev depends on g++-4.1. I didn't think such loops were - allowed. - - The same situation exists in dapper, with version 4.0 instead of 4.1, so - this is not a new problem with feisty. - - It probably doesn't cause problems if apt-get is used to install the - packages. However, if someone without an internet connection is - installing packages by downloading them elsewhere and then using gdebi - to install them, it will not be possible to to install g++-4.1. This - situation was reported here: - http://ubuntuforums.org/showthread.php?t=476786 + This problem exists since Dapper where it was with version 4.0. With + Feisty it is with version 4.1. With Gutsy it is with both 4.1 and 4.2. -- Dependency cycle: g++-4.x and libstdc++6-4.x-dev https://bugs.launchpad.net/bugs/120935 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
