Your message dated Tue, 20 Dec 2016 16:19:12 +0000
with message-id <[email protected]>
and subject line Bug#848778: fixed in gnupg-pkcs11-scd 0.7.3-3
has caused the Debian Bug report #848778,
regarding gnupg-pkcs11-scd: FTBFS: build-dependency not installable: libssl-dev
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.)


-- 
848778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848778
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gnupg-pkcs11-scd
Version: 0.7.3-2
Severity: serious
Tags: stretch sid
User: [email protected]
Usertags: qa-ftbfs-20161219 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> +------------------------------------------------------------------------------+
> | Install package build dependencies                                          
>  |
> +------------------------------------------------------------------------------+
> 
> 
> Setup apt archive
> -----------------
> 
> Merged Build-Depends: debhelper (>= 9), autotools-dev, libassuan-dev, 
> libgpg-error-dev, libgcrypt11-dev, libpkcs11-helper-dev, libssl-dev, 
> pkg-config
> Filtered Build-Depends: debhelper (>= 9), autotools-dev, libassuan-dev, 
> libgpg-error-dev, libgcrypt11-dev, libpkcs11-helper-dev, libssl-dev, 
> pkg-config
> dpkg-deb: building package 'sbuild-build-depends-gnupg-pkcs11-scd-dummy' in 
> '/<<BUILDDIR>>/resolver-klcAYG/apt_archive/sbuild-build-depends-gnupg-pkcs11-scd-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-gnupg-pkcs11-scd-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<<BUILDDIR>>/resolver-klcAYG/apt_archive ./ InRelease
> Get:2 copy:/<<BUILDDIR>>/resolver-klcAYG/apt_archive ./ Release [963 B]
> Ign:3 copy:/<<BUILDDIR>>/resolver-klcAYG/apt_archive ./ Release.gpg
> Get:4 copy:/<<BUILDDIR>>/resolver-klcAYG/apt_archive ./ Sources [546 B]
> Get:5 copy:/<<BUILDDIR>>/resolver-klcAYG/apt_archive ./ Packages [625 B]
> Fetched 2134 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install gnupg-pkcs11-scd build dependencies (apt-based resolver)
> ----------------------------------------------------------------
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-gnupg-pkcs11-scd-dummy : Depends: libssl-dev but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/12/19/gnupg-pkcs11-scd_0.7.3-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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
Source: gnupg-pkcs11-scd
Source-Version: 0.7.3-3

We believe that the bug you reported is fixed in the latest version of
gnupg-pkcs11-scd, 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.
Thorsten Alteholz <[email protected]> (supplier of updated gnupg-pkcs11-scd 
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: Tue, 20 Dec 2016 16:07:31 +0100
Source: gnupg-pkcs11-scd
Binary: gnupg-pkcs11-scd gnupg-pkcs11-scd-dbg
Architecture: source amd64
Version: 0.7.3-3
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz <[email protected]>
Changed-By: Thorsten Alteholz <[email protected]>
Description:
 gnupg-pkcs11-scd - GnuPG smart-card daemon with PKCS#11 support
 gnupg-pkcs11-scd-dbg - GnuPG smart-card daemon with PKCS#11 support (debug)
Closes: 848778
Changes:
 gnupg-pkcs11-scd (0.7.3-3) unstable; urgency=medium
 .
   * debian/control: switch to libssl1.0-dev (Closes: #848778)
                     (this has been done by pkcs11-helper and I have
                      to follow)
Checksums-Sha1:
 caa97c296cc28ff80341d7fc9453ab6965f7934d 2282 gnupg-pkcs11-scd_0.7.3-3.dsc
 2d7e35254df96b295eb2d970021c18f3470ea78a 150358 
gnupg-pkcs11-scd_0.7.3.orig.tar.gz
 870c886251191ad08fa57f4a55e3558d6eb8bfe9 3900 
gnupg-pkcs11-scd_0.7.3-3.debian.tar.xz
 66208aed9c7e2ee4cfc811d95be5e7833b351bc8 60076 
gnupg-pkcs11-scd-dbg_0.7.3-3_amd64.deb
 9ff258131179494ae2a5a1d323616330479229eb 5112 
gnupg-pkcs11-scd_0.7.3-3_amd64.buildinfo
 508d3aef2ccf59cda76f2510c786fbdba60c2c3f 26140 
gnupg-pkcs11-scd_0.7.3-3_amd64.deb
Checksums-Sha256:
 b071e5e4424b2352a0393b7c467a7f346710b03070a94effd2f1f8e8afb245c4 2282 
gnupg-pkcs11-scd_0.7.3-3.dsc
 04bd11d07b89b0cae40df14e698d35eb5c7067b6c62823dc75fc2ca3b196e338 150358 
gnupg-pkcs11-scd_0.7.3.orig.tar.gz
 956582b0e7e6c6cdbf76bbe9c5ff8be672fd8e432ebeae2ce34eafab0164b8a5 3900 
gnupg-pkcs11-scd_0.7.3-3.debian.tar.xz
 5ea891bb92ce2bb6f61777b2a870f59230275bd425f9b6ceb905378bf3039dfb 60076 
gnupg-pkcs11-scd-dbg_0.7.3-3_amd64.deb
 9d44f05979061fe81f4fb3aca5f2013933411730ec83807499b5c618ac0f90bb 5112 
gnupg-pkcs11-scd_0.7.3-3_amd64.buildinfo
 7d45e8ee10ba21e8bc0f46670cc4e4d106e1f9a02f85d5d0175b5dd9c2433173 26140 
gnupg-pkcs11-scd_0.7.3-3_amd64.deb
Files:
 2cd889ef022a515c2c3f8b4e207f821b 2282 utils optional 
gnupg-pkcs11-scd_0.7.3-3.dsc
 a91680d73f814bd3a16fa4a72e0ee998 150358 utils optional 
gnupg-pkcs11-scd_0.7.3.orig.tar.gz
 6485b26742da67dabacb3b1cb7c80821 3900 utils optional 
gnupg-pkcs11-scd_0.7.3-3.debian.tar.xz
 e7d5a3178cd0d6ae54a213108eb1501b 60076 debug extra 
gnupg-pkcs11-scd-dbg_0.7.3-3_amd64.deb
 22c538533ccea758084bbb140a187c85 5112 utils optional 
gnupg-pkcs11-scd_0.7.3-3_amd64.buildinfo
 fdf4fd8a035b6a09774057411b912142 26140 utils optional 
gnupg-pkcs11-scd_0.7.3-3_amd64.deb

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

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAlhZVdBfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR9MzEACXx0gKF15B50O+r8CvZWot20NnXV/S
iVXz6r+tqytazXx51sxkkb3y3KY1xUnDR8fGi8yKBnzsU+Z9aIhF0Ayjv/SUGyCF
xhFE1lm44FXqDtmDPWKZsy/XhffYzr9SvIQjjEiMzZZG4M9ZUYo/sUngUFWMIw2l
EJr9udwbSo1n0bQsNK6yHAp45gupsO0z2IyHk4wI0J5LnR4w4R0+FJYiqPstFjq9
KjYGJOw28s+s0wPcRHsvksxSo1AfLQU2V5SqZiFOaAWEP9gD7MvBXX4szYPlKHcD
wNSUL7kMBtIq36kwG/jvVCkyS5o2SdQdsVGELOhzUOyonvBtZajFWMS5cjNwB2Cm
u7YYa29aTqoRN1Fr5SGE2rr5O1XCzM/vBxEnEeMsy32aXA3XiHjbKbj4kKCOSNBy
hd/ax2VaCSMiS9cR/3FlwVqucESA2AJVuUXNAABRyf/5I+InzS/Eq3OKKFeYfkEk
LIPW0MJyJrfBYMQAljDHyq8tzf35rTaAPo7AVe7CcFg/UTqstDUhEV7TeCVNoKil
2rTQZbfZAdHpTuR4OnxfyXk9qFqp4fVDYjZEoPFctn/1LEf0DHVGkr44DrfNh+uE
7wOfbfjS/+zpvMpDbFnUbX9HIIh/+YG0Lz6/fvDdDKYnOupZpYNNX4I26hsfDjHY
Hb0DtoEV5sMwgA==
=+E7O
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to