Your message dated Fri, 28 Nov 2025 13:01:42 +0100
with message-id <[email protected]>
and subject line closing
has caused the Debian Bug report #1100031,
regarding python-omegaconf: Incompatible with ANTLR >= 4.10; do we still need 
it in Debian?
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.)


-- 
1100031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100031
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-omegaconf
Version: 2.3.0-3
Severity: normal

Prompted by looking into some specific test issues in python-moto, I 
began considering what it would take to upgrade python3-antlr4 to 
something newer than 4.9.2.  This is difficult because ANTLR 4.10 
introduced incompatible changes to the lexers and parsers that cause (at 
least) test problems in a number of other packages 
(https://github.com/antlr/antlr4/releases/tag/4.10); some of these have 
been masked by disabling tests, but they still exist.  But we now have 
some packages that require >= 4.10 as well as some packages that require 
< 4.10, so we kind of need to sort this out.

One of the issues is in python-omegaconf, probably best described in 
https://github.com/omry/omegaconf/pull/1114.  There have been a couple 
of .dev releases that included this, but not a proper release, and 
https://github.com/omry/omegaconf/issues/1200 doesn't paint a very rosy 
picture of its upstream maintenance.

Given that there seem to be no reverse-dependencies in Debian, would it 
be better to just remove this and simplify a future python3-antlr4 
upgrade?

Thanks,

-- 
Colin Watson (he/him)                              [[email protected]]

--- End Message ---
--- Begin Message ---
Closing this bug.

--- End Message ---

Reply via email to