From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e1c6cd05e3a1f08b28f8d0eea4736c829f12b06f
Date: Mon, 02 Mar 2020 08:16:16 +0000 [thread overview]
Message-ID: <48WCds3Hqnz2xyB@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via e1c6cd05e3a1f08b28f8d0eea4736c829f12b06f (commit)
from c8b574c3078b35c272960ac0b26de6dded845467 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit e1c6cd05e3a1f08b28f8d0eea4736c829f12b06f
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Mon Mar 2 08:15:00 2020 +0000
udev: build after kmod
eudev depends on kmod to install all needed rules
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
make.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/make.sh b/make.sh
index b434e7188..984fc95b2 100755
--- a/make.sh
+++ b/make.sh
@@ -1120,7 +1120,6 @@ buildbase() {
lfsmake2 tar
lfsmake2 texinfo
lfsmake2 util-linux
- lfsmake2 udev
lfsmake2 vim
}
@@ -1133,6 +1132,7 @@ buildipfire() {
lfsmake2 openssl
[ "${BUILD_ARCH}" = "i586" ] && lfsmake2 openssl KCFG='-sse2'
lfsmake2 kmod
+ lfsmake2 udev
lfsmake2 popt
lfsmake2 libedit
lfsmake2 libusb
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-03-02 8:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48WCds3Hqnz2xyB@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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