Your message dated Sun, 02 Feb 2020 23:41:54 +0000
with message-id <e1iyose-000f29...@fasolo.debian.org>
and subject line Bug#950169: fixed in gexiv2 0.12.0-2
has caused the Debian Bug report #950169,
regarding gexiv2 ftbfs with libexiv2-27
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.)


-- 
950169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gexiv2
Version: 0.12.0-1
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye

Dear maintainer,

exiv2 started a transition and I scheduled binNMUs. However, your
package failed. Please investigate.

Paul

Tail of log for gexiv2 on amd64:

../gexiv2/gexiv2-metadata.cpp:184:14: error: conflicting return type
specified for ‘virtual long int {anonymous}::GioIo::size() const’
  184 |     long int size() const {
      |              ^~~~
In file included from /usr/include/exiv2/exiv2.hpp:34,
                 from ../gexiv2/gexiv2-metadata-private.h:14,
                 from ../gexiv2/gexiv2-metadata.cpp:12:
/usr/include/exiv2/basicio.hpp:213:24: note: overridden function is
‘virtual size_t Exiv2::BasicIo::size() const’
  213 |         virtual size_t size() const = 0;
      |                        ^~~~
[6/23] c++ -Igexiv2/1a6c516@@gexiv2@sha -Igexiv2 -I../gexiv2 -Igexiv2/..
-I../gexiv2/.. -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount
-I/usr/include/blkid -fdiagnostics-color=always -pipe
-D_FILE_OFFSET_BITS=64 -std=c++11 -g -O2
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread
-MD -MQ 'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-gps.cpp.o' -MF
'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-gps.cpp.o.d' -o
'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-gps.cpp.o' -c
../gexiv2/gexiv2-metadata-gps.cpp
[7/23] c++ -Igexiv2/1a6c516@@gexiv2@sha -Igexiv2 -I../gexiv2 -Igexiv2/..
-I../gexiv2/.. -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount
-I/usr/include/blkid -fdiagnostics-color=always -pipe
-D_FILE_OFFSET_BITS=64 -std=c++11 -g -O2
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread
-MD -MQ 'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-exif.cpp.o' -MF
'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-exif.cpp.o.d' -o
'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-exif.cpp.o' -c
../gexiv2/gexiv2-metadata-exif.cpp
[8/23] c++ -Igexiv2/1a6c516@@gexiv2@sha -Igexiv2 -I../gexiv2 -Igexiv2/..
-I../gexiv2/.. -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount
-I/usr/include/blkid -fdiagnostics-color=always -pipe
-D_FILE_OFFSET_BITS=64 -std=c++11 -g -O2
-fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread
-MD -MQ 'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-iptc.cpp.o' -MF
'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-iptc.cpp.o.d' -o
'gexiv2/1a6c516@@gexiv2@sha/gexiv2-metadata-iptc.cpp.o' -c
../gexiv2/gexiv2-metadata-iptc.cpp
ninja: build stopped: subcommand failed.
dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja
-j4 -v returned exit code 1
make: *** [debian/rules:13: binary-arch] Error 25

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: gexiv2
Source-Version: 0.12.0-2

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

Debian distribution maintenance software
pp.
Jason Crain <ja...@inspiresomeone.us> (supplier of updated gexiv2 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: SHA512

Format: 1.8
Date: Sun, 02 Feb 2020 04:29:42 -0700
Source: gexiv2
Architecture: source
Version: 0.12.0-2
Distribution: unstable
Urgency: medium
Maintainer: Jason Crain <ja...@inspiresomeone.us>
Changed-By: Jason Crain <ja...@inspiresomeone.us>
Closes: 942519 950169
Changes:
 gexiv2 (0.12.0-2) unstable; urgency=medium
 .
   * Drop patch Use-exiv2-version-0.25.patch.
     Exiv2 version 0.27 is now in Debian unstable. Drop this patch so gexiv2
     can build against it. (Closes: #942519, #950169)
   * Update Standards-Version to 4.5.0.
     No changes necessary.
Checksums-Sha1:
 13147be172f2844ee99a9917c0fa59a4f93cbe0d 2237 gexiv2_0.12.0-2.dsc
 425b16689613bcd8cd38e8815df3ee3c9119cee7 9096 gexiv2_0.12.0-2.debian.tar.xz
 0b3148d77a8015cb1c2b20a41911646aab3eb98a 7817 gexiv2_0.12.0-2_source.buildinfo
Checksums-Sha256:
 07f2fb6e1eb97258061dc800aaa2047eaea5b54b0a1bec93ba014e1c9d213cb6 2237 
gexiv2_0.12.0-2.dsc
 41e920e69304a8de8a7dec20476572d0a91e604c8957ce7b7f28bb76064c7a17 9096 
gexiv2_0.12.0-2.debian.tar.xz
 58e4e3173ac1d9f246c3bb0418957a6efe9fb6b062af516259c32ae815aa24d1 7817 
gexiv2_0.12.0-2_source.buildinfo
Files:
 b2d4b6820445e46299426a2f75927b3a 2237 libs optional gexiv2_0.12.0-2.dsc
 fce1a45d41e03fee0fcb22945e539bb0 9096 libs optional 
gexiv2_0.12.0-2.debian.tar.xz
 3db7c242c532dffa9b08af9a984a2339 7817 libs optional 
gexiv2_0.12.0-2_source.buildinfo

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

iQIyBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl43UnQACgkQweDZLphv
fH6mIg/4iOnUGdU/79eg0QJCSprEqgDoL+04vQqcW1638NnXVWSVKYTwoY6V7rOj
NRe+iJu3i2CxBoZkOrqChbcWtSLvK2FDwLXt1HLFoXCFzaWQ+KA79//RIap+S5gz
ImJQ8myYAM3n4wBeP2oSo9ZExyeanFGM+ACjNKE1T0y/3S9kDVQw8HRXK3uPSiHc
0bYtr+soc4c8wVajZcbxPJZuhvD9S4e4m/g56N9dWv4vQBGu4QesjQyFDI+vmD9r
2Rs9RgSsTGE3JB0ssDWYMVE2ccLEcrG126MqU3WZL2DavuhrbjQJYJRBFlVrtq5t
4afxf0buPeECvtZiaDSkYTXOVKBmfOiuB6RrYBw6CrkLXPL6OHf14WHD211/Sfdi
yCzRWybXBIo+f15wVp5uHyHosIjxzls1cnYkF0pJq0TwuTPHhpze3Mf+ql1dem21
utpcr3NQqhAuQ5CfXN0Uy+r1NWp/8z5pqS68v4WkTZ2kZyI0ly65aic8jjVjAVdQ
wWUOgShjWW62KuY2AusxxX6pJ8TyJUkqT5k0uElRGK70mBeUhGQEbOW+uBLEEPKW
U0t8BJNw7zoV6/5F5mzkQHP8j1LOvO/V2agDt6mArks7YLr8DCrJQfYw+UC09eSn
+QH/zj5G2YFy29gbFBkwA5HUb9EWTDmoB6GYpSIYMrlj5y5/FQ==
=1zRR
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to