** Also affects: nss (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nss (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1746947
Title:
For a better overview and to make a decision (as a +really version always sucks
to some extend) I did some tests:
- built nss 3.34 with the freebl3 change in ppa [1] as
2:3.35-2ubuntu1+really3.34-1ubuntu2
- set up some containers to test
- ran the sequence of installs/commands that freeipa tests
I was discussing this with Timo and he correctly pointed out that reverting [1]
might be enough.
This would allow to get all fixes of 3.35, but at the same time not run into
this bug here all over the place.
Building with that for some test runs.
[1]: https://github.com/nss-
dev/nss/commit/33b1
Built with said change - and now testing against the nss in the ppa (should all
work):
- install 4.4 (ppa) -> OK
- install 4.6 (proposed + ppa) -> OK
- old python call against 4.4 (ppa) -> OK
- new python call against 4.6 (proposed + ppa) -> OK
I dupped Corosync on here, so lets verify it fixes t
Public bug reported:
nss in version 3.35 in upstream changed [2] the default file format [1] (if no
explicit one is specified).
For now we reverted that change in bug 1746947 until all packages depending on
it are ready to work with that correctly.
This bug here is about to track when the rever
This bug was fixed in the package nss - 2:3.35-2ubuntu2
---
nss (2:3.35-2ubuntu2) bionic; urgency=medium
* d/p/lp1746947-revert-switch-default-to-sql.patch: the switch of the
default is still causing too much issues in consumers of nss.
So until resolved revert the switched
6 matches
Mail list logo
