This bug was fixed in the package sssd - 1.8.6-0ubuntu0.2
---
sssd (1.8.6-0ubuntu0.2) precise-proposed; urgency=low
* rules: Really install the new pam-auth-update file for password
changes. (LP: #1086272)
* rules: Pass --datadir, so the path in autogenerated python files is
This bug was fixed in the package sssd - 1.9.1-0ubuntu1.3
---
sssd (1.9.1-0ubuntu1.3) quantal-proposed; urgency=low
* rules: Really install the new pam-auth-update file for password
changes. (LP: #1086272)
* rules: Pass --datadir, so the path in autogenerated python files is
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
This bug was fixed in the package sssd - 1.9.4-0ubuntu2
---
sssd (1.9.4-0ubuntu2) raring; urgency=low
* Merge from unreleased debian git
- Fix FTBFS on arm by raising test timeout to 30s
- Introduces postinst/postrm to setup nsswitch.conf when installing
libsss-sudo
-
Everything is fine now in Quantal, and Raring. Precise was never
affected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079938
Hello Xiao-Long, or anyone else affected,
Accepted sssd into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/sssd/1.8.6-0ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Awesome, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079938
Title:
${prefix} present in Python files breaking sssd
To manage notifications about this bug go to:
https://bugs.launchpad.ne
I'll just pass --datadir, it's easiest that way..
** Changed in: sssd (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: sssd (Ubuntu Precise)
Status: Fix Committed => In Progress
** Changed in: sssd (Ubuntu Quantal)
Status: Fix Committed => In Progress
--
You r
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079938
Title:
${prefix} present in Python files breaking sssd
To manage notifica
** No longer affects: debhelper (Ubuntu)
** No longer affects: debhelper (Ubuntu Quantal)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079938
Title:
${prefix} present in Python files breaking sss
There should be no need to pass --datadir, it's just that __init__.py
should be created in a Makefile and not by autoconf, which is doing what
is expected of it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Hi Timo, I've been searching the automake docs all day and I think I've
found something relevant.
According to https://www.gnu.org/software/automake/manual/html_node
/Standard-Directory-Variables.html if "--datadir=..." is not passed
(like in Ubuntu), then "@datadir@" is replaced with "${prefix}/s
Actually, I think it's sssd that's at fault for not being able to parse
debhelper's ./configure arguments, since pretty much every other project
using ./configure can. I'll see if I can come up with a patch for the
issue.
--
You received this bug notification because you are a member of Ubuntu
Bu
So it's a debhelper bug? In any case, the cdbs cruft has been removed,
so the sru is still validated even though it didn't fix your case.
** Tags removed: verification-failed
** Tags added: verification-done
** Also affects: debhelper (Ubuntu)
Importance: Undecided
Status: New
** No lo
Okay, I've found the real cause of the issue. It's due to some
differences between debhelper and rpmbuild:
**On Ubuntu:
Take a look at /usr/share/perl5/Debian/Debhelper/Buildsystem/autoconf.pm
(Screenshot: http://i.imgur.com/WozcJoe.png )
Notice how debhelper passes '\${prefix}' directly to ./co
Hello Adam,
The sssd in 12.04 was never affected since it's on the 1.8.x series.
Both 1.9.1-0ubuntu1.2 in Quantal and 1.9.3-0ubuntu2 in Raring still have
'${prefix}' in /usr/lib/python2.7/dist-packages/SSSDConfig/__init__.py
** Tags removed: verification-needed
** Tags added: verification-failed
Hello Xiao-Long, or anyone else affected,
Accepted sssd into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/sssd/1.8.6-0ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Here is the exact error message: http://paste.ubuntu.com/1411155/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079938
Title:
${prefix} present in Python files breaking sssd
To manage notification
The problem is that "${prefix}" taken litterally by the python file.
"ipa-client-install" with crash when configuring sssd because the path
cannot be found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Xiao-Long: could you explain what issues the wrong path in the python
file causes? Freeipa-client has installed fine for me.
** Description changed:
+ [Impact]
+ packaging bug that causes incorrect paths in a python file
+
+ [Test case]
+ look at /usr/lib/python2.7/dist-packages/SSSDConfig/__ini
** Also affects: sssd (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: sssd (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: sssd (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: sssd (Ubuntu Precise)
Status: New =>
This bug was fixed in the package sssd - 1.9.2-0ubuntu4
---
sssd (1.9.2-0ubuntu4) raring; urgency=low
* Add -lpthread to sss_ssh_knownhostsproxy LDFLAGS (FTBFS).
-- Timo AaltonenSat, 01 Dec 2012 08:58:44 +0200
** Changed in: sssd (Ubuntu)
Status: Triaged => Fix Released
Hmm, guess you're right then. I've also just gone with the default
libexecdir which with compat 9 is under the multiarch dir.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079938
Title:
${prefix} p
I didn't know you had it done already...oops :)
As for the third change, I assumed that the .../krb5/ was the correct
path, since that's what the krb5 packaging creates:
https://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/raring/krb5/raring/view/head:/debian/libkrb5-3.dirs.in
--
You received t
thanks for the patch, I had it covered already though :) (local,
uncommitted git)
And I don't understand the 3rd change? I see two packages using the
current ../plugin/libkrb5 path, but none using the one you suggest?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The attachment "lp1079938.patch" of this bug report has been identified
as being a patch. The ubuntu-reviewers team has been subscribed to the
bug report so that they can review the patch. In the event that this is
in fact not a patch you can resolve this situation by removing the tag
'patch' fro
I've created a patch that fixes this issue. It:
1. Removes leftover cdbs bits
2. Bumps compat version to 9, so "--libdir=/usr/lib/$(DEB_HOST_MULTIARCH)" is
not needed anymore
3. Fixes kerberos plugins path. Ubuntu uses /usr/lib/.../krb5/plugins/krb5/
instead of /usr/lib/.../krb5/plugins/libkrb5/
thanks, looks like a leftover of the cdbs era.
** Changed in: sssd (Ubuntu)
Status: New => Triaged
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I've found the cause of the issue. The offending line is in
debian/rules: http://paste.ubuntu.com/1363982/
which causes this: http://paste.ubuntu.com/1363979/
I don't see ${prefix} or ${libdir} defined anywhere, which is probably
why this issue happens.
--
You received this bug notification bec
Ubuntu 13.04's package is also affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079938
Title:
${prefix} present in Python files breaking sssd
To manage notifications about this bug go to:
h
30 matches
Mail list logo
