Your message dated Sun, 12 Nov 2023 01:33:17 -0500 with message-id <CAB4XWXwmJJUAiH75gHGB=5rq_gxgpbayh4ggtagw-_m-okc...@mail.gmail.com> and subject line Re: Bug#1055824: python3-rich: violates Python package metadata with dependency package 'python3-markdown-it' 3.0.0-2 has caused the Debian Bug report #1055824, regarding python3-rich: violates Python package metadata with dependency package 'python3-markdown-it' 3.0.0-2 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1055824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055824 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: python3-rich Version: 13.3.1-2 Severity: normal Howdy, The Debian binary package ‘python3-rich’ declares: Depends: python3-markdown-it with no version constraint. On this machine, the dependency is satisfied by the only available version ‘python3-markdown-it’ version “3.0.0-2”. The Python metadata installed by the Debian ‘python3-rich’ package declares a constrained version range for that corresponding dependency: Requires-Dist: markdown-it-py (>=2.1.0,<3.0.0) This results in the Python ‘pip’ package dependency graph reporting (correctly) that its version constraints are not satisfied by the installed packages: INFO: pip is looking at multiple versions of rich to determine which version is compatible with other requirements. This could take a while. ERROR: Could not find a version that satisfies the requirement markdown-it-py<3.0.0,>=2.1.0 (from rich) (from versions: none) The inconsistent constraints need to be resolved; the Python package metadata dependency declarations need to be satisfied when the Debian package is installed. Either: * The upstream version constraint needs to be relaxed by the upstream project, to allow ‘python3-rich’ version “3.0.0-2” to satisfy the dependency. or * The Debian package needs to constrain its dependency on ‘python3-rich’ to match upstream's declared constraints. -- System Information: Debian Release: trixie/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_AU.UTF-8), LANGUAGE=en_AU.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-rich depends on: ii python3 [python3-supported-min] 3.11.4-5+b1 ii python3-markdown-it 3.0.0-2 ii python3-pygments 2.15.1+dfsg-1 ii python3-typing-extensions 4.7.1-2 python3-rich recommends no packages. python3-rich suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---> The inconsistent constraints need to be resolved; no they dont. debian uses apt not pip to install packages. from a packaging perspective, what matter is "does rich work?" and since the answer is "yes", there's nothing to do here, closing (and please do not reopen). -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
--- End Message ---
