The 2ping package is in an odd state at the moment. For background, on Saturday morning (UTC) I made two source-only uploads, 4.0-1 then 4.0-2, which exposed some issues (a dependency problem and problem with the unittest suite, respectively). The latter was corrected upstream and I uploaded 4.0.1-1, which was accepted and 2ping_4.0.1-1_all.deb successfully built[0].
However, the binary package is not yet in sid[1], though the source
package is[2]. PTS[3] suggests it's in NEW, but NEW[4] has no mention
of it. removals.txt[5] has an entry for removing the older 3.2.1-1 from
unstable ("no longer built from source, no reverse dependencies"),
presumably because the source package had been updated but not the
binary yet, and I think that may have something to do with the current
state. But I have no idea where 2ping_4.0.1-1_all.deb ended up going.
[0] https://buildd.debian.org/status/package.php?p=2ping&suite=sid
[1] https://packages.debian.org/sid/2ping
[2] https://packages.debian.org/source/sid/2ping
[3] https://packages.qa.debian.org/2/2ping.html
[4] https://ftp-master.debian.org/new.html
[5] https://ftp-master.debian.org/removals.txt
signature.asc
Description: OpenPGP digital signature
