Portage reports a couple of QA issues when emerging app-crypt/mit-krb5-1.16.1. First QA issue: * Running eautoreconf in '/var/tmp/portage/app-crypt/mit-krb5-1.16.1/work/krb5-1.16.1/src' ... * This package has a configure.in file which has long been deprecated. Please * update it to use configure.ac instead as newer versions of autotools will die * when it finds this file. See https://bugs.gentoo.org/426262 for details. Second QA issue: * One or more empty directories installed to /var: * * /var/lib/run/krb5kdc * * If those directories need to be preserved, please make sure to create * or mark them for keeping using 'keepdir'. Future versions of Portage * will strip empty directories from installation image.
Created attachment 531036 [details] build.log.xz
Created attachment 531038 [details] emerge --info app-crypt/mit-krb5
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b55eb5d74c825500bbe759dce1a46d324373e59c commit b55eb5d74c825500bbe759dce1a46d324373e59c Author: Eray Aslan <eras@gentoo.org> AuthorDate: 2018-12-15 14:52:42 +0000 Commit: Eray Aslan <eras@gentoo.org> CommitDate: 2018-12-15 14:52:42 +0000 app-crypt/mit-krb5: bump to 1.16.2 Closes: https://bugs.gentoo.org/671654 Closes: https://bugs.gentoo.org/669018 Closes: https://bugs.gentoo.org/655582 Package-Manager: Portage-2.3.52, Repoman-2.3.12 Signed-off-by: Eray Aslan <eras@gentoo.org> app-crypt/mit-krb5/Manifest | 1 + app-crypt/mit-krb5/mit-krb5-1.16.2.ebuild | 161 ++++++++++++++++++++++++++++++ 2 files changed, 162 insertions(+)
With app-crypt/mit-krb5-1.16.3 the "empty directories" QA issue is now fixed, but I still get the "configure.in" QA issue from portage.
(In reply to Francesco Turco from comment #4) > With app-crypt/mit-krb5-1.16.3 the "empty directories" QA issue is now > fixed, but I still get the "configure.in" QA issue from portage. This is a separate issue. Please do not repurpose bugs.
