Your message dated Wed, 08 Jan 2025 00:55:17 +0000
with message-id <[email protected]>
and subject line Bug#1046734: fixed in libamplsolver 0~20190702-4
has caused the Debian Bug report #1046734,
regarding libamplsolver: 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.)
--
1046734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046734
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libamplsolver
Version: 0~20190702-2
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 libamplsolver
> dpkg-buildpackage: info: source version 0~20190702-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Andreas Tille <[email protected]>
> dpkg-source --before-build .
> debian/rules clean
> dh clean
> dh_auto_clean
> make -j8 distclean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> rm -rf sys.*.*
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_clean
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building libamplsolver using existing
> ./libamplsolver_0~20190702.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
> libamplsolver-0~20190702/makefile
> dpkg-source: error: aborting due to unexpected upstream changes, see
> /tmp/libamplsolver_0~20190702-2.diff.lkAulS
> 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/libamplsolver_0~20190702-2_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: libamplsolver
Source-Version: 0~20190702-4
Done: Étienne Mollier <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libamplsolver, 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.
Étienne Mollier <[email protected]> (supplier of updated libamplsolver
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: Wed, 08 Jan 2025 00:09:30 +0100
Source: libamplsolver
Architecture: source
Version: 0~20190702-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
<[email protected]>
Changed-By: Étienne Mollier <[email protected]>
Closes: 1046734 1091063
Changes:
libamplsolver (0~20190702-4) unstable; urgency=medium
.
* Team upload.
* d/clean: cleanup the makefile. (Closes: #1046734)
* d/patches/*: normalize last-update timestamps.
* d/rules: force non parallel builds.
arith.h and propbably other files are required at more places than
encoded in upstream makefile. Since make 4.4, this produces
consistent build failures. Until the missing specifications are
identified and fixed in upstream makefile, dropping the parallelisme
is a good enough option. (Closes: #1091063)
Checksums-Sha1:
93ab9127d2842bf6bd38ca2f16bb99b8d80d0167 2238 libamplsolver_0~20190702-4.dsc
d2ddf8ff0179eb92a3d51a66008016ada90ee722 4412
libamplsolver_0~20190702-4.debian.tar.xz
Checksums-Sha256:
33df1660f8f374c8ce79e0e88deb053570609d5148362c066f3a5cbc1e9d08e3 2238
libamplsolver_0~20190702-4.dsc
2fca56dd220dfc0208b0289ee75db2f576f79f458f3acf77cd8defc91b28dfc2 4412
libamplsolver_0~20190702-4.debian.tar.xz
Files:
b045266e5c8777b08b54dacb0b0d5034 2238 science optional
libamplsolver_0~20190702-4.dsc
3dc82734909454384ca6ec3d3d6fd7bc 4412 science optional
libamplsolver_0~20190702-4.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmd9tWYUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdoBbw/9EIsEIriQkdOAGhG61I9haB/liNwU
Uc3rZEgQ5S5qX8lWkSYH5VC4BnxRUNYczwGVYjvqyV5otmmB+BEiXWjbsgX4Yj7W
Ud6AvVkTGHOMysReKxM+MnOULpEzFlhsJw1aJJGYfEoTOmpjJ7FUQlzub6IUd+lZ
cXFQ7Pznqm/s98kyZFCgI2v8Di2G6djAQmWrsHOiEe3HRfYorCNQIC3qKm/bigVl
YjBWpeumdqTt4YhgsV5viMP9rP+E14+tMdwXv0kzFCQeIzMNpPVh2CacyCdL/eZy
++DlclUZNkE0w0b+b2ATgVh4Q/EASyjgnN8qDUYrwTXanQcgTyMFnYXlFb0AuMUH
cLnM5v69WnoFHCvztxoCh9tmOBC/Uav7LeQ4SfbyTgJIDziw1HLd+EdtJuB5Bk4F
AjiO2/WUGx5DrEX/rRM+9BTZ7ejvkqdAPTPJ1KXvydXoAQHW1cteefXhYAgzHAXs
g/z5273cp03XbUa/YrTvwmvdkKEJUDnUD68HSR9KQo4t9y6ywGUsZ1lwgyoBA0RK
G9tgGB3rtz2QzySqv3x18E3pNwc4hK29n9Ez5Lwt1gs7NaW//Y/qlYrLYj5RmjQc
g6UlpylL+8jzlXBQulFX6lppJSL1iy7NvVpHP0XnVJS8rMZZ/uGbPE9LCpCQxWgz
3gNoDfiJgQ/KRxM=
=O6/L
-----END PGP SIGNATURE-----
pgpduyaB4SvVD.pgp
Description: PGP signature
--- End Message ---
