Your message dated Sun, 16 Mar 2025 17:20:13 +0000
with message-id <[email protected]>
and subject line Bug#1049012: fixed in mir 2.20.0-3
has caused the Debian Bug report #1049012,
regarding mir: Fails to build source after successful build
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.)
--
1049012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049012
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mir
Version: 2.14.1-4
Severity: minor
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: [email protected]
Usertags: qa-doublebuild
Hi,
This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).
This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.
More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild
Relevant part of the build log:
> cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env
> -us -uc -rfakeroot -S
> --------------------------------------------------------------------------------------------------------------
>
> dpkg-buildpackage: info: source package mir
> dpkg-buildpackage: info: source version 2.14.1-4
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Marius Gripsgard
> <[email protected]>
> dpkg-source --before-build .
> debian/rules clean
> COMMON_CONFIGURE_OPTIONS:
> -DCMAKE_INSTALL_LIBEXECDIR="lib/x86_64-linux-gnu/mir"
> -DMIR_BUILD_INTERPROCESS_TESTS=OFF -DMIR_FATAL_COMPILE_WARNINGS=OFF
> -DMIR_LINK_TIME_OPTIMIZATION=ON -DMIR_LINK_TIME_OPTIMIZATION=ON
> -DMIR_RUN_WLCS_TESTS=OFF -DMIR_USE_LD=ld
> DEB_BUILD_MAINT_OPTIONS: hardening=+all
> dh clean -Bbuild-amd64 --with pkgkde_symbolshelper
> dh_auto_clean -O-Bbuild-amd64
> dh_clean -O-Bbuild-amd64
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building mir using existing ./mir_2.14.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
> mir-2.14.1/include/miral/miral/version.h
> mir-2.14.1/include/server/mir/version.h
> dpkg-source: error: aborting due to unexpected upstream changes, see
> /tmp/mir_2.14.1-4.diff.DIVAWK
> dpkg-source: info: Hint: make sure the version in debian/changelog matches
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
>
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage
> --sanitize-env -us -uc -rfakeroot -S' failed to run.
The full build log is available from:
http://qa-logs.debian.net/2023/08/13/mir_2.14.1-4_unstable.log
If you reassign this bug to another package, please mark 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: mir
Source-Version: 2.20.0-3
Done: Mike Gabriel <[email protected]>
We believe that the bug you reported is fixed in the latest version of
mir, 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.
Mike Gabriel <[email protected]> (supplier of updated mir 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: SHA256
Format: 1.8
Date: Sun, 16 Mar 2025 17:41:41 +0100
Source: mir
Architecture: source
Version: 2.20.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Mir Team <[email protected]>
Changed-By: Mike Gabriel <[email protected]>
Closes: 1049012
Changes:
mir (2.20.0-3) unstable; urgency=medium
.
* debian/libmiroil7.symbols.armhf:
+ Also drop armhf-specific libmiroil7 symbols. This fixes build failure on
the armhf architecture.
* debian/rules:
+ Remove build-generated version.h include files during dh_auto_clean.
(Closes: #1049012).
Checksums-Sha1:
d988e1bdcab4d059a6cc9bc328ec28305fa9424e 6801 mir_2.20.0-3.dsc
4dfbd83e2393ea48a3f40891c508aad7ed866760 38600 mir_2.20.0-3.debian.tar.xz
211cb5a944c7a5c45aedb8ad959b0404b5624a84 17837 mir_2.20.0-3_source.buildinfo
Checksums-Sha256:
d3e8ff7495cd9e97a6594610be1ff6afb1cfcf6b58dc35acf77e655b0ea42211 6801
mir_2.20.0-3.dsc
5a76b35f621e8f68164ee67b21a4e9be3ad59fdd37e6f945b78ba998e9897e21 38600
mir_2.20.0-3.debian.tar.xz
5d01b253f7e6fbd45b9be46377842fc169f7f559cbddbcc6d9da0ef50bddd5b7 17837
mir_2.20.0-3_source.buildinfo
Files:
94b174fcea40903fe39ad1cb47e5c7f1 6801 x11 optional mir_2.20.0-3.dsc
61a79dc02d1dc530f49140dba1c223f2 38600 x11 optional mir_2.20.0-3.debian.tar.xz
842565dc2a66ffc9e02736b55fccd10f 17837 x11 optional
mir_2.20.0-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmfXBJkVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxeokP/RDo6G1Qy/76UZ7rBay4T1bHWisZ
l6rBfqnPat0XQtRWvJ+x3Kz4jnQ2vAlhFP6CyNg1RZPl010q/sbfjriURmNZ0H1W
y1xcS9qPKqBNisDjG2BTIOgCWH4BCuoK74qat59bcYd/ItkLuBUKpvbXBkpCwTkX
n/JzMxafrEySZGEnJxWDf8ebgzsEpMnfIaoMPdmt+7I7rFgKomN4d3w+hG2H/qD2
iKvjTtsdk4WgIhBmFYUAQ93o+auPLRCm1gGIzuo8Wk9GYVeZa2LgArZLKPX6c0IK
XqneFSsTqqSaHrxWbAmfxJusIQyoWOiQaAwu3phIJx7ykrwrIrjLJt6Vy2FMlFBE
xPyec7+1UXU1b056TdfAAGCc/9wp/1OSW7CE0xiVTFhPjkDqgKIhwc60GjJfwVaQ
mGzcbLEuY3cuIkyit1pBmfdAdjOlUQw4ms5E6xZMxVkHw6c1V7qiVQHkW+uZX86G
rJTQ7IXUve82Xf5koYsL1jEeM1uyTg79612nmkfKRkkJ+egZRvhz9SDsvVv2GrJi
20oGTSRltyims8181IlidTRLpKG7ELkHhRzxIM4to2pMSQHrwuj6s8v3+ETSra/D
ST7++HV2rAp+yzAB9IEuMV7R3XcjUJjcTqaxpFKfDYPjrdcUm11WrsPgVyT2va4x
RYOMVfyBl/YT7W9g
=BoTu
-----END PGP SIGNATURE-----
pgppTI4TZcez9.pgp
Description: PGP signature
--- End Message ---
