On 06/02/2015 10:29 PM, Johannes Schauer wrote: > Hi, > > Quoting Miguel Landaeta (2015-06-02 21:54:29) >> Thanks for the report, we are aware of the issue and we are waiting for >> FTPmaster jnr-posix approval to solve this bug and others. > > thanks for the clarification. > > Could you next time please hold off on doing such an upload until the reverse > dependencies land in unstable? Having a source package that does not compile > and a binary package that cannot be installed does not help anybody and on the > contrary can even disrupt existing processes (as it happened with this one > because jython is part of the transitive essential package set). I'd rather > expect such an early upload happen to experimental instead. > > Thanks! > > cheers, josch
Hello Josch, First, I'm responsible for uploading jython; Miguel and Tim Potter and I and several other members of the Java Team are trying to get a modern version of JRuby into Debian, which requires a number of transitions. Second, the short answer to your question is "yes." I should have left the package in experimental (it was there for several months), but I thought that jnr-posix would be along shortly. However, I'd like to understand how jython figures into the transitive set (and why - maybe we get it out of the essential set), and how a developer can determine this. Looking at reverse depends: > $ reverse-depends jython > Reverse-Depends > =============== > * eclipse-pydev-data > * electric > * libred5-java > * libsikuli-script-java > * plm There's nothing here that isn't a leaf or all but. And for build-deps, it's not that much different. > $ reverse-depends -b jython > Reverse-Build-Depends-Indep > =========================== > * electric > * plm > * red5 > > Reverse-Build-Depends > ===================== > * eclipse-pydev > * libfreemarker-java > * libmx4j-java > * sikul So is there a tool I can use to view the entire tree to see where jython is required? Thank you, tony
signature.asc
Description: OpenPGP digital signature
