[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#942874: marked as done (cross-gcc: Please make it source-only when making new uploads)

Your message dated Mon, 18 Nov 2019 06:19:34 +0000
with message-id <E1iWaNq-000HhW-Hg@fasolo.debian.org>
and subject line Bug#942874: fixed in cross-gcc 235
has caused the Debian Bug report #942874,
regarding cross-gcc: Please make it source-only when making new uploads
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.)


-- 
942874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942874
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: cross-gcc
Version: 234
Severity: normal
X-Debbugs-CC: dkogan@debian.org

Dear cross-gcc maintainer,

I noticed that all recent uploads of package cross-gcc were made with
maintainer-built binary packages, according to history information in 
https://tracker.debian.org/pkg/cross-gcc page.

As previously announced in 
https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html , britney
will reject migration when there are maintainer-built binary packages in the
upload. As a result, all cross-gcc builds after version 230 did not migrate to
testing. Please refer to https://wiki.debian.org/SourceOnlyUpload on how to
generate source-only uploads and make a source-only one with next upload.

Best,
Boyuan Yang

--- End Message ---
--- Begin Message --- 
Source: cross-gcc
Source-Version: 235

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

Debian distribution maintenance software
pp.
Dima Kogan <dima@secretsauce.net> (supplier of updated cross-gcc 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 17 Nov 2019 21:51:03 -0800
Source: cross-gcc
Binary: cross-gcc-dev
Architecture: source
Version: 235
Distribution: unstable
Urgency: medium
Maintainer: Debian Cross-Toolchain Team <debian-toolchain@lists.debian.org>
Changed-By: Dima Kogan <dima@secretsauce.net>
Description:
 cross-gcc-dev - Tools for building cross-compilers and cross-compiler packages
Closes: 942874
Changes:
 cross-gcc (235) unstable; urgency=medium
 .
   * rebuild for 9.2.1-19 (Closes: #942874)
   * rebuild for 8.3.0-24
Checksums-Sha1:
 88a85087a07de20209e723f82f2ff45e8571674e 1641 cross-gcc_235.dsc
 76f7798f86595344c3010f6d0ec1930c7f9c07ae 32128 cross-gcc_235.tar.xz
 c4d6eb4ebb58c584a54566fb8f8cf650a8ab9369 5996 cross-gcc_235_amd64.buildinfo
Checksums-Sha256:
 567434600007b78393bee4f9130f054000b6ca871c9a8eee53bfbc4897c95f0d 1641 cross-gcc_235.dsc
 f4f21774362c738a9f50c051784011828cc7ca4aeea66277779cef3cd536db46 32128 cross-gcc_235.tar.xz
 8b6c1336ad895f492ecc1241686b900e1838bcb3287430b682738988bfaebf23 5996 cross-gcc_235_amd64.buildinfo
Files:
 fb41a125c6516e9198070cac9ff225d5 1641 devel extra cross-gcc_235.dsc
 0582be4a4aa0926a8e4d73a2a1af2ab2 32128 devel extra cross-gcc_235.tar.xz
 8b57b27a504293807f9c78200ac992d1 5996 devel extra cross-gcc_235_amd64.buildinfo

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

iQIzBAEBCgAdFiEEdRwTXcLOAUM4CFTz7WO2ElodFWEFAl3SM28ACgkQ7WO2Elod
FWFLtw//XBxgCKmEz/Uu057l1pzTN2zdrdg6PnxjvatuVIzMS+7u+jFa3VSGjpqE
gIddJxa+qHPQ9b8Q+3HJ0zin1KH08osvQFnP+9N+ol57Q+l4rV1E2WCDt2evz3dw
UeM+hLu8T2fX1BRl7U0fSIdnrIDKuL/9SaOiz4evOyVPzQjqul+rmTw8O9aafD2E
UX0dTjmj1GgjqOVVOE+V9Whz9UjRvL9yjgaqhcz5iI4CMI/2MNoYy3pdeJMRbFUL
zDNQS50FNCYUCHwzTW0PI5sJBNEkPIBnhXP/fmbyy1kwGjCyVbdYqevomkknX7XC
2Fbb7epvxV3BUbQqxv9WQBFeczb+6EoXOWQGudfbHBASkjpeYVP/W9mdsjTl1wzt
6vSnS4jDSyV4AMucgyXtNVPLdLMmeZfw5wtuOh93wnbWq1Z1Y/Xrp/+QJRfUzAXs
c7xdQbxPcySuM3sLzDo/YGCNQN/PdtLrqX1+/fA67Adzrga11udynuHnENy6URnF
i2WZ3EUpKxfwrYrCLY8N7RUciMYQK/qax5ylDTXXZh8x20tBwg1tZYnaYAdcnUaz
RrEGbbFw7bxLkgqeedJylc1QegtUG/ZaT+hXlJUoWCDLZ8t0UlDVVDljXuXdBZvo
LfB6WAfYoss6S5KQ77iA58MJIkrQXCSgWq114FpvBxjCEaRY0kQ=
=J7fV
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: