Your message dated Sun, 25 Dec 2022 17:07:45 +0000
with message-id <e1p9utr-0014hs...@fasolo.debian.org>
and subject line Bug#1005435: fixed in libppd 2:0.10-9
has caused the Debian Bug report #1005435,
regarding gpr: FTBFS: configure: error: Must have libppd installed to compile 
gpr
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.)


-- 
1005435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpr
Version: 0.15deb-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> checking for unistd.h... yes
> checking ppd.h usability... yes
> checking ppd.h presence... yes
> checking for ppd.h... yes
> checking for ppd_file_new in -lppd... no
> configure: error: Must have libppd installed to compile gpr


The full build log is available from:
http://qa-logs.debian.net/2022/02/12/gpr_0.15deb-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message ---
Source: libppd
Source-Version: 2:0.10-9
Done: Christoph Biedl <debian.a...@manchmal.in-ulm.de>

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

Debian distribution maintenance software
pp.
Christoph Biedl <debian.a...@manchmal.in-ulm.de> (supplier of updated libppd 
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, 25 Dec 2022 16:54:57 +0100
Source: libppd
Architecture: source
Version: 2:0.10-9
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl <debian.a...@manchmal.in-ulm.de>
Changed-By: Christoph Biedl <debian.a...@manchmal.in-ulm.de>
Closes: 1005435
Changes:
 libppd (2:0.10-9) unstable; urgency=medium
 .
   * autoconf: Probe for glib-2.0 in order to create proper symbols.
     Closes: #1005435
Checksums-Sha1:
 8ad041bb960240d4613a0a048af798ec32d3e6f9 1865 libppd_0.10-9.dsc
 9c84722614205ea352925917416798718dbc60a4 9228 libppd_0.10-9.debian.tar.xz
 a44c4118b2080d7ee2713d0f1814fc39212d7577 7877 libppd_0.10-9_armel.buildinfo
Checksums-Sha256:
 2285ce12a86d20e6ae2d55916df15075e40599ccf142049786a9fe71d11576ec 1865 
libppd_0.10-9.dsc
 ff03b59c9131769edd36ba7344079764a6c1b797a1a0b6c62ababdc7febd3831 9228 
libppd_0.10-9.debian.tar.xz
 a44ed8b60309c7c8066f0367eec926eab7b82805663517fcaac361b2f7d6b6b6 7877 
libppd_0.10-9_armel.buildinfo
Files:
 936a2ba49e57d6956e28041e08abbe94 1865 libs optional libppd_0.10-9.dsc
 3f85029cfddbbe4780f2f73026ad8fff 9228 libs optional libppd_0.10-9.debian.tar.xz
 cfc9caf1ca3286db776191aec4953014 7877 libs optional 
libppd_0.10-9_armel.buildinfo

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

iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAmOoe6EACgkQxCxY61kU
kv0v+g/5ARO1H8UDTSn75e7hwVZ/f0yrHgVRS3yjAgdJBnNECrq0SH5DWcj6yJJP
rRlV2b2wE7YLTvs7vgfJwZzXvUyH0rHXQ8U4fFZ+6pPFeKXDK7xMvnz1PjxIuQ8L
TugwpdUMUpvNHdehm/8ZJOzGvi7yMgJ+jLOW+gKGNalWlhgtdE9bN7UDwJ0fh1VP
VdVaw+2BFUDEnqgyH9gP1PpqaPVgBf9XDm6oyncydPBthBubtBn5Zhv/CsFGaocE
QYHJVKJzR1/EgSBXM/2QUrmnr90lDrTvyQXtE5GtibUkx3ki/fQW7xo8PQuqla+v
Xoc8K7WSI76ucGEkkgtrRUlCIfIM5xyKmPlapqlrEfAuY5AeY841xhabIG2tOmj0
Bxpep79rzXjyArhZp97g34PjdlRB32UXqZU+dQGQHU4A+q6ZeYLio8cK9zpB2Lcf
ebH9MDOClhC3xT8oD+4WOKeqpe6CZZKm1IQJXmFBv6aBz1cBHHR07pdjn+Pz3pem
cAjpjQTgfvkfrhdHo2p2c4ozY6dLBExMFh2OpOSzIj4ftCASdluJYONIneANKyEC
cvAKwjYL6ZHnwtjjS62Fc5edvPXOlNkwDVtf3kL3XMPaTIWHoX4p8fP29yhjvSwM
8E4pTi+FAf9tCFxVsE7Xoi4PlQw7u1iBWFNn7TtNTT7/lLGONbA=
=7B5/
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to