Hi Manuel, Manuel Guerra (2026-01-01): > As the maintainer of pycares and aiodns, I am reporting that pycares > version 5.0.0-3 introduced changes that break compatibility with the > current aiodns (3.6.1). > [...]
I'm trying to understand why this bug was closed with the 5.0.1-2 upload: from what I see on #1124323, the incompatibility is still there in sid, and downgrading to python3-pycares 4.9.0-1 fixes it. > Please block migrations from pycares 5.0.0 to Testing until aiodns is > compatible. Yes, please. > I have updated aiodns with a version restriction (<< 5.0.0) > to allow its own migration with version 4.9.0, which already resides in > Testing. This seems like a great idea! However I don't see this version restriction in python3-aiodns 3.6.1-2. Am I looking in the wrong place? Cheers, -- intrigeri
