linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Autif Khan <autif.mlist@gmail.com>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: /dev/disk/by-label missing after upgrade to 1.42.7
Date: Thu, 20 Jun 2013 20:23:14 -0400	[thread overview]
Message-ID: <20130621002314.GA10730@thunk.org> (raw)
In-Reply-To: <CADzUK1+ykJ9uZjHkCuVrc5_kHyXwVsngfYBKJcd0qdtSZJGNOQ@mail.gmail.com>

On Thu, Jun 20, 2013 at 07:08:35PM -0400, Autif Khan wrote:
> I have updated our scripts to overwrite only those binaries that
> originated from the e2fsprogs package. In our build/CI system it would
> be (relatively) hard to build a debian package using fakeroot
> dpkg-buildpackages, instead, we run dpkg -S /bin/binary to find if the
> package originated in e2fsprogs and if it did, we copy it over,
> otherwise not. For now this works, we will pay the technical debt
> if/when we need to - chances are this will go away in Ubuntu 14.04 LTS
> which should have the latest version of e2fsprogs.

If you're not willing to use dpkg-buildpackage, I strongly recommend
that you add the following configure options:

     --disable-libblkid --disable-libuuid --disable-fsck --disable-uuidd

... especially if you are building with shared libraries.  Otherwise,
you'll be building with one version of the shared libraries, and
running with a different shared libraries.

						- Ted


      reply	other threads:[~2013-06-21  0:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 18:55 /dev/disk/by-label missing after upgrade to 1.42.7 Autif Khan
2013-06-13 19:45 ` Autif Khan
2013-06-13 21:35   ` Eric Sandeen
2013-06-13 22:56     ` Darrick J. Wong
2013-06-14  1:26     ` Theodore Ts'o
2013-06-20 23:08       ` Autif Khan
2013-06-21  0:23         ` 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=20130621002314.GA10730@thunk.org \
    --to=tytso@mit.edu \
    --cc=autif.mlist@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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).