Your message dated Thu, 4 Feb 2021 18:52:11 +0200
with message-id <20210204165211.GA13256@localhost>
and subject line Re: Bug#974684: Incorrect dependency in python3-lxml
has caused the Debian Bug report #974684,
regarding python3-lxml: Cannot install python3-lxml/buster-backports on
bpo-enabled machine
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.)
--
974684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974684
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3-lxml
Version: 4.6.1-1~bpo10+1
Severity: important
Hi,
just tried to apt-get install python3-lxml/buster-backports but it failed as
follows:
------------------8<--------------------
# apt-get install python3-lxml/buster-backports
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '4.6.1-1~bpo10+1' (Debian Backports:buster-backports [amd64])
for 'python3-lxml'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
python3-lxml : Depends: python3 (< 3.6) but 3.7.3-1 is to be installed
E: Unable to correct problems, you have held broken packages.
------------------>8--------------------
The dependencies against python3 are defined as:
in python3-lxml 4.3.2-1 (buster): Depends: python3 (<< 3.8)
in python3-lxml 4.6.1-1~bpo10+1: Depends: python3 (<< 3.6)
Seeing that python3.7 is the default python3 in buster, why (<< 3.6) for /bpo
instead of (<< 3.7)?
Regards
Daniel
-- System Information:
Debian Release: 10.6
APT prefers proposed-updates
APT policy: (990, 'proposed-updates'), (990, 'stable'), (500,
'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500,
'oldstable-updates'), (500, 'oldstable-debug'), (500, 'oldstable'), (99,
'testing'), (98, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-12-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/bash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
This is now fixed, closing the bug.
cu
Adrian
--- End Message ---
