Created attachment 289259 [details] emerge -info With USE=doc, the ebuild references a directory that doesn't exist. Relevant messages: >>> Install firebird-2.5.0.26074.0-r2 into /var/tmp/portage/dev-db/firebird-2.5.0.26074.0-r2/image/ category dev-db install: cannot stat `docs/*.pdf': No such file or directory !!! dodoc: docs/*.pdf does not exist * ERROR: dev-db/firebird-2.5.0.26074.0-r2 failed (install phase): * dodoc failed * * If you need support, post the output of 'emerge --info =dev-db/firebird-2.5.0.26074.0-r2', * the complete build log and the output of 'emerge -pqv =dev-db/firebird-2.5.0.26074.0-r2'. * The complete build log is located at '/var/log/portage/emerge/dev-db:firebird-2.5.0.26074.0-r2:20111008-195137.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-db/firebird-2.5.0.26074.0-r2/temp/environment'. * S: '/var/tmp/portage/dev-db/firebird-2.5.0.26074.0-r2/work/Firebird-2.5.0.26074-0' * QA Notice: file does not exist: * * dodoc: docs/*.pdf does not exist
Created attachment 289261 [details] emerge log
Created attachment 289263 [details] emerge -pqv
This ebuild also fails with USE='-doc": Here are the _different_ relevant messages: >>> Install firebird-2.5.0.26074.0-r2 into /var/tmp/portage/dev-db/firebird-2.5.0.26074.0-r2/image/ category dev-db * Renaming isql -> fbsql !!! dosbin: bin/fb_inet_server does not exist * ERROR: dev-db/firebird-2.5.0.26074.0-r2 failed (install phase): * dosbin failed * * If you need support, post the output of 'emerge --info =dev-db/firebird-2.5.0.26074.0-r2', * the complete build log and the output of 'emerge -pqv =dev-db/firebird-2.5.0.26074.0-r2'. * The complete build log is located at '/var/log/portage/emerge/dev-db:firebird-2.5.0.26074.0-r2:20111008-204057.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-db/firebird-2.5.0.26074.0-r2/temp/environment'. * S: '/var/tmp/portage/dev-db/firebird-2.5.0.26074.0-r2/work/Firebird-2.5.0.26074-0' * QA Notice: file does not exist: * * dosbin: bin/fb_inet_server does not exist
Created attachment 289505 [details, diff] doc xinetd use flag patch The attached patch fixes both issues. It should not require a revision bump since it the issues prevents merge.
Created attachment 289507 [details, diff] doc xinetd use flag patch Modified attached patch fixes both issues. It should not require a revision bump since it the issues prevents merge. Stupid pdfs in mixed case...
This bug is obsolete once the 2.5.1 ebuild in bug 392469 has been added to tree, basically can be closed now as won't resolve. Though has been resolved for some time, the attached patch was never applied or ebuild in tree bumped, but I did fix ASAP after bug report.
(In reply to comment #6) > This bug is obsolete once the 2.5.1 ebuild in bug 392469 has been added to > tree, basically can be closed now as won't resolve. Though has been resolved > for some time, the attached patch was never applied or ebuild in tree bumped, > but I did fix ASAP after bug report. William, thank you for your work. Since you aren't a committer to the tree, do you follow some sort of procedure to get your patches applied? Perhaps the process got bogged down along the way. I hope that this incident will lead to improvement in applying patches like yours. Regards, Howard
(In reply to comment #7) > > William, thank you for your work. No problem > Since you aren't a committer to the tree, I was, and had made several attempts over the last few years to become a dev again and be able to directly commit this and other stuff. > do > you follow some sort of procedure to get your patches applied? Perhaps the > process got bogged down along the way. I hope that this incident will lead to > improvement in applying patches like yours. Not really, in the past I just looked for who was touching the package given no maintainer since my departure. I would try to go directly to them rather than filing a bug, but that's not always an option. For this package that was Patrick some time back, and I was mostly proxying stuff via him ever since. Not sure what happened I poked him a few times on IRC about this bug shortly after filing it and within the following days. But involving multiple people in that process is hardly ideal and is fraught with problems, and many things can prevent even a simple patch/commit or otherwise. Patrick has many things on his plate, like most gentoo devs. I guess I could look to go through the proxy committer project/team. Though really ideally I get back on board and commit this stuff myself. But things have been this way for years, really don't expect them to change unfortunately :)
2.5.0 is gone, try 2.5.1
