Dear Maintainer, upstream has made some changes to the configuration sections in pyproject.toml that ruff understands. Tests in other packages (e.b. python-xsdata) have started to use the new configuration options and it would lighten the patch-load if ruff were updated to its latest release (0.3.5 at the time of writing). Regards, Michael - -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 5.10.110-rockchip-rk3588 (SMP w/8 CPU threads) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_DK.UTF-8), LANGUAGE=en_US.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages ruff depends on: ii libc6 2.38-5 ii libgcc-s1 14-20240330-1 ruff recommends no packages. ruff suggests no packages. - -- no debconf information -----BEGIN PGP SIGNATURE----- iQFPBAEBCgA5FiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmYMPfgbHGZsYWRpc2No ZXJtaWNoYWVsQGZsYWRpLmF0AAoJEP/TyIuZfdFqMR4H/2JUC9YyAVx6WtopF3kx O4zOMrFVjFfhrtjcuB3i4Hka/R56sSB4FM213ucKGhITVJFJXPsUqwyq6M0VvTEC miu6QiMD+F/Md6Q0r3jXxXxvWs7dafzrHa2KQV+G18WatTh5KFMWpIO96m34tQ8u 7FVUzhFYOfPH7ZyQtxNNjXJwe6HOiwY0kPMUP5qcJgKPiyRJbyN5X52Js78ywhOI YcYym323bL/IoBtjqzxJtuqMH+Xy9knaXM8/Iq0hXc6nGVVxJImidGjOH/I4O3wD oNn9X6YdoXcw03NNNxdJFARn3zPyNB83E3efQggGgfaEJxTfZ5PBvwoKv9G4926K eN0= =Xzr3 -----END PGP SIGNATURE-----
Hello, Upstream has produced more releases and is now at 0.4.8 on pypi In addition to The changes mentioned by Michael, the newer versions also have some additional CLI options that enable features that some users may need. For exemple "ruff format --diff" is currently used by coc-pyright for triggering code formatting, but the option "--diff" does not exist in version 0.0.291 Cheers!
Hello Jelmer, would you mind to have a look at this wishlist report? Would be really helpful to get a newer version of ruff into Debian, as already mentioned in the report packages start to depend on a more recent version of ruff. Thanks!
ruff 0.0.whatever is now beyond old, and there's a current merge on Salsa. So, what's the hold-up and can we help out?
Hi, can somebody help with bug#1068248? That's an update for "ruff", the linter for Python which happens to be written in Rust ;-) It's been languishing for half a year now, we (i.e. the Python people whose packages use ruff for testing) really could use an update; the problem is that I have no idea how to package for Rust. The package itself seems to be in reasonably good shape, except for the inconvenient fact that it has a direct dependency to a crate on github … Thanks in advance (I hope *g*)!
FWIW I imported a new upstream release a couple of weeks ago, which is in the Git repository - https://salsa.debian.org/python-team/packages/ruff However, it needs a lot of work since the dependencies have changed significantly. Some aren't in Debian, some are at different versions and some are pulled directly out of upstream git repositories. When I packaged the first release, this was a significant amount of work - and 6 months on a lot of the dependencies have changed again. I think the best first step would probably be to inventarise what rust packages are missing and then maybe we can distribute the work. Cheers, Jelmer
Hi from a ruff user. The rust debian team kindly pointed to
cargo debstatus
debcargo
I ran cargo debstatus with these steps and the output is at
https://paste.debian.net/1353518
git clone --depth 1 'https://github.com/astral-sh/ruff'
cd crates/ruff # per <github.com/kpcyrd/cargo-debstatus/issues/12>
Delete recursive dependencies, otherwise `cargo debstatus` fails (it gives
stack overflow error or fills the disk):
- I deleted the `ruff_annotate_snippets` dependency in
crates/ruff_annotate_snippets/Cargo.toml
- red_knot_python_semantic and red_knot_test depend on each other.
I deleted the red_knot_test line in
crates/red_knot_python_semantic/Cargo.toml
cargo debstatus \
| sed 's,│ \+,,g' \
| sed 's,├── \+,,' \
| sed 's,└── \+,,' \
| sort \
| uniq \
Note that it's not a pipe character what you see in sed's pattern:
$ echo '│' | hexdump # symbol being removed
0000000 94e2 0a82
0000004
$ echo '|' | hexdump # normal pipe symbol
0000000 0a7c
0000002
The commands `cargo debstatus` and `debcargo` are from the Debian packages cargo-debstatus and debcargo respectively.
I've packaged these. We should just patch this out I think, since nushell isn't packaged in Debian. Looks like you did this one as well: Leaving these: Jelmer
Hi, I'd like to help. I run `cargo debstatus` but they are too many packages. Seems raj you know how to filter them? Anyone has a current status about which packages we need to to introduce to Debian? I think we should focus on them for now.
See the list I just posted to the bug. Basically: icu-collections icu-locid-transform-data icu-locid-transform icu-locid icu-normalizer-data icu-normalizer icu-properties-data icu-properties icu-provider-macros icu-provider idna-adapter notify-types peg-macros peg-runtime peg salsa-macro-rules serde-wasm-bindgen test-case-core test-case-macros test-case tracing-flame unicode-names2-generator ureq utf16-iter utf8-iter uuid-macro-internal writeable zerofrom-derive zerovec-derive zerovec Jelmer
Hello! I could send to NEW idna-adapter, that was initialized by Peter Michael Green. Now, I'm stuck with icu-collection due #1073151. I will try to fix them and continue with icu* deps.
May I note that - idna-adapter 1.1 didn't need the icu* (icu4x) stack. It's 1.2 that introduced them. With only one week to soft freeze, I don't think you should/could touch them. - I have filed an ITP for icu4x, #1101486. If you are determined to package the stack, please take it over.
yep :/. I'll try