First Mantic Minotaur test rebuild

[Andreas Hasenack]

Hi,

On Wed, Sep 6, 2023 at 6:19 AM Graham Inggs <ginggs at ubuntu.com> wrote:
>
> The first test rebuild of Mantic Minotaur was started on August 30,
> 2023 for all architectures, all components. The rebuild is finished
> for the main component on all architectures except riscv64, and still
> running for universe and multiverse.
>
> Results (please also look at the superseded builds) can be found at:
>
> https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html

Many of these failures are caused by glibc 2.38 now having strlcat and
friends, and this causes a dpkg-gensymbols error like this (example
from src:libqb):

dpkg-gensymbols: error: some symbols or patterns disappeared in the
symbols file: see diff output below
dpkg-gensymbols: warning: debian/libqb100/DEBIAN/symbols doesn't match
completely debian/libqb100.symbols
--- debian/libqb100.symbols (libqb100_2.0.8-1_amd64)
+++ dpkg-gensymbolsTJnRGb 2023-09-04 11:09:48.720929506 +0000
@@ -244,6 +244,6 @@
  qb_vsnprintf_deserialize at Base 2.0.1
  qb_vsnprintf_serialize at Base 2.0.1
  remove_tempdir at Base 2.0.1
- strlcat at Base 2.0.1
- strlcpy at Base 2.0.1
+#MISSING: 2.0.8-1# strlcat at Base 2.0.1
+#MISSING: 2.0.8-1# strlcpy at Base 2.0.1
  use_filesystem_sockets at Base 2.0.1

Do we have a pattern to fix these, or a checklist? Mark them as
optional I suppose, but how can we be sure reverse dependencies aren't
relying on these strl* symbols, do we rebuild them all? It may sound
far fetched, but I suppose some application could have been relying on
strlcat from bin:libqb100 (even though it's not declared in
libqb-dev's /usr/include/qb/* anywhere).

I saw the fix[1] to krb5's build issue, but there the symbol was
internal (but still exposed?). Is that what we need to apply,
including the replacing of #MINVER# in the symbols file to a strict
"equals", which is what I assume changes the shlibs:Depends from a ">=
MINVER" to "= $ver", and thus accounts for the ordering of upgrades?
And still a breaks for the other binary packages produced by the same
source?


1. https://git.launchpad.net/ubuntu/+source/krb5/commit/?id=a518233aab27fb7e06b8db2a46e5a2a0e4845b33






>
> Additional build failures for packages in mantic-proposed (not yet in
> mantic) can be found at:
>
> http://qa.ubuntuwire.com/ftbfs/
>
> Please help with fixing the build failures.
>
> Graham
>
> --
> ubuntu-devel mailing list
> ubuntu-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel