Your message dated Fri, 15 May 2020 18:04:26 +0000
with message-id <e1jzeh8-000hkt...@fasolo.debian.org>
and subject line Bug#960054: fixed in reactphp-socket 1.4.0-1
has caused the Debian Bug report #960054,
regarding src:reactphp-socket: fails to migrate to testing for too long:
arch:all uploaded
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.)
--
960054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: reactphp-socket
Version: 1.1.0-1
Severity: serious
Control: close -1 1.3.0-1
Tags: sid bullseye pending
User: release.debian....@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:reactphp-socket in its current version in unstable has been trying
to migrate for 60 days [2]. Hence, I am filing this bug.
If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.
This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.
I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.
Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.
Paul
[1] https://lists.debian.org/debian-devel-announce/2020/02/msg00005.html
[2] https://qa.debian.org/excuses.php?package=reactphp-socket
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: reactphp-socket
Source-Version: 1.4.0-1
Done: Thorsten Glaser <t...@mirbsd.de>
We believe that the bug you reported is fixed in the latest version of
reactphp-socket, 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.
Thorsten Glaser <t...@mirbsd.de> (supplier of updated reactphp-socket 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: SHA384
Format: 1.8
Date: Fri, 15 May 2020 19:48:17 +0200
Source: reactphp-socket
Architecture: source
Version: 1.4.0-1
Distribution: unstable
Urgency: low
Maintainer: Teckids Debian Task Force <t...@lists.teckids.org>
Changed-By: Thorsten Glaser <t...@mirbsd.de>
Closes: 960054
Changes:
reactphp-socket (1.4.0-1) unstable; urgency=low
.
* (Closes: #960054)
* New upstream release
* Bump debhelper
* d/p/fix_deps.patch: redo for new version
* Update lintian overrides; add UMEGAYA and R³:no
Checksums-Sha1:
ead99607355e2651b0daa7ba6fd1e4506f07697d 2068 reactphp-socket_1.4.0-1.dsc
20b0edb57f9a3f6a5e13573bbed4a9d213340b5c 35117
reactphp-socket_1.4.0.orig.tar.gz
1385c3dd81ddd0eb26ca87c352b670913469eca4 3168
reactphp-socket_1.4.0-1.debian.tar.xz
Checksums-Sha256:
6551faa55ecc548e7ced44078bde6da4d9d6829f4f8c023969723360c84bac77 2068
reactphp-socket_1.4.0-1.dsc
37c25ac33bcfd11acdbc5c3baba47542c24b3e1030d16a62aedf78ddf419492a 35117
reactphp-socket_1.4.0.orig.tar.gz
4ffebfb11c7949b8362e213ff84936f3daae508d9c77842124e12af8b057f3c7 3168
reactphp-socket_1.4.0-1.debian.tar.xz
Files:
b1b25244b5d628ae61b2cd4a4ae77434 2068 php optional reactphp-socket_1.4.0-1.dsc
303062a6bc3c589619edf10a6d4c9100 35117 php optional
reactphp-socket_1.4.0.orig.tar.gz
0e1d97decdbd27c116d141d569915ff1 3168 php optional
reactphp-socket_1.4.0-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (MirBSD)
Comment: ☃ ЦΤℱ—８ ☕☂☄
iQIcBAEBCQAGBQJevtbGAAoJEHa1NLLpkAfgJnoP/A+Azgfe+L4GMyBJ3EvIzmvC
/lqSuph40VmmoblJ5tpKDbwCDPZwjA63AtN1WazOOGyC8NuAb32XBm6Hxi2UR6Xg
cN1NspAbypr5PsEBPlfS9xbd2TxcWVDtJO6FSHFdMqqoyLi0xh2KAvyDd5HIM7mm
Sj04oRTooA7Gkfgxqv0GlUxDsRaMwzmEQ0a3EOHrAjWV7cUD63AXIIo09mikC/71
MBUyh80u5KpmwjKJoVD0X0NOeQ9Ajof99HbTVu6UfgoxakdQDTazx7DPFyL4o0F0
gxwyzI9lfus9ar0IAximX8xnxiRZ0RW2S2YmnMxXvK3A2sq6rVqAm5JjgHXyHPMU
vjXNaszje+f2/J7iSJdCvSECsAd+dP84JYMrRXuNDEnltDeSbPw41Jg/ifgv2l9x
8r8niXnAgRNUmdkm91Xj1qlIPpLHiMN5wpidy7Q1lj6krJNnfPBhFVmk+/IgsfeL
YaOrvQNixycBPJO/6I+SGGSBxt6/SyT3eIVNX+GJopjVkjNYNyqby/iKbB8dCetN
DCROQzkUTv2Au/swxu8R7TbsmOFMtZun7EoNY91czac2BPWFfwka0bo0oN/T0nW2
ogvv/tlyofBKYFqPxWdl3PWrMnpmVyHamum1Hp1j7mPEgDKkKeB1k010+MrIxxIg
fPoeKBnaphHIuROi7mRK
=lb3a
-----END PGP SIGNATURE-----
--- End Message ---
