libsnappy-dev: Ambiguity in Compress method signatures causes FTBFS in ceph
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snappy (Debian) |
Fix Released
|
Unknown
|
|||
snappy (Ubuntu) |
Triaged
|
High
|
Unassigned |
Bug Description
Imported from Debian bug http://
Package: libsnappy-dev
Version: 1.2.0-2
Severity: important
Tags: ftbfs
X-Debbugs-Cc: <email address hidden>
Dear Maintainer,
The patch added to restore older API signatures to resolve Bug 1070217
creates ambiguity in the method signatures resulting in FTBFS in at
least the ceph package:
In file included from /<<PKGBUILDDIR>
/<<PKGBUILDDIR>
/<<PKGBUILDDIR>
68 | snappy:
| ~~~~~~~
In file included from /<<PKGBUILDDIR>
/usr/include/
81 | size_t Compress(Source* reader, Sink* writer);
| ^~~~~~~~
/usr/include/
82 | size_t Compress(Source* reader, Sink* writer,
| ^~~~~~~~
make[3]: *** [src/compressor
make[3]: Leaving directory '/<<PKGBUILDDIR
make[2]: *** [CMakeFiles/
The compression options parameter which was added for >= 1.2 of snappy
provides a default, so the added method with no options creates this
ambiguity.
Thanks!
-- System Information:
Debian Release: trixie/sid
APT prefers oracular
APT policy: (500, 'oracular')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.8.0-31-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETA
Locale: LANG=en_GB.UTF-8, LC_CTYPE=
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/
LSM: AppArmor: enabled
Versions of packages libsnappy-dev depends on:
ii libsnappy1v5 1.2.0-2
libsnappy-dev recommends no packages.
libsnappy-dev suggests no packages.
-- no debconf information
Changed in snappy (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in snappy (Debian): | |
importance: | Undecided → Unknown |
Changed in snappy (Debian): | |
status: | New → Fix Released |