Hi,

On 20-02-2025 08:23, Chen Shengqi wrote:

So this is causing both libraries to be dlopen-ed when pytorch-foo
tries to import torch in Python, and this is obviously broken.

Will you think about fixing this (eventually)? Having libraries co-installable is a common theme, particularly during transitions and during upgrades.

At this moment I don't see any elegant solution to this, users would
have to upgrade everything to avoid the breakage. Do you have any
suggestions?


Maybe not elegant per se, but it would be correct: add a versioned
Breaks to pytorch to the versions in testing that it breaks. Then the migration software will also be able to schedule the tests with the right things from unstable (I think. But while I'm thinking about it, I'm not 100% sure if it handles the binNMU'd case correctly).

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to