On Tue, 22 Sep 2015, Markus Koschany wrote:
>
> I think we can drop lynx from Build-Depends since it is commented out
> anyway and I would remove Thorsten Werner from Uploaders.
I agree, this important package for the team (and the project) should
have an up-to-date list of Uploaders. I guess Emm
2015-09-23 14:28 GMT+06:00 Emmanuel Bourg :
> Le 23/09/2015 08:50, Sergey Basalaev a écrit :
>
> The sequence is:
> 1. Upgrade antlr3/3.2 to the version 3.3
> 2. Build stringtemplate 4.0.6 with antlr 3.3
> 3. Upgrade antlr3 to the version 3.5.2
> 4. Upgrade stringtemplate4 to the version 4.0.8
>
Am 23.09.2015 um 09:53 schrieb Emmanuel Bourg:
> I pushed the java-policy package on Alioth [1], reviews are welcome.
> I'll remove the policy from java-common once the java-policy package is
> in unstable.
I think we can drop lynx from Build-Depends since it is commented out
anyway and I would re
Le 23/09/2015 08:50, Sergey Basalaev a écrit :
> So now I'm stuck. How do you build packages with such circular dependencies?
> I checked previous versions of both packages in git, but it's still
> unclear for me how they were built in the first place.
Hi Sergey,
I used an intermediary version o
I pushed the java-policy package on Alioth [1], reviews are welcome.
I'll remove the policy from java-common once the java-policy package is
in unstable.
Emmanuel Bourg
[1] http://anonscm.debian.org/cgit/pkg-java/java-policy.git
Greetings, debian-java
I wanted to put the latest antlr3 package into my Ubuntu PPA, but I cannot
build it
because apparently it has circular build dependencies.
antlr3 3.5.2-2
Build-Depends: libstringtemplate4-java (>= 4.0.8)
libstringtemplate4-java 4.0.8-2
Build-Depends: antlr3 (>= 3.5.2)
6 matches
Mail list logo