Groups > linux.debian.maint.java > #12464

Re: Status of antlr4 in Debian

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Emmanuel Bourg <ebourg@apache.org>
Newsgroups	linux.debian.maint.java
Subject	Re: Status of antlr4 in Debian
Date	Wed, 26 Oct 2022 18:30:01 +0200
Message-ID	<FkRrX-gSYs-11@gated-at.bofh.it> (permalink)
References	<FkPTb-gRY4-9@gated-at.bofh.it>
X-Original-To	debian-java@lists.debian.org
X-Mailbox-Line	From debian-java-request@lists.debian.org Wed Oct 26 16:22:53 2022
Old-Return-Path	<ebourg@apache.org>
X-Amavis-Spam-Status	No, score=-12.002 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no
X-Policyd-Weight	NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .apache. - helo: .mxout1-ec2-va.apache. - helo-domain: .apache.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5
Authentication-Results	apache.org; auth=none
MIME-Version	1.0
User-Agent	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.13.1
Content-Language	en-US
Content-Type	text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding	8bit
X-Mailing-List	<debian-java@lists.debian.org> archive/latest/23104
List-ID	<debian-java.lists.debian.org>
List-URL	<https://lists.debian.org/debian-java/>
List-Archive	https://lists.debian.org/msgid-search/9e929ccb-7ae1-fe97-715c-308ab13d850e@apache.org
Approved	robomod@news.nic.it
Lines	26
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Wed, 26 Oct 2022 18:22:31 +0200
X-Original-Message-ID	<9e929ccb-7ae1-fe97-715c-308ab13d850e@apache.org>
X-Original-References	<c9ca287f-0d44-325f-9fc7-d95db2fc0aad@debian.org>
Xref	csiph.com linux.debian.maint.java:12464

Show key headers only | View raw

Hi Pierre,

Le 26/10/2022 à 16:47, Pierre Gruet a écrit :

> My question is: apart from time to work on the package, is there any 
> reason we should remain with antlr4 4.7.2 in Debian although 4.11.1 has 
> been released upstream?

Yes, antlr is the kind of package you don't want to upgrade, because 
it's likely to break another package and debugging a language grammar 
without upstream consent is really the last thing you want to do. So as 
long as it works, I'm not touching it :)

The safe way to upgrade antlr4 is to:
- check the version used by the reverse dependencies
- if the lowest version used is above the package version, then upgrade
- if the version you need is still higher, checkout the project, update 
the antlr dependency and run the upstream test suite (not from the 
Debian package build since tests are sometime disabled)
- if all goes well, upgrade the antl4 package
- if if not, clone the package to keep the previous version (we had to 
do this with antlr 3.2)

Good luck!

Emmanuel Bourg

Back to linux.debian.maint.java | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Status of antlr4 in Debian Pierre Gruet <pgt@debian.org> - 2022-10-26 16:50 +0200
  Re: Status of antlr4 in Debian Emmanuel Bourg <ebourg@apache.org> - 2022-10-26 18:30 +0200
    Re: Status of antlr4 in Debian Pierre Gruet <pgt@debian.org> - 2022-10-26 22:50 +0200
      Re: Status of antlr4 in Debian Thorsten Glaser <t.glaser@tarent.de> - 2022-10-26 23:00 +0200
        Re: Status of antlr4 in Debian Pierre Gruet <pgt@debian.org> - 2022-10-27 18:00 +0200

csiph-web