From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 4cf1d18fbb8a7cc118c084e5eb27f19107461830
Date: Sun, 27 May 2012 13:38:10 +0200 [thread overview]
Message-ID: <20120527113810.D08E8200BA@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1472 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 3.x development tree".
The branch, master has been updated
via 4cf1d18fbb8a7cc118c084e5eb27f19107461830 (commit)
from 90202c1fc31dde75eec8307045f4a056e085da15 (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 4cf1d18fbb8a7cc118c084e5eb27f19107461830
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun May 27 13:37:42 2012 +0200
udev: Build cannot require usbutils-devel which does not exist.
-----------------------------------------------------------------------
Summary of changes:
udev/udev.nm | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/udev/udev.nm b/udev/udev.nm
index ee49000..3545756 100644
--- a/udev/udev.nm
+++ b/udev/udev.nm
@@ -5,7 +5,7 @@
name = udev
version = 182
-release = 4
+release = 5
groups = System/Base
url = ftp://ftp.kernel.org/pub/linux/utils/kernel/hotplug/
@@ -38,7 +38,7 @@ build
pciutils
shadow-utils
systemd-units
- usbutils-devel >= 1:005
+ usbutils >= 1:005
end
configure_options += \
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-05-27 11:38 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=20120527113810.D08E8200BA@argus.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