From: Dominick Grift <domg472@gmail.com>
To: KaiGai Kohei <kaigai@ak.jp.nec.com>
Cc: KaiGai Kohei <kaigai@kaigai.gr.jp>,
Daniel J Walsh <dwalsh@redhat.com>,
selinux@tycho.nsa.gov
Subject: Re: sepostgresql.pp conflicts on F9 (Re: How to find SELinux policy type?)
Date: Tue, 30 Sep 2008 09:24:07 +0200 [thread overview]
Message-ID: <1222759447.29878.3.camel@sulphur.notebook.internal> (raw)
In-Reply-To: <48E1A8BF.6060107@ak.jp.nec.com>
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
On Tue, 2008-09-30 at 13:19 +0900, KaiGai Kohei wrote:
> Dominick,
>
> Show the package:
> http://koji.fedoraproject.org/koji/buildinfo?buildID=64748
>
> It will be able to help your matter.
hello
sh-3.2# rpm -Uvh sepostgresql-8.3.4-2.1067.fc9.x86_64.rpm
error: Failed dependencies:
postgresql-server = 8.3.4 is needed by
sepostgresql-8.3.4-2.1067.fc9.x86_64
sh-3.2# rpm -qa | grep postgresql-server
postgresql-server-8.3.3-2.fc9.x86_64
sepostgresql-8.3.3-2.869.fc9.x86_64 from installed has depsolving
problems
--> Missing Dependency: postgresql-server = 8.3.3 is needed by package
sepostgresql-8.3.3-2.869.fc9.x86_64 (installed)
Error: Missing Dependency: postgresql-server = 8.3.3 is needed by
package sepostgresql-8.3.3-2.869.fc9.x86_64 (installed)
sh-3.2# cd selinux-policy-3.5.6-2.fc10.src
sh-3.2# grep -i require selinux-policy.spec
BuildRequires: python gawk checkpolicy >= %{CHECKPOLICYVER} m4
policycoreutils >= %{POLICYCOREUTILSVER}
Requires(pre): policycoreutils >= %{POLICYCOREUTILSVER} libsemanage >=
2.0.14-3
Requires: checkpolicy >= %{CHECKPOLICYVER} m4
Requires(pre): policycoreutils >= %{POLICYCOREUTILSVER}
Requires(pre): coreutils
Requires(pre): selinux-policy = %{version}-%{release}
Requires(pre): policycoreutils >= %{POLICYCOREUTILSVER}
Requires(pre): coreutils
Requires(pre): selinux-policy = %{version}-%{release}
Requires: policycoreutils-newrole >= %{POLICYCOREUTILSVER} setransd
Requires(pre): policycoreutils >= %{POLICYCOREUTILSVER}
Requires(pre): coreutils
Requires(pre): selinux-policy = %{version}-%{release}
I hope this helps.
Thanks
--
Dominick Grift <domg472@gmail.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-09-30 7:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 23:12 How to find SELinux policy type? James Morris
2008-09-23 23:32 ` Mike Sweetser - Adhost
2008-09-24 0:21 ` Paul Howarth
2008-09-24 0:41 ` KaiGai Kohei
2008-09-24 1:01 ` James Morris
2008-09-24 11:27 ` Daniel J Walsh
2008-09-24 0:18 ` KaiGai Kohei
2008-09-24 13:01 ` Daniel J Walsh
2008-09-24 13:30 ` Justin P. Mattock
2008-09-26 3:34 ` Valdis.Kletnieks
2008-09-26 3:50 ` KaiGai Kohei
2008-09-26 9:38 ` Dominick Grift
2008-09-26 10:25 ` KaiGai Kohei
2008-09-26 10:41 ` Dominick Grift
2008-09-26 13:32 ` KaiGai Kohei
2008-09-27 15:54 ` KaiGai Kohei
2008-09-30 4:19 ` sepostgresql.pp conflicts on F9 (Re: How to find SELinux policy type?) KaiGai Kohei
2008-09-30 7:24 ` Dominick Grift [this message]
2008-09-30 7:52 ` KaiGai Kohei
2008-09-30 8:06 ` Paul Howarth
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=1222759447.29878.3.camel@sulphur.notebook.internal \
--to=domg472@gmail.com \
--cc=dwalsh@redhat.com \
--cc=kaigai@ak.jp.nec.com \
--cc=kaigai@kaigai.gr.jp \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.