Check attached build log.
Created attachment 167340 [details] Build log
Confirmed on two more systems.
That's what is called inside the ebuild, for certain files iconv -f man8/vmstat.8: text/troff -t iso8859-1 /var/tmp/portage/app-i18n/man-pages-es-1.55-r1/work/man-pages-es-extra-0.8a/man8/vmstat.8 -o /var/tmp/portage/app-i18n/man-pages-es-1.55-r1/image//usr/share/man/es/man8/vmstat.8 you could try to filter out the ones not reporting the charset to avoid the iconv error related. btw the postinst text suggest to use -T utf8 when you are supposedly converting them to latin1. I hope it helps a bit.
(In reply to comment #2) > Confirmed on two more systems. > With all those details I'm sure I'll be able to diagnose the error and fix it real soon now. - ferdy
Beside the fact that Luca _did_ provide you quite a bit of details, you either wrote or maintain the ebuild, and that's the whole output of it, do you tell me it does not output any error for you on any of your systems?
Exactly, no error. Just a harmless warning that has been there forever. Details would include your glibc version... for instance. - ferdy
If you wanted to know glibc version you could have just asked for it, no? sys-libs/glibc-2.8_p20080602 (~arch). The errors are not fatal because you didn't add || die to the iconv command so it's not aborting the build even in case of error (which I would expect is not too bad, since it's just conversion). But as Luca pointed out it doesn't seem to be a problem with the iconv version per se but rather with the commandline passed to it, so the problem is in the ebuild.
(In reply to comment #7) > If you wanted to know glibc version you could have just asked for it, no? > sys-libs/glibc-2.8_p20080602 (~arch). Well, I thought posting such basic information (emerge --info) was required for both users and developers when reporting a bug. > The errors are not fatal because you didn't add || die to the iconv command so > it's not aborting the build even in case of error (which I would expect is not > too bad, since it's just conversion). But as Luca pointed out it doesn't seem > to be a problem with the iconv version per se but rather with the commandline > passed to it, so the problem is in the ebuild. What's your file version? I wonder why aren't you getting any charset for those files while I am. - ferdy
Also ~arch, file-4.26; it's happening on full ~arch systems both with and without unicode/nls USE flags. I'm going to sleep soonish, but if you want tomorrow I can give you file -i output of the whole source package in here.
Ok, the systems I tried are stable (and can even be a bit outdated). That output would be helpful, I guess. - ferdy
Created attachment 167397 [details] file(1) output for all the man pages Seems like file does not output charset information for text/troff files (maybe it assumes UTF-8). You might want to contact upstream on that.
Moving to maintainer-needed since Ferdy left Gentoo.
Dropped
