Change of default database file format to SQL

Bug #1747411 reported by Christian Ehrhardt 
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
certmonger (Ubuntu)
Fix Released
Undecided
Unassigned
corosync (Ubuntu)
Fix Released
Undecided
Unassigned
dogtag-pki (Ubuntu)
Fix Released
Undecided
Timo Aaltonen
freeipa (Ubuntu)
Fix Released
Undecided
Unassigned
libapache2-mod-nss (Ubuntu)
Won't Fix
Undecided
Unassigned
nss (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

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 revert can be dropped.
Therefore we list all known-to-be-affected packages and once all are resolved this can be dropped.

[1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql
[2]: https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3

Tags: server-next

Related branches

summary: - Change of default database file format
+ Change of default database file format to SQL
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

I'll make sure the freeipa related packages are updated for bionic

Changed in dogtag-pki (Ubuntu):
assignee: nobody → Timo Aaltonen (tjaalton)
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package certmonger - 0.79.5-3

---------------
certmonger (0.79.5-3) experimental; urgency=medium

  * Merge changes from upstream git to support sqlite nssdb's.
    (LP: #1747411)
  * force-utf-8.diff: Dropped, upstream.
  * fix-apache-path.diff: Use proper path to apache nssdb.

 -- Timo Aaltonen <email address hidden> Fri, 30 Mar 2018 09:57:57 +0300

Changed in certmonger (Ubuntu):
status: New → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

dogtag-pki 10.6.0~beta2 landed in bionic

Changed in dogtag-pki (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

freeipa in bionic-proposed doesn't use nss db's anymore

Changed in freeipa (Ubuntu):
status: New → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

and freeipa doesn't use libapache2-mod-nss either anymore

Changed in libapache2-mod-nss (Ubuntu):
status: New → Won't Fix
tags: added: server-next
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

For corosync the affected components are corosync-qnetd.

I checked and without adaption on install they would be fine as they initialize a new DB and nowhere does anyone specify the type. But as with some other tools on an upgrade we have to assume that the old DBM format will be tried to be read as SQL and then fail.

Worth to notice is that Fedora who started all of this in [1] in their NSS build still uses DBM as default :-)

corosync 2.4.4-1 of 20th of April made corosync compatible with the nss change.
They prefix all calls with dbm to stay compat until the upgrade is handled by upstream.
So a merge of this or latter version will address this for corosync.
Afterwards nss can be merged dropping the change of the default.

[1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Corosync is actually a sync for Cosmic, with all Delta dropped:

  * Merge with Debian unstable (LP: #1747411). Remaining changes:
    </none>
  * Dropped Changes:
    - Properly restart corosync and pacemaker together (LP: #1740892)
      d/rules: pass --restart-after-upgrade to dh_installinit.
      (this is default in compat >=10, and the package is 11)
    - d/control: indicate this version breaks all older pacemaker, to
      force an upgrade of pacemaker. (Upgrades have gone through Bionic,
      so we can drop this now)
    - d/corosync.postinst: if flagged to do so by pacemaker, start
      pacemaker on upgrade. (Can be dropped after Bionic)
    - New upstream release 2.4.3 (now in Debian)
    - Drop upstreamed patches and refresh others. (now in Debian)

To get a second opinion on that I opened: https://code.launchpad.net/~paelzer/ubuntu/+source/corosync/+git/corosync/+merge/345184

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nss - 2:3.36.1-1ubuntu1

---------------
nss (2:3.36.1-1ubuntu1) cosmic; urgency=medium

  * Merge with Debian unstable. Remaining changes:
    - d/libnss3.links: make freebl3 available as library (LP 1744328)
      - d/control: add dh-exec to Build-Depends
      - d/rules: make mkdir tolerate debian/tmp existing (due to dh-exec)
    - d/rules: when building with -O3 on ppc64el this FTBFS, build with
      -Wno-error=maybe-uninitialized to avoid that
  * Dropped changes:
    - revert switching to SQL default format (LP: 1746947) Dropping this
      adresses (LP: #1747411) and effectively means we now switch to the new
      default format after we ensured all depending packages are ready.
  * Added changes:
    - d/rules: extended the FTBFS to -O3 on ppc64el to only apply on ppc64el

nss (2:3.36.1-1) unstable; urgency=medium

  * New upstream release.
  * debian/control: Update Maintainer and Vcs fields, moving off alioth.

nss (2:3.36-1) unstable; urgency=medium

  * New upstream release. Closes: #894981.

 -- Christian Ehrhardt <email address hidden> Mon, 07 May 2018 17:08:46 +0200

Changed in nss (Ubuntu):
status: New → Fix Released
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

nss and corosync being the last on this are in Cosmic now.

Changed in corosync (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.