On 12/3/2019 3:44 PM, Jon Turney wrote:
> On 01/12/2019 19:31, Ken Brown wrote:
>> On 8/1/2019 12:05 PM, Jon Turney wrote:
>>> e.g. setup -q -g -P python3-lxml (which used to do something useful)
>>> currently gets you an (empty) python3-lxml package, which will be replaced
>>> by python36-lxml
On 01/12/2019 19:31, Ken Brown wrote:
On 8/1/2019 12:05 PM, Jon Turney wrote:
e.g. setup -q -g -P python3-lxml (which used to do something useful)
currently gets you an (empty) python3-lxml package, which will be replaced
by python36-lxml (which obsoletes it) on the next setup run. After this
On 8/1/2019 12:05 PM, Jon Turney wrote:
> e.g. setup -q -g -P python3-lxml (which used to do something useful)
> currently gets you an (empty) python3-lxml package, which will be replaced
> by python36-lxml (which obsoletes it) on the next setup run. After this
> change, python36-lxml is installed
e.g. setup -q -g -P python3-lxml (which used to do something useful)
currently gets you an (empty) python3-lxml package, which will be replaced
by python36-lxml (which obsoletes it) on the next setup run. After this
change, python36-lxml is installed instead.
See also the dicusssion at
