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

Re: Status of antlr4 in Debian

Path	csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	Pierre Gruet <pgt@debian.org>
Newsgroups	linux.debian.maint.java
Subject	Re: Status of antlr4 in Debian
Date	Wed, 26 Oct 2022 22:50:01 +0200
Message-ID	<FkVvz-gViD-11@gated-at.bofh.it> (permalink)
References	<FkPTb-gRY4-9@gated-at.bofh.it> <FkRrX-gSYs-11@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 20:47:45 2022
Old-Return-Path	<pgt@debian.org>
X-Amavis-Spam-Status	No, score=-11.999 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, NICE_REPLY_A=-0.001, PGPSIGNATURE=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -3.5
MIME-Version	1.0
User-Agent	Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.2
Content-Language	fr-FR
Content-Type	multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------5KzWUJTPH704n5rjrrTbPMyl"
X-Mailing-List	<debian-java@lists.debian.org> archive/latest/23105
List-ID	<debian-java.lists.debian.org>
List-URL	<https://lists.debian.org/debian-java/>
List-Archive	https://lists.debian.org/msgid-search/254dafbd-1ea8-dca1-df9d-15786bd59fa6@debian.org
Approved	robomod@news.nic.it
Lines	68
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Wed, 26 Oct 2022 22:47:14 +0200
X-Original-Message-ID	<254dafbd-1ea8-dca1-df9d-15786bd59fa6@debian.org>
X-Original-References	<c9ca287f-0d44-325f-9fc7-d95db2fc0aad@debian.org> <9e929ccb-7ae1-fe97-715c-308ab13d850e@apache.org>
Xref	csiph.com linux.debian.maint.java:12465

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

Hi Emmanuel,

Le 26/10/2022 à 18:22, Emmanuel Bourg a écrit :
> 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 :)

That's much understandable :-D

> 
> 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)

Thank you for this detailed checklist. I will investigate the field, 
being very cautious.

> 
> Good luck!
> 
> Emmanuel Bourg
> 

Thanks also for this :-D

Best regards,

-- 
Pierre

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