Your message dated Thu, 13 Aug 2026 16:48:57 +0000
with message-id <[email protected]>
and subject line Bug#1110591: fixed in gpsshogi 0.7.0-3.4
has caused the Debian Bug report #1110591,
regarding gpsshogi ftbfs with boost1.88
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 [email protected]
immediately.)
--
1110591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110591
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:gpsshogi
Version: 0.7.0-3.2
Severity: important
Tags: sid forky
User: [email protected]
Usertags: boost1.88
gpsshogi ftbfs with boost1.88:
[...]
g++ -DOSL_SMP -g -O2 -fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-flto=auto -ffat-lto-objects -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-fcf-protection
-fdebug-prefix-map=/<<PKGBUILDDIR>>=/usr/src/gpsshogi-0.7.0-3.2build2
-Wdate-time -D_FORTIFY_SOURCE=3 -O3 -DNDEBUG -g -I.. -I../include
-Wdate-time -D_FORTIFY_SOURCE=3 -c -o gpsusi.o gpsusi.cc
gpsusi.cc:102:14: error: ‘io_service’ in namespace ‘boost::asio’ does
not name a type; did you mean ‘use_service’?
102 | boost::asio::io_service io_service;
| ^~~~~~~~~~
| use_service
gpsusi.cc: In function ‘void play(std::istream&, std::ostream&)’:
gpsusi.cc:857:28: error: ‘io_service’ was not declared in this scope
857 | udp::resolver resolver(io_service);
| ^~~~~~~~~~
gpsusi.cc:858:20: error: ‘query’ is not a member of
‘boost::asio::ip::udp::resolver’ {aka
‘boost::asio::ip::basic_resolver<boost::asio::ip::udp>’}
858 | udp::resolver::query query(udp::v4(), args[0], args[1]);
| ^~~~~
gpsusi.cc:862:60: error: ‘query’ was not declared in this scope
862 | udp_endpoint.reset(new
udp::endpoint(*resolver.resolve(query)));
| ^~~~~
gpsusi.cc:862:60: note: suggested alternatives:
In file included from /usr/include/boost/asio/execution/blocking.hpp:23,
from
/usr/include/boost/asio/execution/any_executor.hpp:31,
from /usr/include/boost/asio/execution.hpp:19,
from /usr/include/boost/asio/any_io_executor.hpp:22,
from /usr/include/boost/asio/basic_socket.hpp:19,
from /usr/include/boost/asio/basic_datagram_socket.hpp:20,
from /usr/include/boost/asio/ip/udp.hpp:19,
from /usr/include/osl/search/usiReporter.h:7,
from gpsusi.cc:20:
/usr/include/boost/asio/query.hpp:114:6: note:
‘boost_asio_query_fn::query’
114 | void query();
| ^~~~~
/usr/include/boost/asio/query.hpp:263:3: note:
‘boost::asio::{anonymous}::query’
263 | query = boost_asio_query_fn::static_instance<>::instance;
| ^~~~~
gpsusi.cc: In function ‘int main(int, char**)’:
gpsusi.cc:1345:30: error: ‘io_service’ was not declared in this scope
1345 | tcp::resolver resolver(io_service);
| ^~~~~~~~~~
gpsusi.cc:1346:22: error: ‘query’ is not a member of
‘boost::asio::ip::tcp::resolver’ {aka
‘boost::asio::ip::basic_resolver<boost::asio::ip::tcp>’}
1346 | tcp::resolver::query query(tcp::v4(), args[1], args[2]);
| ^~~~~
gpsusi.cc:1347:46: error: ‘query’ was not declared in this scope
1347 | tcp::endpoint server(*resolver.resolve(query));
| ^~~~~
gpsusi.cc:1347:46: note: suggested alternatives:
/usr/include/boost/asio/query.hpp:114:6: note:
‘boost_asio_query_fn::query’
114 | void query();
| ^~~~~
/usr/include/boost/asio/query.hpp:263:3: note:
‘boost::asio::{anonymous}::query’
263 | query = boost_asio_query_fn::static_instance<>::instance;
| ^~~~~
make[2]: *** [<builtin>: gpsusi.o] Error 1
--- End Message ---
--- Begin Message ---
Source: gpsshogi
Source-Version: 0.7.0-3.4
Done: Bastian Germann <[email protected]>
We believe that the bug you reported is fixed in the latest version of
gpsshogi, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Germann <[email protected]> (supplier of updated gpsshogi 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 13 Aug 2026 17:19:02 +0200
Source: gpsshogi
Architecture: source
Version: 0.7.0-3.4
Distribution: unstable
Urgency: medium
Maintainer: Yann Dirson <[email protected]>
Changed-By: Bastian Germann <[email protected]>
Closes: 1110591
Changes:
gpsshogi (0.7.0-3.4) unstable; urgency=medium
.
* Non-maintainer upload
.
[ Mateus Rodrigues de Morais ]
* fix: compatibility with Boost 1.88 by updating deprecated APIs
.
[ Bastian Germann ]
* Drop boost_system dependency, set empty BOOST_LIBS (Closes: #1110591)
Checksums-Sha1:
1de0999200de71b29a3679280f3c5af7c72a6b9c 2039 gpsshogi_0.7.0-3.4.dsc
531588f91e41595d08898d2f03daed988953344f 20572 gpsshogi_0.7.0-3.4.debian.tar.xz
b4032febec332d4457591a44aa9d20e2c87a7661 17796
gpsshogi_0.7.0-3.4_source.buildinfo
Checksums-Sha256:
fd730a179956b6adc4ce3c3fedda4537ba1f23538adfcadb1708c8bfb3d2e5d2 2039
gpsshogi_0.7.0-3.4.dsc
bcc32e5d4ccfebbbad955c245a9dc989576de8a799619a63694a688c08676097 20572
gpsshogi_0.7.0-3.4.debian.tar.xz
bfd5336c3900fb1623d9de71dbf88c0ba70239ecfb1d157623075d5b4933ef93 17796
gpsshogi_0.7.0-3.4_source.buildinfo
Files:
e8eabd64faf2d4f8431088a8f9826878 2039 games optional gpsshogi_0.7.0-3.4.dsc
18f6d3ddd9039447fb27c454bf5b7d65 20572 games optional
gpsshogi_0.7.0-3.4.debian.tar.xz
51838622b5fa51b9c415f84486b5feef 17796 games optional
gpsshogi_0.7.0-3.4_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmp96QIQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFHdZDACuw6gOCJDRhy3ak7fkeGbqqDDRei3YdmdQ
DoJiBcw2MYuL1Z3/tvsHr8yuboa6JKXXOK+5aU6y1MwZILixGqwBT41GJ38WiVbZ
F6Oh/aMHZjuogpqxwHxMHEkvNTHT+kdzomGyPncq3naPQ1FhRFNlx3QSgFSxv8Nt
zBpIQJOo3+PnKPgRIB/zpSjdKlDd75nCfpY3R4qxTmpp5A+s6ugJ67M9rf3WsBa1
ZN39IH0cPywa84C0oE/JoIYdAwN6b73CQEW7DQhi4Z3SMstobGmq75mBZhq2X4os
vPIywQPqaO9nWqdcfApZ6e9Mrk3E2fmp3Jq0HbdAbQY2pO4KKPyAfVU6ZE37BwJL
sgVrUSqbiysOlscqpdPDyDMABqexTyJof5Q7FXUsPUeOlJVhQ2Sx2sz50oTN3fMP
SdDU7eWYKb+erKwx84p1fAH1ZlHs1OC5Gtjuse8VOufm97iVHmL2r91dhk2Y2MDC
RIixQaF+lVuIbZ2mmhxSuaQe4xx0jtY=
=t3MW
-----END PGP SIGNATURE-----
pgpbYHj1ojZNc.pgp
Description: PGP signature
--- End Message ---
