Source: libvidstab
Version: 1.1.1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramacher@debian.org

Dear maintainer,

libvidstab FTBFS on !amd64:

dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below
dpkg-gensymbols: warning: debian/libvidstab1.2/DEBIAN/symbols does not match completely debian/libvidstab1.2.symbols
--- debian/libvidstab1.2.symbols (libvidstab1.2_1.1.1-3_arm64)
+++ dpkg-gensymbolsUPNVYY	2026-06-16 17:17:06.810930860 +0000
@@ -31,8 +31,8 @@
  cmp_trans_x@Base 1.1.1
  cmp_trans_y@Base 1.1.1
  compareSubImg_thr@Base 1.1.1
- compareSubImg_thr_sse2@Base 1.1.1
- contrastSubImg1_SSE@Base 1.1.1
+#MISSING: 1.1.1-3# compareSubImg_thr_sse2@Base 1.1.1
+#MISSING: 1.1.1-3# contrastSubImg1_SSE@Base 1.1.1
  contrastSubImg@Base 1.1.1
  contrastSubImgPacked@Base 1.1.1
  contrastSubImgPlanar@Base 1.1.1
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:11: binary-arch] Error 25

See
https://buildd.debian.org/status/fetch.php?pkg=libvidstab&arch=arm64&ver=1.1.1-3&stamp=1781630228&raw=0
for details.

Cheers

Hello there,

The symbols file was newly introduced in the 1.1.1 packaging, but it
doesn't heed the architecture distinction made in debian/rules, i.e. to
only enable HAVE_SSE2 on amd64.

It should suffice to copy the current libvidstab1.2.symbols to
libvidstab1.2.symbols.amd64 and then to strip the two above symbols from
libvidstab1.2.symbols, cf.

| $ COLUMNS=70 man dh_makeshlibs | grep arch
|        debian/package.symbols.arch
|            arch specific names  if  you  need  to  provide  different
|            symbols files for different architectures.

HTH,
Flo - who triggered this via filing #1040695

We believe that the bug you reported is fixed in the latest version of
libvidstab, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1140200@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Keng-Yu Lin <kengyu@debian.org> (supplier of updated libvidstab package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Fri, 19 Jun 2026 03:28:00 +0800
Source: libvidstab
Built-For-Profiles: noudeb
Architecture: source
Version: 1.1.1-4
Distribution: unstable
Urgency: medium
Maintainer: Keng-Yu Lin <kengyu@debian.org>
Changed-By: Keng-Yu Lin <kengyu@debian.org>
Closes: 1140200
Changes:
 libvidstab (1.1.1-4) unstable; urgency=medium
 .
   * Restrict SSE2-specific symbols to amd64 in symbols file
     to fix FTBFS on non-amd64 architectures (Closes: #1140200).
   * Update debian/copyright to update copyright year and email address.
Checksums-Sha1:
 810f41011aa633dcb81a52d4cffebdcae0e6df29 1894 libvidstab_1.1.1-4.dsc
 f1499a0834036998c5b8576ed914c3c3535a0776 5060 libvidstab_1.1.1-4.debian.tar.xz
 71232496b5ab178a4ae3112adcfb93f757a622f3 8693 libvidstab_1.1.1-4_source.buildinfo
Checksums-Sha256:
 3cd4b85662407e3c4769fdf0123c79b66a70eaf30f7572a39b8ac94d75c6bb3e 1894 libvidstab_1.1.1-4.dsc
 0670aee76f438fda11183a12aeb790afe1b62c0e126cde05e876beb5aba502dc 5060 libvidstab_1.1.1-4.debian.tar.xz
 80c2d6ead86e29c66a926e67306a2a1b1a13115dd1e64e81afc94a9d763d9dd9 8693 libvidstab_1.1.1-4_source.buildinfo
Files:
 d2d75e2f06f3ff94cd0bb8b940390102 1894 libs - libvidstab_1.1.1-4.dsc
 132637af68f64417729fa970143032ff 5060 libs - libvidstab_1.1.1-4.debian.tar.xz
 14b0c11cff39aed899a2d1185d46a02f 8693 libs - libvidstab_1.1.1-4_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJGBAEBCgAwFiEEdwtc2/tLhothQ0hFxheGnxR4UE4FAmo1RPMSHGtlbmd5dUBk
ZWJpYW4ub3JnAAoJEMYXhp8UeFBO/kUP/jrueT2cb4s4gyujejDvVgOqTDu57O6j
G7YgCwMrwc4UjvpLnlpALxBSN4zZ+6Gg89dtOYQYwfhPYTGyZy6Y3J8w7+tNvw+Q
gEpJ9cgnfhwk3q11+QQXy7zic6jkBHFlKac6X0GitxlqdiOxWznjd5yTy7Dwv1XK
wO1bwUhzxWFQcNKfeERCUspIwSO7WA7Je380Nx/iMgWPzFoiwFy57Sgw1MMFWpT5
Co7dVjuy4N0QmzdTSCWWTrLVMp91FENxjRDYhqU0I00xEIrgZnGfF8CC4u5tz3TC
7sNs5NGIcR1dDZFsjDF17OBiPnJOQcXjJ4JAj8DQewRKrbFoaJKO1ysSR5PztLtJ
ozz3ebuhvM4pE4K5WcCFzl7sEupSBPVZDFmpgq750BIgDpIVngAAHb8wjne7fWYS
pdsJhnErCbPm6pGzLHqKhsYOrgC2MpU+JXePEvmfSXshjOJlVkTRHv53zdjnaVOQ
7hN4dP6ULdY1OBc9Sh28f9BjCE20lm6KVtv8k7F6LsZsgdrRQTLBwSDoo9FKx+MY
amasWYsTJdCyDBs9DySbuFxXqa0H7DhTwVGl2svE0ijZipOeF+ef+FpUScCQrytb
CznG5BWSBTvdDBqoUdDao5KbGAdwYB9QuJqOamBBJxdOCObD//plmPvmW7cTjgov
ucBJA0tSxLLR
=3all
-----END PGP SIGNATURE-----

Ah, right, I forgot about the "(arch=amd64)" inline option, which is the
better choice indeed. Sorry for the red herring, and thanks for taking
care!

Cheers,
Flo