On Fri, Aug 23, 2019 at 04:44:07PM -0400, Gabriel Filion wrote: > Hello! > > Thanks a bunch for the fix to the > libtrapperkeeper-webserver-jetty9-clojure package. > > I'm wondering though why the package hasn't migrated to testing (and > stable) yet. This info is completely uninformative about the situation: > > https://qa.debian.org/excuses.php?package=trapperkeeper-webserver-jetty9-clojure > > I was under the impression that packages uploaded to unstable were > migrated automatically to testing after a while.. was there maybe some > delays imposed since this was uploaded not long after buster's release? > > .. also the package in buster is still buggy, so I guess at this point > it would be nice to see a push to stable to fix the issue > > Cheers, and thanks again for your work on this, I really appreciate what > you do!
Hi, From the PTS page [1], I see the excuse as: testing migrations excuses: - 38 days old (5 needed) - Piuparts tested OK - https://piuparts.debian.org/sid/source/t/trapperkeeper-webserver-jetty9-clojure.html - Checking build-dependency on amd64 - Not built on buildd: arch all binaries uploaded by [email protected] - Not considered Starting with buster, uploads must be source only and the binary packages built on the buildds in order to migrate to testing. I'll have a look at uploading a source package. Cheers, tony [1] https://tracker.debian.org/pkg/trapperkeeper-webserver-jetty9-clojure
signature.asc
Description: PGP signature
