vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 4843ded578710ac037848e68241846c63e3f9b1e
Merge: 8913946 b628e5e
Author: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date: Sun Sep 5 14:02:29 2021 +0000
Merge branch 'salsa-ci' into 'master'
enable salsa-ci with branch2repo
See merge request installer-team/cdebconf!8
commit 8913946ccdbcf210ddabfe8a6c03d212dae12c0e
Merge: 8b3fe4e c43c578
Author: Julien Cristau <jcristau@debian.org>
Date: Mon Aug 23 11:32:44 2021 +0000
Merge branch 'g-malloc-cannot-fail' into 'master'
gtk: Remove "check NULL" comments
See merge request installer-team/cdebconf!10
commit c43c57892b8e705117303501ff395209b7dacc55
Author: Simon McVittie <smcv@debian.org>
Date: Fri May 21 10:46:15 2021 +0100
gtk: Remove "check NULL" comments
All of these are GLib/GTK functions that either succeed or crash out with
a fatal error, but cannot return NULL. The version of g_malloc0() that can
in theory return NULL (although usually not on Linux) is g_try_malloc0(),
and GTK widget creation never survives out-of-memory conditions.
If cdebconf genuinely runs out of memory, there isn't really going to
be anything we can do about it (popping up a dialog or writing to the
syslog is certainly going to need memory!) so the realistic response
is to just crash. GLib calls g_error() on out-of-memory, which has the
least-bad feasible handling for OOM: it will do its best to write a
message to stderr, and then abort() to leave a core dump.
Signed-off-by: Simon McVittie <smcv@debian.org>
commit b628e5eaa6faddb5749df006008f6a60b02e3842
Author: Philip Hands <phil@hands.com>
Date: Sun May 16 18:51:17 2021 +0200
enable salsa-ci with branch2repo
![[bug history graph]](https://qa.debian.org/data/bts/graphs/c/cdebconf.png){kind=link}