Accepted qbs 1.5.2+dfsg-1 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 02 Aug 2016 00:04:16 +0200
Source: qbs
Binary: qbs qbs-common libqbscore1 libqbsqtprofilesetup1 qbs-dev qbs-examples qbs-doc qbs-doc-html
Architecture: source
Version: 1.5.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>
Changed-By: Adam Majer <adamm@zombino.com>
Description:
libqbscore1 - Qbs core library
libqbsqtprofilesetup1 - Qbs profile setup library
qbs - Qbs build tool
qbs-common - Qbs static files
qbs-dev - Qbs development files
qbs-doc - Qbs documentation
qbs-doc-html - Qbs HTML documentation
qbs-examples - Qbs examples
Closes: 831182
Changes:
qbs (1.5.2+dfsg-1) unstable; urgency=medium
.
[ Adam Majer ]
* Remove /usr/include from INCLUDEPATH list of installed
.pri file. Adding this default included path causes FTBFS
for software using qbs with GCC 6 (fix_ftbfs_gcc6.diff)
(closes: #831182)
.
[ Dmitry Shachnev ]
* New upstream release.
* Drop kfreebsd.diff, a similar patch was applied upstream.
* Avoid using the Qt Build Suite term, following upstream.
Checksums-Sha1:
59488d11d47d32f9d9141ab3f462a83b8c5c5e1b 2443 qbs_1.5.2+dfsg-1.dsc
897c46ffd628d7e7d2176c8b4cd1ad10a0215b45 878121 qbs_1.5.2+dfsg.orig.tar.gz
cc105cf3477843bb32c4deed0f50002ac03406ee 15904 qbs_1.5.2+dfsg-1.debian.tar.xz
Checksums-Sha256:
65ca3263687ec487b9281657a2a774c4e6717c4f29fb606bdbb9c2c08c41f183 2443 qbs_1.5.2+dfsg-1.dsc
263276552db8e7c01b3f7ae45140593bc664d2a7f220e835e0483fc1bdb672cb 878121 qbs_1.5.2+dfsg.orig.tar.gz
09a92d048a00cfdf15e4ffb4e1b62335722cba3764b8f13a6b46f9867f3d4e59 15904 qbs_1.5.2+dfsg-1.debian.tar.xz
Files:
3cf35e2111dcefb3f5fb1771fd4fd4b1 2443 devel optional qbs_1.5.2+dfsg-1.dsc
3ef54a24c6f794f87a99ba926776cd19 878121 devel optional qbs_1.5.2+dfsg.orig.tar.gz
9984c4505530f62cd32ef385eb9718bd 15904 devel optional qbs_1.5.2+dfsg-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIEBAEBAgAGBQJXn8g4AAoJEIZFCLAbJnnPUZMPPjMwEOi1ps5XKVbJtJPCctFW
PSAI7wJqLKysGoJsKU7dtF8zJGOfj8RB5lKmxLRrcSwY3Q4NLdykGVu8djsUWGdb
cY7ju7Xh4wEp5ZQ9lVRuqioL4g35hQQSqs7sn/1+RIR7Hr3NYBgcntV0g/lIEnFp
YAzGMKRInqVM3NGTybGNgLcD5LeUPk7Tn0HT2cgEen924/iLFG9sBYF/RB51hZp6
c7PPXiSQWGLIkK+R1OZyQNwA3g/b9/2PfqZl00pF6H8QRbBX6VTq4T63nyXCW4C0
tfTcERQkLFy1GwKk1ZQ1dF4aWCrUhI7Ec++zqoTUwR4g/OqbYXBuivY31oJnLNvK
9YyeAk8ty2kZ6bTfFr+l13BT0Sp9Bwe9+V0KFi7hyIyBss3001PG8ftjyaKlKKf/
Ete4rMPGIZrrl+JcSeDzM1Mbt5jEczTURQubczsuYAp+BzK+tEjN0OJeR/mrzjU8
twNvL1mRirOgf8Zalunq2xUWfDzL9TYfs5BU07R6gaPRHMpCzmVpF/hbxPwU/XPl
AEyv+QjqmM58Q5RTMKOV7OxGCkNfQJMOLdWfZszQxPmp482TGOoj5Bdzs2/4zuEt
IWUpgMNGyMwQe1nJdMrekyWK1620uVBtgi8DUntonaPduiyvatVS
=K6ys
-----END PGP SIGNATURE-----
Reply to: