From: Theodore Ts'o <tytso@mit.edu>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsprogs: building ext2simg
Date: Mon, 9 Oct 2017 08:59:02 -0400 [thread overview]
Message-ID: <20171009125902.66u7hsgxsueedquq@thunk.org> (raw)
In-Reply-To: <CAP71WjwVdqmLEq1NGWK36JkEd-i05YcAu4jeY6GFjsk6TS=Mtg@mail.gmail.com>
On Mon, Oct 09, 2017 at 10:24:46AM +0200, Nicolas Dechesne wrote:
>
> The problems appears as soon as I upgrade from e2fsprogs 1.42.12-2+b1
> (the version in Jessie) to either the version in Stretch or the
> version in jessie-backport. So it looks like e2fsprogrs 1.43, breaks
> something with existing ext2simg (I am using ext2simg from
> android-tools-fsutils, so the 'old' one).
So *that* shouldn't have happened. I do try to keep the ABI/API of
the libext2fs shared library stable, even across major version
numbers. That being said, I suspect ext2simg was doing something that
made it highly dependent on the internal implementation detalis of
libext2fs. It would be interesting to know what in the world that
was, so I can try to avoid that in the future. But I've always viewed
many of these tools to be quite highly fragile, so I'm not sure
there's much we can do to fix this in terms of changing what libext2fs
is doing. But if I can fix/improve the backwards compatibility
problem from libext2fs's side, I'm certainly willing to entertain that
notion.
- Ted
prev parent reply other threads:[~2017-10-09 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 20:04 e2fsprogs: building ext2simg Nicolas Dechesne
2017-10-08 21:27 ` Theodore Ts'o
2017-10-09 8:24 ` Nicolas Dechesne
2017-10-09 12:59 ` Theodore Ts'o [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171009125902.66u7hsgxsueedquq@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=nicolas.dechesne@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).