Your message dated Tue, 02 Jun 2020 02:37:46 +0000
with message-id <e1jfwoe-000fdw...@fasolo.debian.org>
and subject line Bug#960872: fixed in gtkgl2 2.1.0-0.3
has caused the Debian Bug report #960872,
regarding gtkgl2: autopkgtest failure: cc: not found
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 ow...@bugs.debian.org
immediately.)


-- 
960872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtkgl2
Version: 2.1.0-0.1
X-Debbugs-CC: debian...@lists.debian.org, nico...@debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s), Nicolas,

With a recent upload of gtkgl2 an autopkgtest was added, great. However,
it fails. I copied some of the output at the bottom of this report.
There seems to be missing a test dependency.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=gtkgl2

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gtkgl2/5240227/log.gz

autopkgtest [21:18:39]: test link-basic-example: [-----------------------
/tmp/autopkgtest-lxc.0adei5av/downtmp/build.N6w/src/debian/tests/link-basic-example:
9: cc: not found
autopkgtest [21:18:39]: test link-basic-example: -----------------------]

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: gtkgl2
Source-Version: 2.1.0-0.3
Done: Nicolas Boulenguez <nico...@debian.org>

We believe that the bug you reported is fixed in the latest version of
gtkgl2, 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 960...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nicolas Boulenguez <nico...@debian.org> (supplier of updated gtkgl2 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 18 May 2020 00:31:57 +0000
Source: gtkgl2
Architecture: source
Version: 2.1.0-0.3
Distribution: unstable
Urgency: medium
Maintainer: Sam Hocevar <s...@debian.org>
Changed-By: Nicolas Boulenguez <nico...@debian.org>
Closes: 960872
Changes:
 gtkgl2 (2.1.0-0.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * autopkgtest: call gcc instead of cc.  Closes: #960872.
   * Use substitution variables to restrict patterns in debhelper config files.
Checksums-Sha1:
 088d5f8860f8bbcd9e33c23b2a3871f1e4d84180 1904 gtkgl2_2.1.0-0.3.dsc
 3816ea3c33cc98306ca35bb1e89d0ea152111b97 6740 gtkgl2_2.1.0-0.3.debian.tar.xz
Checksums-Sha256:
 7fabb978b746e69f002575cb67cc836e987478a1a69dfce70b4417b7a33aee52 1904 
gtkgl2_2.1.0-0.3.dsc
 0f62424a248d619bf5835e12e25f4bdb4753166977251dae290533b9fff19164 6740 
gtkgl2_2.1.0-0.3.debian.tar.xz
Files:
 ea16ab8c25f583dad61ed798ce006c2a 1904 devel optional gtkgl2_2.1.0-0.3.dsc
 65919dcc6aa2b7a5de6929753bae5b5a 6740 devel optional 
gtkgl2_2.1.0-0.3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAl7B3bITHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jfluD/9QBVvbM5YtQj/u1a/nduuQKR0lyBqq
2Z1HybNBXDUsGXBIQKLzh1xDPf/F9lgMpI/EfKwmXBBZqyEdv0Q27vl/8G0BBMr9
oANpXBdy0Q3KGL2zzXqGCrC2VFFYHR+vTqs2XAohsESwq9kklINGPRUgluKNcBlk
Ea0mKbP6wcV51zcwjJDjKUelxVl85nxv51v/CsLBmQhOEh+zfKKDmfAYzg3H7hlS
20B2Q5QuiXPdZQJBPkQdT+KtnoOLLeZlZkZCeC0Z0zyTTY3yEWZ+7M2BxeYn/0XW
YAlZDQtiA1bXQfW3wwsQILMcVdObaGXIX16vS7o9goKQdpnDZTC0d+i2Kc9sOzXw
4Uh+oIH5XVyy96mWjaBfgQHMU6Ey0HZLVBKMt/7ZQQj0gSKGayRVmHxzJ9QFF7w3
7FAT63OXVG0PSjtUz08xLB47cx1JhPa9KeKgSd/YF23hEqpvFfI1NRVgh01Eqw+s
4WX7casWY++O1sldCIXPNwOB7IIYlGCMMYtuLSiL3M7FLRpFUpZ14+YMs+VWxKRz
juOvj9HbeeSVDobeAzGRcQyUuEe52jSyhuQWCIxKXS7rZnM0r/NAimEw8knhQuSN
Gv/6Ss+bE/3Ru7+m8wdN2sFYaAXrn22agiVfY/XSH0+vAoecAo9uixseaVmr8OUj
SWssofh7WaJf3g==
=X+YH
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to