Re: Jmol on Sid, amd64 arch.
2010-12-08 09:36, Kenward Vaughan skrev: load: class JmolApplet not found. [...] Caused by: java.net.ConnectException: Network is unreachable at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) [...] Are you aware of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523368 and related bugreports? Quoting the bugreport: the solution is to set net.ipv6.bindv6only=0 in /etc/sysctl.d/bindv6only.conf . The bug has been fixed in openjdk. Hope it helps Johan -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/idnton$4m...@dough.gmane.org
Re: Bug#573538: Packaging again sagemath
Hi List, As a normal user who has read the emails, but not taken part in the discussion due to lack of time for commitments, I would like to comment. 2010-07-19 18:54, Giovanni Mascellani skrev: Yes, that's my interpretation too. But I think that, in order to have good communication with upstream, we'll have to show that the package can be maintained and won't fall forgotten as last time. As I read the reaction from upstream, they were frustrated that people installed the package with the expectation that it should be current and just work. As Tim stated, I think the problem was that it entered into a repository where people expect such things, and that this happened when it was released as part of a stable ubuntu release. That is, the problem was not primarily debian-related. The response and proposals from upstream also seem to argue about ubuntu rather than debian. IMHO and AFAIUI: For stable debian, people probably do not expect packages to be up-to-date. For unstable debian, people probably do not expect packages to be bug-free. For experimental debian, people probably do not install packages without knowing what they are doing, and without expecting them to work without problems. It was also stated (by Tim?) that due to a process involving the NEW-queue (I think), removing the package from debian and then reintroducing it again could be much more work than moving to experimental and working from there. I would appreciate getting an up-to-date sage-package in debian again, so I hope you find time and interest enough to continue the work. Regards Johan -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/i23mnv$ja...@dough.gmane.org
Re: Reproducibility
2010-04-30 16:29, Michael Hanke skrev: Usually we have some version in stable and some people will use it. [...] In Debian we have the universal operating system that incorporates all software and 'stable' is a snapshot of everything at the time of release -- and this is not what scientists want. That is why we have backports.org and neuro.debian.net that offer at least the latest and greatest for 'stable'. But this is still not enough. This is why I like the approach of Gobolinux, at least in theory. As I understand the basic idea of gobolinux, every packages follows a system like the debian alternatives system, where the alternatives are the different versions of that package. Upgrading therefore does not have to remove old versions, but can just install the new version and update the symlink, removing the old package can then be a separate procedure. To me (IMHO) that feels like _the_ solution, when combined with the debian snapshot service. I imagine maintenance not to be a problem. I would be happy to have only the same level of support as we have now, but with the eternal _availability_ of all packages. Perhaps other users have other requirements. Of course this also requires more form the alternatives-handling software in order to handle versioned dependencies when switching the alternatives system between different version, but I expect that to be doable using tools similar to those that exist now. Regards Johan -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hreska$ob...@dough.gmane.org
