Your message dated Wed, 28 Dec 2022 20:40:02 +0000
with message-id <e1paddw-001kwq...@fasolo.debian.org>
and subject line Bug#1025262: fixed in mir 1.8.2+dfsg-5
has caused the Debian Bug report #1025262,
regarding mir FTBFS, symbols files issues.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1025262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mir
Version: 1.8.2+dfsg-3
Severity: serious
Tags: ftbfs

mir FTBFS on all architectures with symbols files issues
(there was previously a bug report for hppa, but since it now fails on release
architectures I feel a seperate bug report is deserved).

https://buildd.debian.org/status/fetch.php?pkg=mir&arch=amd64&ver=1.8.2%2Bdfsg-4%2Bb1&stamp=1669159921&raw=0

--- debian/libmirprotobuf3.symbols (libmirprotobuf3_1.8.2+dfsg-4+b1_amd64)
+++ dpkg-gensymbolskixGS3       2022-11-22 23:31:49.399075926 +0000
@@ -8,75 +8,85 @@
  MIR_PROTOBUF_PROTOBUF_3.6.0@MIR_PROTOBUF_PROTOBUF_3.6.0 1.7
  MIR_PROTOBUF_UBSAN@MIR_PROTOBUF_UBSAN 1.7
  _ZN3mir8protobuf10Connection12InternalSwapEPS1_@MIR_PROTOBUF_FEDORA 1.7
- _ZN3mir8protobuf10Connection16default_instanceEv@MIR_PROTOBUF_3 1.7
+#MISSING: 1.8.2+dfsg-4+b1# 
_ZN3mir8protobuf10Connection16default_instanceEv@MIR_PROTOBUF_3 1.7
  
_ZN3mir8protobuf10Connection21CheckTypeAndMergeFromERKN6google8protobuf11MessageLiteE@MIR_PROTOBUF_3
 1.7
  _ZN3mir8protobuf10Connection5ClearEv@MIR_PROTOBUF_3 1.7
  _ZN3mir8protobuf10Connection8CopyFromERKS1_@MIR_PROTOBUF_3 1.7
  _ZN3mir8protobuf10Connection9MergeFromERKS1_@MIR_PROTOBUF_3 1.7
- (arch=alpha amd64 arm64 armel armhf i386 m68k mips64el mipsel powerpc ppc64 
ppc64el riscv64 s390x sh4 sparc64 
x32)_ZN3mir8protobuf10ConnectionC1EPN6google8protobuf5ArenaE@MIR_PROTOBUF_3 
1.8.0+dfsg1
+#MISSING: 1.8.2+dfsg-4+b1# (arch=alpha amd64 arm64 armel armhf i386 m68k 
mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 
x32)_ZN3mir8protobuf10ConnectionC1EPN6google8protobuf5ArenaE@MIR_PROTOBUF_3 
1.8.0+dfsg1
+ _ZN3mir8protobuf10ConnectionC1EPN6google8protobuf5ArenaEb@MIR_PROTOBUF_3 
1.8.2+dfsg-4+b1
  _ZN3mir8protobuf10ConnectionC1ERKS1_@MIR_PROTOBUF_3 1.7
  (arch=hppa)_ZN3mir8protobuf10ConnectionC1Ev@MIR_PROTOBUF_3 1.8.0+dfsg1
- (arch=alpha amd64 arm64 armel armhf i386 m68k mips64el mipsel powerpc ppc64 
ppc64el riscv64 s390x sh4 sparc64 
x32)_ZN3mir8protobuf10ConnectionC2EPN6google8protobuf5ArenaE@MIR_PROTOBUF_3 
1.8.0+dfsg1
+#MISSING: 1.8.2+dfsg-4+b1# (arch=alpha amd64 arm64 armel armhf i386 m68k 
mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x sh4 sparc64 
x32)_ZN3mir8protobuf10ConnectionC2EPN6google8protobuf5ArenaE@MIR_PROTOBUF_3 
1.8.0+dfsg1
+ _ZN3mir8protobuf10ConnectionC2EPN6google8protobuf5ArenaEb@MIR_PROTOBUF_3 
1.8.2+dfsg-4+b1
  _ZN3mir8protobuf10ConnectionC2ERKS1_@MIR_PROTOBUF_3 1.8.0+dfsg1
  (arch=hppa)_ZN3mir8protobuf10ConnectionC2Ev@MIR_PROTOBUF_3 1.8.0+dfsg1

and so on.

I presume this is related to the new version of protobuf.

--- End Message ---
--- Begin Message ---
Source: mir
Source-Version: 1.8.2+dfsg-5
Done: Mike Gabriel <sunwea...@debian.org>

We believe that the bug you reported is fixed in the latest version of
mir, 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 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel <sunwea...@debian.org> (supplier of updated mir 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 01 Dec 2022 21:38:44 +0100
Source: mir
Architecture: source
Version: 1.8.2+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Mir Team <team+...@tracker.debian.org>
Changed-By: Mike Gabriel <sunwea...@debian.org>
Closes: 1025262
Changes:
 mir (1.8.2+dfsg-5) unstable; urgency=medium
 .
   [ Anton Gladky ]
   * Add debian/.gitlab-ci.yml
 .
   [ Mike Gabriel ]
   * debian/libmirprotobuf3.symbols:
     + Update .symbols after upload of new protobuf library. (Closes: #1025262).
Checksums-Sha1:
 6df872340b0d561c0c704e330fa4f816c17e2cff 5884 mir_1.8.2+dfsg-5.dsc
 f905f281cefef8959fff90de745f6a2525516d23 69212 mir_1.8.2+dfsg-5.debian.tar.xz
 184cfba5ffb38b97123a2683e4b56026da6d7896 15071 
mir_1.8.2+dfsg-5_source.buildinfo
Checksums-Sha256:
 bddcc0bcab3938cbc6c6ba82bb6f1b5e51a00a97e8c3eae53be4755da84cb1f7 5884 
mir_1.8.2+dfsg-5.dsc
 46ae6d460a131f192ff61da1884db36d5f4bc3f18c4b57e70e29ea71b098bb63 69212 
mir_1.8.2+dfsg-5.debian.tar.xz
 72d6d61ac789fca88718a711d177da2db494855cc5b808f7eda468dca46b345d 15071 
mir_1.8.2+dfsg-5_source.buildinfo
Files:
 f24fd15c9d5ff1c02c86ef6881977b75 5884 x11 optional mir_1.8.2+dfsg-5.dsc
 48a50dd03a8ee086f853ddbf2d18b266 69212 x11 optional 
mir_1.8.2+dfsg-5.debian.tar.xz
 74514a8236ab323efc6c64410e427245 15071 x11 optional 
mir_1.8.2+dfsg-5_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmOsmzoVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsx6rgQAJNG7K3LMblzLjHS4T9H+Y7Szcnh
i4i0gjZSX/ZOcWLONsmS2ut9PAMk2K1ngiStNlzt3JTI9cZRQax7JIIrr1qlaJFK
Bq128FOLF+3CgEIVZ06VQIIYhAWTkihGl68Zmc5NKf1MwkpCRvlEbivYNGh2tiVu
NWgW7FJSfBQGk8XaSiT0CdqOx9VbjHii3A6UGUBptizjJ/15BxPSRlpgpfB/8djL
fAGuqCU88h4nXa+Y9xEfMCIIb99PNemjMUIn0QRSNNfHwFVHaafH9yJ4sUk4suX3
5nWVvOS6T6+acDRiaT23idH7iNkKBa7/+MTr1nCsrBU7CW1LGCj9i/kK7/kaio+B
yEY140Pxf7r5Nc5IORDfK9k87MKCnlLS2NyLnQW3NFPfMUC5vNgZQBM4q+68WrIG
hqYBHt/5E1Q0w5utaRVs3vMtT886GgNgXvwhAFHaEJxzgDH9R968EaZ6S2AXPlU1
NDHB6pRksFYmEJDAwKL9SC3mi/Zy2Xn2NPJoY27j4Bt5V6menZP0F8O4pSa8Ffkg
XK17gtJa4Myv8OwV+KJI0gcV0MonO80auoSGo54b/z8DBNM9t9CxxHiixzv0gcqj
e2ppwr7tjs7hg+TpjFCt+AzAJ6EkQ8NezzYzP444B0j+3aQvSi28x4Bj3ZErauj1
Xh/7m+8RQDkWnnYn
=+Q4O
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to