** Changed in: sssd (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058576
Title:
FTBFS: armhf: build-time test failures
To manage notifications about thi
** Merge proposal unlinked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/sssd/+git/sssd/+merge/468108
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058576
Title:
FTBFS: armhf: build-time
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/sssd/+git/sssd/+merge/468108
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058576
Title:
FTBFS: armhf: build-time t
Uploaded to noble, it's built in proposed \o/
** Changed in: sssd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058576
Title:
FTBFS: armhf: bui
** Changed in: sssd (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058576
Title:
FTBFS: armhf: build-time test failures
To manage notifications about this bug
This bug was fixed in the package sssd - 2.9.4-1.1ubuntu5
---
sssd (2.9.4-1.1ubuntu5) noble; urgency=medium
* Fix build-time tests (LP: #2058576):
- d/p/fix-format-string-time64.patch: fix format string used for a
timestamp filter string. Thanks to Sergio Durigan Junior
** Bug watch added: Debian Bug tracker #1068063
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068063
** Also affects: sssd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068063
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/sssd/+git/sssd/+merge/463721
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058576
Title:
FTBFS: armhf: build-time
On Wednesday, April 03 2024, Andreas Hasenack wrote:
> It is enabled:
>
> Types: deb
> URIs: http://ports.ubuntu.com/ubuntu-ports
> Suites: noble noble-updates noble-backports noble-proposed
> Components: main universe restricted multiverse
> Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.g
It is enabled:
Types: deb
URIs: http://ports.ubuntu.com/ubuntu-ports
Suites: noble noble-updates noble-backports noble-proposed
Components: main universe restricted multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
Or is there some other trick specific to the state noble is in
On Wednesday, April 03 2024, Andreas Hasenack wrote:
> This is very hard to troubleshoot at the moment, because I just can't
> get the build-dependencies installed, either with noble or noble-
> proposed:
I think you need to enable noble-updates.
--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0
This is very hard to troubleshoot at the moment, because I just can't
get the build-dependencies installed, either with noble or noble-
proposed:
noble:
$ sudo apt-get build-dep .
Note, using directory '.' to get the build dependencies
Reading package lists... Done
Building dependency tree... Do
** Changed in: sssd (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: sssd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Tags added: server-todo
** Changed in: sssd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058576
Title:
FTBFS: armhf: build-time test failures
To manage
removing 'faketime' from dependencies solves failures above.
Remaining failures:
[ FAILED ] tests: 3 test(s), listed below:
[ FAILED ] test_user_by_recent_filter_valid
[ FAILED ] test_group_by_recent_filter_valid
[ FAILED ] test_users_by_filter_filter_old
3 FAILED TEST(S)
FAIL responder_
In an armhf noble container I can reproduce the build failure. But when
I try to run the tests manually, they pass:
# SSS_TEST_DIR=. ABS_TOP_SRCDIR=. LDB_MODULES_PATH=./ldb_mod_test_dir/
./test-driver --test-name foo --log-file pam-srv-tests.log --trs-file
pam-srv-tests.trs ./pam-srv-tests ht
16 matches
Mail list logo
