public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: peteman <peteman@bofanez.org>
Cc: xfs@oss.sgi.com
Subject: Re: debian xfsprogs package
Date: Fri, 6 Mar 2015 07:00:10 +1100	[thread overview]
Message-ID: <20150305200010.GB4251@dastard> (raw)
In-Reply-To: <54F888CD.3070200@bofanez.org>

On Thu, Mar 05, 2015 at 08:48:13AM -0800, peteman wrote:
> the debian xfsprogs package places xfs_check in /usr/sbin. This
> causes problems when fscking the /usr partition....

xfs_check was deprecated quite some time ago, and was removed
from the upstream repository almost a year ago, as per the xfs-check
man page:

$ dpkg --list xfsprogs |tail -1
ii  xfsprogs       3.2.0        amd64        Utilities for managing the XFS filesystem
$ man xfs_check
....
Note that xfs_check is deprecated and scheduled for removal in June 2014. Please use xfs_repair -n instead.

And the commit in the upstream repo:

commit bfc541e77b9af46a2e3764df595620ec9824a456
Author: Eric Sandeen <sandeen@redhat.com>
Date:   Tue May 20 18:30:23 2014 +1000

    xfsprogs: remove xfs_check
    
    This removes xfs_check and all references to it in
    manpages.  The DIAGNOSTICS section from xfs_check(8)
    has been moved to xfs_db(8).
    
    Signed-off-by: Eric Sandeen <sandeen@redhat.com>
    Reviewed-by: Dave Chinner <dchinner@redhat.com>
    Signed-off-by: Dave Chinner <david@fromorbit.com>

And so it was removed in the 3.2.1 release. debian testing is
shipping 3.2.1 already...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2015-03-05 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 16:48 debian xfsprogs package peteman
2015-03-05 20:00 ` Dave Chinner [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=20150305200010.GB4251@dastard \
    --to=david@fromorbit.com \
    --cc=peteman@bofanez.org \
    --cc=xfs@oss.sgi.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