Bug#921421: marked as done (gcc-8-cross-mipsen: FTBFS in sid (Version in Debian Archive >= Version in debian/changelog))
Your message dated Thu, 28 Feb 2019 18:13:47 +0100
with message-id <[🔎] 91459d68-7e96-16c8-7867-7dcbb4699e04@debian.org>
and subject line c-t-b-mipsen now built
has caused the Debian Bug report #921421,
regarding gcc-8-cross-mipsen: FTBFS in sid (Version in Debian Archive >= Version in debian/changelog)
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 owner@bugs.debian.org
immediately.)
--
921421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921421
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-8-cross-mipsen
Version: 2~c1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
--------------------------------------------------------------------------------
dpkg-buildpackage
-----------------
dpkg-buildpackage: info: source package gcc-8-cross-mipsen
dpkg-buildpackage: info: source version 2~c1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by YunQiang Su <syq@debian.org>
dpkg-source --before-build .
fakeroot debian/rules clean
gcc: 8.2.0-16 / 8.2.0-16cross1
old gcc version: 8.2.0-16 / 1
debian/rules:68: *** Version in Debian Archive >= Version in debian/changelog. Stop.
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2
--------------------------------------------------------------------------------
The same thing happens here:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/gcc-8-cross-mipsen_2~c1.rbuild.log.gz
Simple question: It is not possible to use a versioned Build-Depends for this?
(For QA purposes, a package with unsatisfiable build-depends is a lot
easier to track than this).
Thanks.
--- End Message ---
--- Begin Message ---
Version: 2~c2
c-t-b-mipsen now built.
--- End Message ---
Reply to: