Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: transition
Hello, this is not a regular transition because I screwed up: The upload of http-parser (soname 2.7.1) last night hit unstable instead of experimental as suggested by the transition wiki, and also as intended. My primary objective is to keep the damage as low as possible. So I'm asking for your advice how to proceed. I can revert the upload although I'd prefer to go forward. Before uploading, I already had identified the following build dependencies: cargo_0.22.0-1~exp1 jabberd2_2.6.1-1 libgit2_0.26.0+dfsg.1-1.1 ocserv_0.11.9-1 purple-matrix_0.0.0+git20170530-1 ruby-http-parser.rb_0.6.0-3 sssd_1.15.3-3 tcpflow_1.4.5+repack1-4 With ruby-http-parser.rb as exception, all these built fine. I've filed #881627 to discuss the failing one. Additionally, I've filed an RC bug #881628 against http-parser to prevent testing migration until things are sorted out. Also as a measure against another failure of that kind I've switched to dput-ng that warns about a Distribution: discrepancy between .changes and debian/changelog. That would have prevented the current mess. For completeness, here is what reportbug suggested about the transition: Ben file: title = "http-parser"; is_affected = .depends ~ "libhttp-parser2.1" | .depends ~ "libhttp-parser2.7.1"; is_good = .depends ~ "libhttp-parser2.7.1"; is_bad = .depends ~ "libhttp-parser2.1"; Sorry for the hazzle, and looking forward for a solution everybody can live with. Christoph
signature.asc
Description: Digital signature