ebuild for gnu icecat Reproducible: Always
Created attachment 542908 [details] icecat ebuild
Created attachment 542910 [details] icecat.desktop
gentoo-default-prefs.js-1 and gentoo-hwaccel-prefs.js-1 come from www-client/firefox-52.6.0.ebuild
Thank you for your contribution. I had a short look on the ebuild. Here a few ideas: * Please test the ebuild with repoman full -x https://wiki.gentoo.org/wiki/Repoman * We always try to use the latest EAPI, please bump to EAPI=7 * Please remove obsolete lines * KEYWORDS need ~ after a version bump run ekeyword ~all YOUREBUILD * please fix the header. (see /usr/portage/skel.ebuild and https://devmanual.gentoo.org/ebuild-writing/eapi/) * We usually sort the KEYWORDS as ekeywords does. This makes comparison between packages easier. Simply run ekeywords on the ebuild to let it sort.
JimmyJazz, Hi, I'd also like to thank you for this contribution. I've been researching Icecat and am interesting in helping (you?) co-maintain it. Novice skills but eager to learn. I'd really like to see it return to ::gentoo. Granted the previous security issues have been resolved upstream. See:https://bugs.gentoo.org/427186 Question: would you be able to provide me with the Manifest, as running 'repoman -x on the ebuild complains for me with the following: RepoMan scours the neighborhood... * Manifest not found for '/usr/local/portage/domhnall-repo/www-client/icecat/icecat-52.6.0.ebuild' !!! A file is not listed in the Manifest: '/usr/local/portage/domhnall-repo/www-client/icecat/icecat-52.6.0.ebuild' ebuild.syntax [fatal] 1 www-client/icecat/icecat-52.6.0.ebuild manifest.bad [fatal] 1 www-client/icecat/Manifest metadata.missing [fatal] 1 www-client/icecat/metadata.xml Please fix these important QA issues first. Gentoo Security Padawan (domhnall)
Created attachment 555000 [details] icecat 60.3.0 ebuild icecat 60.3.0 - for gentoo-hwaccel-prefs.js-1 and gentoo-default-prefs.js-1, see firefox ebuild - unable to activate french locale. - ebuild icecat-60.3.0.ebuild digest clean prepare
*** This bug has been marked as a duplicate of bug 563572 ***