CI: CentOS7 issue
by Fabiano Fidêncio
I've hit the following issue with our CI:
error: unmatched (
error: unmatched (
error: /dev/stdin:111: bad %if condition
Traceback (most recent call last):
File "/root/payload/contrib/ci/rpm-spec-builddeps", line 33, in <module>
spec = rpm.spec(sys.argv[1])
ValueError: can't parse specfile
The full log can be found at:
https://ci.centos.org/job/sssd-CentOS7/1025/console
Is there some easy way to connect to the machine where it happened and
debug it from there?
Best Regards,
--
Fabiano Fidêncio
5 years, 4 months
Ticket #3458 and related PR #275
by Alexey Kamenskiy
Hello dev team,
I've opened the PR #275 (https://github.com/SSSD/sssd/pull/275) some time
ago.
I am wondering if someone could review this PR and provide some feedback?
Namely I would be interested in merging this for the next release as we do
need this functionality (currently I am using installations with this patch
applied and built from source).
Is there any possibility of that happening soon-ish?
--
Best regards,
Alexey Kamenskiy
5 years, 4 months
[sssd PR#50][opened] [RFC] Use GNULIB's compiler warning code
by fidencio
URL: https://github.com/SSSD/sssd/pull/50
Author: fidencio
Title: #50: [RFC] Use GNULIB's compiler warning code
Action: opened
PR body:
"""
This patch series was sent to the sssd-devel and some discussions
already happened there[0]. I've decided to open the PR because there
are some few patches that can be pushed even if we decide to not use
the "many warnings" patches.
Let's keep track of those patches (and discussions related to them) in
the github, in this way we can avoid them to get lost. :-)
[0]: https://lists.fedorahosted.org/archives/list/sssd-devel@lists.fedorahoste...
Best Regards,
Changes:
683f72d (Fabiano Fidêncio, 10 weeks ago)
BUILD: Make use of GNULIB's compiler warning code
As GNULIB has the 'manywarnings' module, which basically turns on every GCC
warning, let's make use of it. We can easily blacklist the warnings we
cannot cope with, but the main goal should be to have enabled every
possible GCC warning.
When new GCC warnings are created the 'manywarnings' file can be refreshed
from upstream GNULIB.
Signed-off-by: Fabiano Fidêncio <fidencio(a)redhat.com>
f59828a (Fabiano Fidêncio, 5 days ago)
NSS: Fix "old-style-definition" warning caught by GCC
Signed-off-by: Fabiano Fidêncio <fidencio(a)redhat.com>
f22aff7 (Fabiano Fidêncio, 5 days ago)
SIFP: Fix a "jump-misses-init" warning caught by GCC
Signed-off-by: Fabiano Fidêncio <fidencio(a)redhat.com>
58609d3 (Fabiano Fidêncio, 5 days ago)
RESOLV: Fix a "-Werror=null-dereference" caught by GCC
Signed-off-by: Fabiano Fidêncio <fidencio(a)redhat.com>
bd1d7fd (Fabiano Fidêncio, 5 days ago)
RESOLV: Simplify reply_weight_rearrange() a little bit
Signed-off-by: Fabiano Fidêncio <fidencio(a)redhat.com>
"""
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/50/head:pr50
git checkout pr50
5 years, 4 months
[sssd PR#348][opened] IPA: Only generate kdcinfo files on clients
by jhrozek
URL: https://github.com/SSSD/sssd/pull/348
Author: jhrozek
Title: #348: IPA: Only generate kdcinfo files on clients
Action: opened
PR body:
"""
In some cases, IPA masters end up having a broken SSSD configuration that
also includes the SRV records. This can cause the kdcinfo files to point to
a different master which uses a different PKINIT certificate which is only
valid for that IPA master. This can result e.g. in webui not working.
This patch prevents the kdcinfo files from being generated on the IPA
masters, but keep generating them on the clients.
Not generating kdcinfo files on masters has no negative performance impact,
because libkrb5 is configured via krb5.conf to point to self anyway.
"""
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/348/head:pr348
git checkout pr348
5 years, 4 months
