All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Laurent Bigonville <bigon@debian.org>
Cc: SELinux@tycho.nsa.gov
Subject: Re: setools FTBFS in python module
Date: Fri, 29 Jun 2012 15:41:19 -0400	[thread overview]
Message-ID: <4FEE04DF.2020502@redhat.com> (raw)
In-Reply-To: <20120628125629.0fead796@eldamar.bigon.be>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/28/2012 06:56 AM, Laurent Bigonville wrote:
> Hi,
> 
> setools is currently FTBFS in debian due to swig 2.0.7 with the following
> error:
> 
>> ../../../libqpol/include/qpol/terule_query.h:118:13: note: previous 
>> declaration of 'qpol_terule_get_rule_type' was here qpol_wrap.c: In 
>> function 'qpol_terule_get_rule_type': qpol_wrap.c:4888:3: warning: 
>> passing argument 1 of 'qpol_terule_get_rule_type' from incompatible 
>> pointer type [enabled by default] qpol_wrap.c:4885:16: note: expected 
>> 'struct qpol_terule *' but argument is of type 'struct qpol_policy_t *'
>> qpol_wrap.c:4888:3: warning: passing argument 2 of 
>> 'qpol_terule_get_rule_type' from incompatible pointer type [enabled by
>> default] qpol_wrap.c:4885:16: note: expected 'struct qpol_policy_t *' but
>> argument is of type 'struct qpol_terule *' qpol_wrap.c:4888:3: error: too
>> many arguments to function 'qpol_terule_get_rule_type' 
>> qpol_wrap.c:4885:16: note: declared here qpol_wrap.c: At top level: 
>> qpol_wrap.c:4895:31: error: conflicting types for 
>> 'qpol_terule_get_source_type' In file included from
>> ../../../libqpol/include/qpol/policy.h:60:0, from
>> ../../../libqpol/include/../include/qpol/avrule_query.h:34, from 
>> qpol_wrap.c:3010:
> 
> OpenSuse is applying a patch[1] that is fixing the issue. Do you think that
> this patch could be merged (as well as the other swig patch that fix swig
> 2.0 detection?).
> 
> Also what is the status of setools? It seems that all the distribution 
> (RedHat, OpenSuse, Debian,...) are applying a bunch of other patches. 
> Shouldn't all these be merged? Or is setools definitely dead?
> 
> Cheers
> 
> Laurent Bigonville
> 
> [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672040 [1] 
> https://build.opensuse.org/package/view_file?file=setools-swig-2.0.7.patch&package=setools&project=security%3ASELinux&rev=fa0565dafcc84c3c18514867f92270a1
>
>  -- This message was distributed to subscribers of the selinux mailing
> list. If you no longer wish to subscribe, send mail to
> majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without quotes
> as the message.
> 
> 
I guess we need someone to take over upstream for this.  We are actively
developing it but upstream has not worked on it in a long time and has ignored
patches.  Eric Paris @ Red Hat has stepped up to take over upstream
responsibilities on the SELinux user space, and I guess some one needs to
request that setools be opened up the community.  I would gladly submit the
Fedora patches to a responsive upstream.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/uBN8ACgkQrlYvE4MpobOC9ACgtkFq9GZvPru39knmtahivDTv
k04AoIQWaveZUhcMqjcIQH7DyGwqRJ7V
=v6/j
-----END PGP SIGNATURE-----

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

      reply	other threads:[~2012-06-29 19:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 10:56 setools FTBFS in python module Laurent Bigonville
2012-06-29 19:41 ` Daniel J Walsh [this message]

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=4FEE04DF.2020502@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=bigon@debian.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 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.