With findutils 4.2.18, running the init script fills the screen with warnings. * Stopping X Font Server ... [ ok ] * Scanning font directories ... find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. [ ok ] * Indexing font directories ... * /usr/share/fonts/freefont ... The fix is easy. Change line 37 from: fontlist="$(find $1/ -type f -maxdepth 1 | \ to: fontlist="$(find $1/ -maxdepth 1 -type f | \
Same here. Apparently the order of parameters for the "find" command is important now. Looks like a simple editing problem for /etc/init.d/xfs.
The order of parameters was always important. It's just that the new find tells you when it's being lax and letting you get away with things that shouldn't really work.
*** Bug 83376 has been marked as a duplicate of this bug. ***
*** Bug 83453 has been marked as a duplicate of this bug. ***
Sorry I assumed that order wasn't important before. Apparently that's untrue. Anyway, the messages still remain.
*** Bug 87736 has been marked as a duplicate of this bug. ***
Do you mean that the messages still remain after applying Aaron's suggested fix, or the Portage copy hasn't been fixed yet? I see that the current xfs script does not contain the suggested fix.
Yeah, I've got a big pile of stuff on my X todo list, and I haven't had time to sit down and work on it for a couple of weeks. Hopefully soon.
I can write the patch if you'd like, and I confirm that the suggested fix works on my system. Does the xfs script originate from the xorg package? I did a quick search through the source and I can't find it, and it installs whether or not the font-server useflag is enabled.
In the xorg ebuild: exeinto /etc/init.d ... if use font-server; then newexe ${FILES_DIR}/xfs.start xfs insinto /etc/conf.d newins ${FILES_DIR}/xfs.conf.d xfs fi You'll find it in the files tarball. But no need to make the patch yourself, I can do that when I'm doing the rest of the work.
Alright, let me know as summer comes if you'd like me to help with that list of yours :P
Should be fixed in 6.8.2-r2.
*** Bug 89714 has been marked as a duplicate of this bug. ***
*** Bug 89924 has been marked as a duplicate of this bug. ***
*** Bug 91076 has been marked as a duplicate of this bug. ***
*** Bug 95567 has been marked as a duplicate of this bug. ***
(In reply to comment #12) > Should be fixed in 6.8.2-r2. This package is still hard-masked, could you please also patch this in xorg-x11-6.8.2-r1?
No, stable packages are intended to not change. -r2 will be unmasked shortly.
(In reply to comment #18) > No, stable packages are intended to not change. -r2 will be unmasked shortly. This sounds very stupid if you have a broken stable package...
(In reply to comment #18) > No, stable packages are intended to not change. -r2 will be unmasked shortly. I thought they were intended to really work. Fixing a bug in "stable branch" should be good.
And the way to fix is to provide a new ebuild, instead of changing an old one in ways that aren't widely tested and may break it in a new way while fixing one problem. Plus this is a syntax warning, not a build breakage, calm down.
