From: "Michael Palimaka" <kensington@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/apparmor/
Date: Tue, 31 Oct 2017 12:22:36 +0000 (UTC) [thread overview]
Message-ID: <1509452542.01dab293acf4c1c779814b9a0b098a207b306ba1.kensington@gentoo> (raw)
commit: 01dab293acf4c1c779814b9a0b098a207b306ba1
Author: Michael Palimaka <kensington <AT> gentoo <DOT> org>
AuthorDate: Tue Oct 31 12:21:59 2017 +0000
Commit: Michael Palimaka <kensington <AT> gentoo <DOT> org>
CommitDate: Tue Oct 31 12:22:22 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=01dab293
sys-apps/apparmor: revision bump resolves automagic distro detection
The automagic distro detection caused different files to be installed, for
example if /usr/bin/rpm was present.
Closes: https://bugs.gentoo.org/635908
Package-Manager: Portage-2.3.8, Repoman-2.3.4
.../apparmor/{apparmor-2.11.1.ebuild => apparmor-2.11.1-r1.ebuild} | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/sys-apps/apparmor/apparmor-2.11.1.ebuild b/sys-apps/apparmor/apparmor-2.11.1-r1.ebuild
similarity index 93%
rename from sys-apps/apparmor/apparmor-2.11.1.ebuild
rename to sys-apps/apparmor/apparmor-2.11.1-r1.ebuild
index ce5c3943dfd..eb164b45cf3 100644
--- a/sys-apps/apparmor/apparmor-2.11.1.ebuild
+++ b/sys-apps/apparmor/apparmor-2.11.1-r1.ebuild
@@ -49,12 +49,11 @@ src_test() {
}
src_install() {
- emake DESTDIR="${D}" USE_SYSTEM=1 install
+ emake DESTDIR="${D}" DISTRO="unknown" USE_SYSTEM=1 install
dodir /etc/apparmor.d/disable
newinitd "${FILESDIR}"/${PN}-init ${PN}
- rm "${D}"/etc/init.d/boot.apparmor || die
use doc && dodoc techdoc.pdf
}
next reply other threads:[~2017-10-31 12:22 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 12:22 Michael Palimaka [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-03 8:06 [gentoo-commits] repo/gentoo:master commit in: sys-apps/apparmor/ Sam James
2024-03-15 2:45 Sam James
2024-01-08 12:28 Sam James
2024-01-03 22:30 Sam James
2023-11-05 8:46 Arthur Zamarin
2023-11-05 8:46 Arthur Zamarin
2023-07-15 15:07 Arthur Zamarin
2023-06-26 19:50 Sam James
2023-06-01 21:07 Sam James
2023-06-01 16:53 Arthur Zamarin
2023-06-01 5:20 Sam James
2023-06-01 5:20 Sam James
2023-06-01 5:20 Sam James
2022-12-20 20:54 Arthur Zamarin
2022-12-20 20:39 Sam James
2022-10-28 7:01 Sam James
2022-10-20 23:34 Sam James
2022-10-18 16:32 Jakov Smolić
2022-09-02 4:40 Arthur Zamarin
2022-06-24 8:41 Michael Palimaka
2022-06-17 6:54 Agostino Sarubbo
2022-06-17 1:10 Sam James
2022-03-05 0:05 Sam James
2021-11-12 2:09 Sam James
2021-06-04 7:22 Michael Palimaka
2021-02-24 16:27 Sam James
2020-12-08 7:04 Michael Palimaka
2020-10-11 4:16 Michael Palimaka
2020-05-07 13:41 Michael Palimaka
2020-03-19 8:20 Michael Palimaka
2019-08-18 8:13 Michael Palimaka
2019-08-04 12:27 Michael Palimaka
2019-03-28 13:17 Michael Palimaka
2019-03-25 11:38 Michael Palimaka
2019-03-07 11:27 Michael Palimaka
2018-11-09 8:57 Michael Palimaka
2018-01-01 2:59 Michael Palimaka
2018-01-01 2:59 Michael Palimaka
2017-08-05 7:59 Michael Palimaka
2017-06-03 12:53 Michael Palimaka
2017-01-11 16:24 Michael Palimaka
2016-07-27 15:50 Michael Palimaka
2016-05-25 17:50 Michael Palimaka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1509452542.01dab293acf4c1c779814b9a0b098a207b306ba1.kensington@gentoo \
--to=kensington@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox