Your message dated Sat, 11 Mar 2023 11:33:58 +0000
with message-id <e1paxu6-002dev...@fasolo.debian.org>
and subject line Bug#1018023: fixed in eterm 0.9.6-7
has caused the Debian Bug report #1018023,
regarding eterm: FTBFS with imlib2 1.9.1
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.)


-- 
1018023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: eterm
Version: 0.9.6-6.1
Severity: important
Tags: ftbfs sid bookwork
User: a...@debian.org
Usertags: imlib2-1.9.1
X-Debbugs-Cc: a...@debian.org

Dear maintainer,

your package fails to build from source with imlib2 1.9.1 in
experimental. imlib2-config has been dropped by upstream in favor of
pkg-config. Please adjust your build system accordingly.

Looking closer there may be a different error that causes the FTBFS
because of newly introduced symbols.


In file included from menus.h:29,
                 from actions.h:31,
                 from actions.c:33:
pixmap.h:224:20: error: conflicting types for ‘imlib_strerror’; have ‘const 
char *(Imlib_Load_Error)’
  224 | extern const char *imlib_strerror(Imlib_Load_Error);
      |                    ^~~~~~~~~~~~~~
In file included from /usr/include/libast.h:79,
                 from feature.h:100,
                 from actions.c:27:
/usr/include/Imlib2.h:2846:21: note: previous declaration of ‘imlib_strerror’ 
with type ‘const char *(int)’
 2846 | EAPI const char    *imlib_strerror(int err);
      |                     ^~~~~~~~~~~~~~



I intend to upload imlib2 1.9.1 to unstable in one or two months. Feel free to
reply to this bug report if you have any questions.

Regards,

Markus

--- End Message ---
--- Begin Message ---
Source: eterm
Source-Version: 0.9.6-7
Done: José Antonio Jiménez Madrid <donjosemad...@gmail.com>

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

Debian distribution maintenance software
pp.
José Antonio Jiménez Madrid <donjosemad...@gmail.com> (supplier of updated 
eterm 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: Fri, 10 Mar 2023 21:03:30 +0100
Source: eterm
Architecture: source
Version: 0.9.6-7
Distribution: unstable
Urgency: medium
Maintainer: José Antonio Jiménez Madrid <donjosemad...@gmail.com>
Changed-By: José Antonio Jiménez Madrid <donjosemad...@gmail.com>
Closes: 1018023
Changes:
 eterm (0.9.6-7) unstable; urgency=medium
 .
   * Fix FTBFS with imlib2 1.9.1. Closes: #1018023.
     Thanks to Matthew Vernon for pointing me to the patch used by netbsd.
Checksums-Sha1:
 6b07a448797528bd9f2f999e0a82735c0af4e2fe 2019 eterm_0.9.6-7.dsc
 5364d433198e6d8dfdf196d66058a0c2ba0e1c1d 14068 eterm_0.9.6-7.debian.tar.xz
Checksums-Sha256:
 091df881c40f4ebb4b462722805c55b15643a1b503ef653af593f66b324c54d1 2019 
eterm_0.9.6-7.dsc
 5611777358b35bdb4178ef33a6e5a1464666fd7276aee5e7b095f6df89792c1e 14068 
eterm_0.9.6-7.debian.tar.xz
Files:
 2555e0127c082c876ef1d0c9bd3276b6 2019 x11 optional eterm_0.9.6-7.dsc
 47c4eeaa3f6b2623c3b1d56ea2bd9227 14068 x11 optional eterm_0.9.6-7.debian.tar.xz

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

iQJHBAEBCgAxFiEEuk75yE35bTfYoeLUEvTSHI9qY8gFAmQMY2UTHG1hdHRoZXdA
ZGViaWFuLm9yZwAKCRAS9NIcj2pjyDp9EACLaLQ6CHzDlJDadPky/9+TZm28lZzu
ceqBdiwktc8G7q39PzwP35fTxKAPuS+kaQMRryLgj2WKhovGlLQqRlwlCO0eo4Jt
sH3EVGVENhonwxh1SuT2PTEqqwjKIxw3IkDRpAn0A+0HTgWNWQCnb2mwBo0h6SKl
Waf51WoFJ4J9Ht/iDnH/LrBSudZbtxMQ5V0ouQYCGcExjSh/RwIQTIXh5b5FQ5hf
kd0RFpUj7j9cxrbnPjXYXfp4h1CmckGQD3TTRWctl/IY5JyX9u1Trnao9SgmQCMw
fWYZrWvt8+Fz0yp+MsQNxxCPnLr3s0JGY6lmoA0s8o9dFHqZshpLQ0yrfTjN4AhQ
Lsfv2mrRREhKeUL3Y9T6GN9tFTOoRM9W24R8uMV+x4J1d0VtAS8XSWhwo9yguTCw
81vRNu6VYDCJcKSnFDQ9YlBY8xq4t7dIXfShROUW4qhNCJ/EjY4T42qZ0kpnvlQA
eA5plh5x0iB2rm1EBUS/ZWuo0DzMBcC7FSZGXgv1RFuAk2QLNl1OMjl00qua4vPA
+7fu9LUqvo0Ku3aa9qWJRVQgcruTTXs6RZg88wofEVjjFSJD5tFpVo+Qo+fS3Gv1
MW0mN8Iy9pmvg2FATUnz7sixe0ocIwVcgYda4wMhy25QBP3S8o+Ilox6rZJt5Bp+
U3qrDnmUL+Y1Mg==
=xiDN
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to