* Paul Wise (p...@debian.org) wrote:
> On Mon, Mar 13, 2017 at 1:36 AM, Simon McVittie wrote:
>
> > Most of the packages that I've glanced at so far seem to have moved
> > from an ancient version (often automake1.4 or automake1.9) to 1.11.
> > In the past, Automake had a tendency to break compatib
On Mon, Mar 13, 2017 at 1:36 AM, Simon McVittie wrote:
> Most of the packages that I've glanced at so far seem to have moved
> from an ancient version (often automake1.4 or automake1.9) to 1.11.
> In the past, Automake had a tendency to break compatibility
> between minor releases, making it desir
On Mon, Mar 13, 2017 at 1:36 AM, Simon McVittie wrote:
> Paul Wise
>warzone2100 (U)
I've talked to folks on the upstream IRC channel and it appears to be
compatible with automake 1.14 so the latest version will probably
work.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Thu, Feb 9, 2017 at 3:48 PM, Adam Borowski wrote:
> On Thu, Feb 09, 2017 at 03:24:48PM +0200, Eugene Zhukov wrote:
>> I have a package (saxonhe) whose newer versions are not backwards
>> compatible and break other packages (build)depending on it e.g.
>> epubcheck. I guess this is a common probl
4 matches
Mail list logo