Your message dated Fri, 28 Aug 2026 15:18:43 +0000
with message-id <[email protected]>
and subject line Bug#1048867: fixed in lomiri-api 0.3.2-2
has caused the Debian Bug report #1048867,
regarding lomiri-api: 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.)
--
1048867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1048867
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: lomiri-api
Version: 0.2.1-1
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 lomiri-api
> dpkg-buildpackage: info: source version 0.2.1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Marius Gripsgard
> <[email protected]>
> dpkg-source --before-build .
> debian/rules clean
> dh clean --with pkgkde_symbolshelper
> dh_auto_clean
> debian/rules override_dh_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> rm -Rfv /<<PKGBUILDDIR>>/debian/test-home/
> removed directory '/<<PKGBUILDDIR>>/debian/test-home/.local/share'
> removed directory '/<<PKGBUILDDIR>>/debian/test-home/.local'
> removed directory '/<<PKGBUILDDIR>>/debian/test-home/'
> dh_clean
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building lomiri-api using existing
> ./lomiri-api_0.2.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
> lomiri-api-0.2.1/results.txt
> dpkg-source: error: aborting due to unexpected upstream changes, see
> /tmp/lomiri-api_0.2.1-1.diff.kdUmOo
> 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/lomiri-api_0.2.1-1_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: lomiri-api
Source-Version: 0.3.2-2
Done: Jeremy Bícha <[email protected]>
We believe that the bug you reported is fixed in the latest version of
lomiri-api, 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.
Jeremy Bícha <[email protected]> (supplier of updated lomiri-api 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: Fri, 28 Aug 2026 16:45:35 +0200
Source: lomiri-api
Built-For-Profiles: derivative.ubuntu noudeb
Architecture: source
Version: 0.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian UBports Team <[email protected]>
Changed-By: Jeremy Bícha <[email protected]>
Closes: 1048867
Changes:
lomiri-api (0.3.2-2) unstable; urgency=medium
.
* Team upload
* Add debian/clean to remove results.txt (Closes: #1048867)
* Use dh_installdocs to install NEWS
Checksums-Sha1:
b9117cd9d724c3126704957017def8ef2cd98ba1 2963 lomiri-api_0.3.2-2.dsc
30ea131774ad7f51fff990cf53ab40bd13ee8c3b 13348 lomiri-api_0.3.2-2.debian.tar.xz
83b5aa60dfc970eb93b709a0df60432722d782c0 13878
lomiri-api_0.3.2-2_source.buildinfo
Checksums-Sha256:
2aff757f96fc951c91ac98d8dcf6c411d1b3edd4025568bb661c668f0206a095 2963
lomiri-api_0.3.2-2.dsc
0443bb965125fa69f5394116c69fc2bf581f029fd2e65dd3bc686af96daa6187 13348
lomiri-api_0.3.2-2.debian.tar.xz
fcc1092db025b57868b5a56d191d5847f38448eed64ce668642d78d50aef6b50 13878
lomiri-api_0.3.2-2_source.buildinfo
Files:
8bb96ca3d298ae213d3169d36785b125 2963 libs optional lomiri-api_0.3.2-2.dsc
3e35b0f804a2c67d46dece10ba0f2fa3 13348 libs optional
lomiri-api_0.3.2-2.debian.tar.xz
dbea953e5da8eb0855ee63015541ef19 13878 libs optional
lomiri-api_0.3.2-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmqRnycACgkQ5mx3Wuv+
bH0bCBAAzh0WK9PpbSWT8chHFoxFYrb73uoAGrQ33lnE1QYe54kf1M7jepKNTu3m
ot27JKNvQT604ByaORsSfbmJUTH60t2HXsWuD/d2dP67kcDhPDhj4n+wvQFWFAUo
ctUwfaaxv2FLaiXZRlp9/BUUe7Zd+88ceIe+lhAQsM44GujVTY2RCY7dAebnIvyL
xeo4lLVTeY9ceh8+GMou+CHIhTUYBHqDDqLOoDp2Fd6jGLVUYzwxBdzBn+fHATAn
YPHqJqFR/2YKNo7An+28Mwl0WNEJLduuj5rtwzzw2uHP0G6dzaeoTzIRwNfZCTVs
Xn47PhPtV8nLfgnfjikHgEO1Ur5DEpnj05qrgCw1Av7eedSuH1h2wtB00j+jIC3o
pMFQj6ZtIr899CrAh8SQClDQffndWdlBxsywON4dSQi5A+G4QjhEylORqv79swNh
lUmVrtnCkoZXR/+SRR4HS++D/+uSYxKOxTK/D6HvMcsG2MEULZFfmAFSB/05woh9
63Z2BzWD5bx6FfpXup5rFZKHobeOJ9gSFgfltkXT8SAkCA2Tzr8Pi6oVouCcGLvd
y/IwRKTXUYTes0EYrSqPs3m9bilGGZBHiLIQKPfCMg1GDsDmPsrKHyVwXIcEkNZd
QB/cPDLpUDRrxiiMSV95dW21viPdjFGTeu7LUWNrMTRc2X4lF68=
=p3BD
-----END PGP SIGNATURE-----
pgpfQa6UQE_9r.pgp
Description: PGP signature
--- End Message ---
