Bug#706866: transition: libarchive

To: peter green <plugwash@p10link.net>, 706866@bugs.debian.org

Subject: Bug#706866: transition: libarchive

From: Andres Mejia <amejia004@gmail.com>

Date: Mon, 6 May 2013 20:18:36 -0400

Message-id: <[🔎] CAPM41nMKWtxbape7mxTg55VnvUVQmKgsKBNN0dF=5+Xz3Tsh8Q@mail.gmail.com>

Reply-to: Andres Mejia <amejia004@gmail.com>, 706866@bugs.debian.org

In-reply-to: <CAPM41nOJL9YLSr-xkSQMvGjD2HBE7-Xw2FJJJD1a9aLV43n1eg@mail.gmail.com>

References: <[🔎] 518842DF.1000005@p10link.net> <CAPM41nOJL9YLSr-xkSQMvGjD2HBE7-Xw2FJJJD1a9aLV43n1eg@mail.gmail.com>

Oops, meant to reply all.

On May 6, 2013 8:17 PM, "Andres Mejia" <amejia004@gmail.com> wrote:

Yes, I plan on disabling lrzip support for now.

On May 6, 2013 7:55 PM, "peter green" <plugwash@p10link.net> wrote:

I am requesting a transition from libarchive12 to libarchive13. libarchive13
is from the latest release of libarchive (3.1.2). A soname bump was done
upstream due to some ABI changes, specifically with HFS support.

I notice the most recent experimental upload FTBFS on many architectures with testsuite failures. Have you investigated how serious those failures are? Do you have plans for fixing them before uploading to sid?

Reply to:

References:

Bug#706866: transition: libarchive
- From: peter green <plugwash@p10link.net>