Thanks for reacting so promptly. On Tuesday 19 October 2004 21:15, you wrote: > On Mon, Oct 18, 2004 at 04:51:17PM +0200, Frans Pop wrote: > Just reinstall the package when this happens and it should fix itself > up. I will upload a fix.
I edited the postrm script so it didn't fail any more and managed to remove the package cleanly in that way. > > P.S. I feel it is fairly ridiculous that this package together with > > lib64gcc1 and lib64stdc++6 are installed by default on all systems as > > most systems are not 64 bit and have absolutely no use for them. > > Especially if you consider their size (12MB total)! > > You may want to talk to the debian-installer team about this. I don't > know why it happens. As it happens I'm a member of the d-i team (actually I was testing d-i when I noticed this problem). In line with Debian policy, d-i installs _every_ package available for an architecture that a) is in base OR b) has priority 'standard' or higher. As lib64stdc++6 is both 'base' and 'important', it gets installed and pulls in amd64-libs and lib64gcc1 because of it's dependencies. lib64gcc1 would get installed in it's own right as it is priority 'required'. I have no idea how the sections and priorities for these packages have been decided, but to me they seem very high. Especially as I can see no other packages in base or with high priorities that depend on these libs. Moving lib64stdc++6 to libs and giving both lib64stdc++6 and lib64gcc1 priority 'optional' should fix this. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
