shiny-server has been mentioned as a potential covid-19 related package
[0], though it isn't on the current hackathon list [4].
There is a packaging attempt in science-team Salsa (but no formal ITP)
from early 2018. Discussion at the time suggests it builds but possibly
doesn't work [1], and
Sorry, that's only true of the Python part of streamlit (/lib/); the
JavaScript part (/frontend/) has 300+ (recursive) dependencies.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956194
Thanks for trying, and please do upload the module you've finished: it
may be useful elsewhere. If you'd
From searching the source, it appears that only 2 tests (plus some
examples) need tensorflow:
hashing_test.py:HashTest.test_tensorflow_non_hashable and
keras_test.py:KerasTest. Hence, skipping these tests may be a
reasonable option after all.
Internet-using tests are discouraged because they can fail for external
reasons, but preferred to leaving online features untested:
https://sources.debian.org/src/autopkgtest/5.12.1/doc/README.package-tests.rst/#L431
(Not sure if there are any rules about downloading code vs data)
There is a
From #954150, it appears there _is_ a code vs data distinction: tests
are allowed to use the network but not to download and run code.
https://ftp-master.debian.org/REJECT-FAQ.html Non-Main II
I intend to post a patch to autopkgtest to document this.
Manually running the tests in question
A potential workaround for testing: while package builds (including
build-time tests) are not allowed to use the network, autopkgtests *are*
allowed to => skip the tensorflow-needing tests in build, but run them
(with tensorflow from PyPI) in autopkgtest?
However, streamlit also has a Javascript component (the frontend
directory), with ~100 dependencies Debian doesn't have (plus a few that
Debian has in too old a version):
$ npm2deb depends /home/rnpalmer/Debian/builds/stackbuild/package.json
Dependencies:
NPM
Existing discussion of this package's dependencies:
https://lists.debian.org/debian-med/2020/04/threads.html#00065
Summary:
- Python part: 2 tests depend on tensorflow (which is known to be hard
to package), but the rest doesn't so skipping these tests is an option.
- JavaScript part: npm2deb
tensorflow 1.10 was packaged in experimental, but with reduced
performance, and was removed because this was considered not worth it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935769
streamlit requires tensorflow only for testing:
It does (and eslint itself is one of the packages that we do have but
npm2deb can't find), but even ignoring build dependencies completely and
assuming we can use the plotly.js embedded in python3-plotly or
r-cran-plotly, the recursive dependency tree is >300 different
not-yet-packaged
It was left un-updated because upstream started using a patched LLVM,
and packaging that was considered inappropriate and/or too much work.
Upstream stopped doing that ~6 months ago, so there is currently no
obvious reason for not updating it, but I haven't actually tried to do so.
Previous discussions:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862524
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887728
Note that we probably can't use code from this package to improve ours:
I can't find any packaging code in the conda source on GitHub (BSD-3
licensed), and repo.anaconda.com has legal restrictions, including on
redistribution:
https://know.anaconda.com/TOS.html
However, end users of conda are
Package FTBFS everywhere, for multiple reasons but looks like the new
pytest_asyncio is at least one of them; will investigate further later.
Not yet, it should at least be 1.0.5 from Salsa.
(Also, q2-* have autopkgtests so it will probably get stuck in -proposed.)
On 25/08/2020 08:19, Graham Inggs wrote:
Hi Rebecca
On Mon, 24 Aug 2020 at 01:03, Rebecca N. Palmer wrote:
pandas 1.0 has been in experimental for 6+ months, because
Second attempt uploaded.
Of the reverse dependencies with known fixes, python-feather-format has
been uploaded but q2templates hasn't.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950430
pandas 1.0 has been in experimental for 6+ months, because it breaks
some of its reverse dependencies:
In testing:
#950924 python-feather-format (has patch, no maintainer response to it)
#950931 q2templates (has upstream fix)
#950929
On 18/10/2021 08:15, Nilesh Patra wrote:
On Mon, Oct 18, 2021 at 01:32:30AM +0200, Steffen Möller wrote:
Is anyone continuing the update of
snakemake now?
@Rebecca, could you look into it now that pulp is done?
Currently, there is just a very few failing tests -- I guess
most are due to some
On 15/10/2021 14:46, Andreas Tille wrote:
Hi Rebecca
and whoever might care. As usual snakemake is troublesome to upgrade.
I have injected the latest version into Git but there are lots of
failed tests. It would be great if someone could care about this.
Kind regards
Andreas.
I
The documentation says:
https://github.com/snakemake/snakemake/blob/main/docs/tutorial/additional_features.rst#cluster-execution
https://github.com/snakemake/snakemake/blob/main/docs/executing/cluster.rst
I don't know how up to date this is, but the code to use drmaa is still
there.
snakemake
I didn't mean that these other non-packaged options were direct
alternatives to drmaa, only that snakemake already doesn't have all its
features available in Debian without installing external packages, and
that I don't consider losing one more to be a serious bug.
If anyone _wants_ to work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Please upload snakemake 6.15.1-1 to unstable
(Salsa HEAD = commit ID 8bf4db496feed2fa84f23018acba0033e321ef69).
This splits the binary package into snakemake and snakemake-doc,
which I can't do myself because DMs can't upload NEW packages.
I think at least my problem (participant list+chat but no video/audio,
and frequent disconnects) was at my end, not the server's, and is now
fixed. I don't know whether the other people with issues had the same
issue.
I think the cause was that I had AppArmor blocking it (with my own
I switched it because of the general recommendation to move away from
master because it's potentially offensive. I had forgotten that that
team policy existed.
It's generally my intention that if I list myself as Uploader then I'm
taking full responsibility, and won't let that package get
On 07/02/2023 07:00, Andreas Tille wrote:
Am Mon, Feb 06, 2023 at 10:21:46PM + schrieb Rebecca N. Palmer:
I switched it because of the general recommendation to move away from master
because it's potentially offensive.
Thanks for explaining your reason for the change. I admit I have
Control: reopen -1 1026539
theano has been mostly abandoned upstream since 2018. (The Aesara fork
is not abandoned, but includes interface changes including the import
name, so would break reverse dependencies not specifically altered for it.)
It is currently broken (FTBFS due to multiple
Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Control: affects -1 src:theano src:deepnano src:keras
Control: reopen 1026539
Control: reopen 1027215
theano has been mostly abandoned upstream since 2018. (The Aesara fork
is not abandoned, but includes
Control: severity 1053943 1053939 1053942 1044053 1044056 serious
Control: severity 1044074 1053946 1044078 1044079 1044077 serious
Control: severity 1044071 1044067 1044068 1044055 1044060 serious
Control: severity 1044072 1044073 1044064 1053945 1044054 serious
Control: severity 1044076 1053940
I'd like to move forward with the pandas 1.5 -> 2.1 transition
reasonably soon.
Given that pandas 2.x is *not* required for Python 3.12 (but is required
for Cython 3.0), should we wait for the Python 3.12 transition to be
done first?
These are broken by pandas 2.x and have a possible (but
29 matches
Mail list logo
