reassign 498934 gcc-4.4-base,gcc-4.5-base,gcc-4.6-base,gcc-4.7-base found 498934 gcc-4.4/4.4.7-1 found 498934 gcc-4.5/4.5.3-12 found 498934 gcc-4.6/4.6.3-4 found 498934 gcc-4.7/4.7.0-6 severity 498934 minor stop
Hello, Thanks for the detailed bug report and your interest in improving Debian. Sorry that the bug was unattended for so long. I'm just doing some cleanup, I am not involved with the GCC package. All of these GCC versions have the package as "required": ------------------------------------------------------------------------------------ # aptitude show '~ngcc-.\..-base' | egrep "(Package|Priority)" Package: gcc-4.6-base Priority: required Package: gcc-4.4-base Priority: required Package: gcc-4.7-base Priority: required Package: gcc-4.5-base Priority: required ------------------------------------------------------------------------------------ According with the policy: http://www.debian.org/doc/debian-policy/ch-archive.html "required: Packages which are necessary for the proper functioning of the system (usually, this means that dpkg functionality depends on these packages). Removing a required package may cause your system to become totally broken and you may not even be able to use dpkg to put things back, so only do so if you know what you are doing. Systems with only the required packages are probably unusable, but they do have enough functionality to allow the sysadmin to boot and install more software." I don't think that, according to the definition, these packages are of priority "required" at all. None of them are really required for dpkg or anything else, in fact only one of them is usually installed at the same time. On the other hand, maybe there's some explanation about why the package is required. And it's very difficult or impossible to have a regular system installed without one of the gcc-*-base package, so the question of whether is priority "required" or not it's will not have much effect at the end of the day, I think. So I think that the best way to go forward is to reassign the bug to the current packages presenting the behaviour and let the maintainers deal with it. Cheers. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
