On Thu, Jan 02, 2025 at 06:09:20PM +0100, Antonio Valentino wrote:
Dear Paul,
# Broken Depends:
c-blosc2: libblosc2-dev
pytables: python3-tables-lib
zmat: octave-zmat
we may need to stop building those packages on this arch or otherwise change the nature of the depends relationship before this removal can be processed.
For libblosc2-dev I can confirm that it is no longer built for mips64el (see [1]).
Nice, that's great news. The old binary is still kicking around, even
though it's no longer built by unstable.
libblosc2-dev | 2.15.1+ds-1 | unstable | mips64el
libblosc2-dev | 2.15.2+ds-4 | unstable | amd64, arm64, armel, armhf, i386, ppc64el, riscv64
If you'd be able to file a removal for that one I can process that.
For python3-tables-lib I can confirm that it is fine to stop building on mips64el. It is not clear to me if you need a change in the src:pytables control file. It would not be appropriate form my point of view because pytables itself has no issues on mips64el. Could you please clarify?
python3-tables-lib | 3.10.1-1+b2 | unstable | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64
This is an arch:any package. It's built on mips64el. If this removal
goes through, libblosc2-4 will be removed from mips64el.
python3-tables-lib will be uninstallable, since it depends on
libblosc2-4.
| Depends: python3 (<< 3.14), python3 (>= 3.12~), python3-numpy (>= 1:1.25.0), | python3-numpy-abi9, libblosc1 (>= 1.7.0), libblosc2-4 (>= 2.11.2),
| libbz2-1.0, libc6 (>= 2.14), libhdf5-310 (>= 1.14.3),
| liblzo2-2 (>= 2.02)
Also it is not clear to me what do you mean with "change the nature of the depends relationship". Do you have something specific to suggest?
Not really, I'll defer to the package maintainer to figure out what the
right solution to avoid rendering packages uninstallable is. From the 30 seconds I spent checking, I reckon you have two major options:
1) request removal of python3-tables-lib and any dependenents /
build-dependents on mips64el, and change Architecture: any
2) compile out support for libblosc2-4 on mips64el (if possible) and
make that dependency arch-specific ([!mips64el]).
I'll let y'all figure that out.
For zmat I have put in cc Qianqian Fang, the current uploader of the
package. Maybe he can confirm if the operation is fine form his point of view.
Same story for zmat as python3-tables-lib above.
| Depends: libblosc2-4 (>= 2.9.2), libc6 (>= 2.14), libgcc-s1 (>= 3.0),
| liblz4-1 (>= 0.0~r130), libstdc++6 (>= 4.1.1), libzstd1 (>= 1.5.5), | zlib1g (>= 1:1.2.0), octave (>= 9.2.0)
removing this package wound render zmat-octive uninstallable on
mips64el.
octave-zmat | 0.9.9+ds.1-3 | unstable | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, riscv64
You have the same two options as above :)
[1] https://salsa.debian.org/science-team/c-blosc2/-/blob/debian/2.15.2+ds-4/debian/control?ref_type=tags#L42
kind regards
--
Antonio Valentino
Thanks for your work,
paultag
--
⢀⣴⠾⠻⢶⣦⠀ Paul Tagliamonte <paultag>
⣾⠁⢠⠒⠀⣿⡁
https://people.debian.org/~paultag |
https://pault.ag/
⢿⡄⠘⠷⠚⠋ Debian, the universal operating system.
⠈⠳⣄⠀⠀ 4096R / FEF2 EB20 16E6 A856 B98C E820 2DCD 6B5D E858 ADF3
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEt+z0Ld/ZiscwHAYrEQGtWoE2mtcFAmd2y9MACgkQEQGtWoE2 mteYIg//anwK94wXIWaPnzyPcthUq1+xBr7UiZqWc3AugZZAf3FCFJTxnrhs6spN xyRV4OaUVvb0+XX7vax0mDHu7eKn4aCGWLnnF4HOajSg7HYJGTkOLa/I1k0HU6na PO3NUrItiKx7UtT5trVlXd8DkFhtbzP/b+Fpx8a+4zOxj9ivjKvz1pR2kOOO86hu LXVCfUAdwTfQqmUzZnxN0r+1GRUzlrON0wgW1QG34zu2+jdGX6Uhq/c9F/Hk1Vvi 0bJUbonasJZ7XL7FMLEEE0jV+nS3ADZwzu1RNak/ASCHeHv+wqUSQDUHkR9hAU1c YStjKkOP0x3WMh8EQ3t7ktHpsKY2+cgHytBTXICjNbyLUvgqC2BKnqjZ2i0g7WDp iG0PeiBXIbLS+1DDjgc+guAnYAn8jqSh1LJk/tI414RYTFfxxRpIbr5WOvm6XIpt R9QG3NvqRyqj2sofHkm3MASrT4DaQPl+UrG0KsyTjCVRIr5bIxWsk5lJNQoKhlat fmdJiSpqo4aCV3+GcKPO/9DDUcF8KBlEFEN0bf0FTgogteJR0Jsm4IJsGP6pwJxr GjKK6oYBytMb4tmQG+XwjM6jfhZJN