Package Details: xfsdump 3.1.6-1

Git Clone URL: https://aur.archlinux.org/xfsdump.git (read-only)
Package Base: xfsdump
Description: Additional XFS filesystem utilities
Upstream URL: http://oss.sgi.com/projects/xfs/
Licenses: LGPL
Submitter: ilpianista
Maintainer: Jristz
Last Packager: Jristz
Votes: 27
Popularity: 0.315749
First Submitted: 2010-11-13 15:36
Last Updated: 2015-11-22 01:04

Latest Comments

ryansito commented on 2015-11-16 20:43

It won't build for me:
[LD] xfsinvutil
inv_files.o: In function `inv_dirpath':
/home/user/xfsdump/src/xfsdump-3.1.4/invutil/inv_files.c:53: undefined reference to `assert'
inv_files.o: In function `inv_fstab':
/home/user/xfsdump/src/xfsdump-3.1.4/invutil/inv_files.c:60: undefined reference to `assert'
inv_files.o: In function `inv_lockfile':
/home/user/xfsdump/src/xfsdump-3.1.4/invutil/inv_files.c:67: undefined reference to `assert'
inv_files.o: In function `inv_basepath':
/home/user/xfsdump/src/xfsdump-3.1.4/invutil/inv_files.c:74: undefined reference to `assert'
collect2: error: ld returned 1 exit status
../include/buildrules:32: recipe for target 'xfsinvutil' failed
make[2]: *** [xfsinvutil] Error 1
include/buildrules:22: recipe for target 'invutil' failed
make[1]: *** [invutil] Error 2
Makefile:53: recipe for target 'default' failed
make: *** [default] Error 2
==> ERROR: A failure occurred in build().
Any idea? Thanks!!

dkaylor commented on 2015-10-06 07:16

Disowning, anyone else care to adopt?

dkaylor commented on 2015-06-19 06:59

Initial upload of xfsdump 3.1.4-2 to AUR4. No changes to the PKGBUILD.

dkaylor commented on 2015-01-21 18:44

I have entries for keyservers in my gpg.conf also (two actually), and I still have to add the --keyserver option. I don't really understand it either; need to read the man page thoroughly, which I haven't done in a while. If I learn anything, I will let you know.

piedro commented on 2015-01-21 14:53

... I had an entry in gpg.conf, probably misunderstood that part, whatever...

Specifying the keyserver manually works perfectly.

I really appreciate (and needed) your help,
thank you very much,
piedro

dkaylor commented on 2015-01-19 19:36

So, gpg --keyserver hkp://pgp.mit.edu --recv-keys 9893A827C19F7D96164A38FFADE82947F475FA1D

dkaylor commented on 2015-01-19 19:35

@piedro

You need to specify a key server to search using --keyserver

I use --keyserver hkp://pgp.mit.edu for importing keys

piedro commented on 2015-01-19 13:05

How to add the key for Dave Chinner then?

I used "gpg --recv-keys 9893A827C19F7D96164A38FFADE82947F475FA1D" and get "no keyserver available" though I use valid keyservers...

thx, piedro

dkaylor commented on 2015-01-14 12:21

Updated pkgrel to -2, just a few cleanups, added
validpgpkeys=('9893A827C19F7D96164A38FFADE82947F475FA1D')
for Dave Chinner, his key is used to sign the xfsdump source tar.gz
Anyone not already familiar with the pacman 4.2 way of doing things should read
http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/

dkaylor commented on 2014-08-02 05:50

Updated to 3.1.4.

zman0900 commented on 2013-06-19 06:13

I got it building properly without the hackery. Its not really a bug in their build system; upstream is forcing xfsdump and xfsrestore into /sbin if prefix is /usr to make sure they're always on the root partition. Since this is an Arch specific problem, I make a patch to their build system.

This patch makes --sbindir work as expected:
https://dl.dropboxusercontent.com/u/50802094/xfsdump-binaries-in-usr-bin.patch

Here's a working PKGBUILD that uses the patch:
https://dl.dropboxusercontent.com/u/50802094/PKGBUILD-xfsdump

The wiki says DIST_ROOT should be DESTDIR so I changed that. Also removed the extra hashes because I was lazy.

dkaylor commented on 2013-06-02 09:29

Uploaded a new PKGBUILD that merges all of the xfsdump binaries into /usr/bin, following the recent changes made to xfsprogs. I couldn't use the method from xfsprogs, it doesn't work properly with xfsdump source at the moment, so it's sort of a hacky way to go about it, but it works.

I'm not sure if a lack of symlinks in /sbin to /usr/bin is an issue, if anyone thinks so, let me know.

Thanks to Jristz for the advice on these changes!

Jristz commented on 2013-06-01 10:54

first that is a bug in build process, fill a bug upstream

I think for now a work around is moving files anddeleting foders in the old way using rmdir, mv in package()

dkaylor commented on 2013-06-01 10:18

But, when I just use:

make DIST_ROOT="${pkgdir}" PKG_ROOT_SBIN_DIR="/usr/bin" install

I get executables for xfsrestore and xfsdump in /usr/bin and symlinks to them
in /usr/sbin, along with an executable for xfsinvutil in /usr/sbin.

dkaylor commented on 2013-06-01 10:04

When I use:

./configure --prefix=/usr --sbindir=/usr/bin
make DIST_ROOT="${pkgdir}" PKG_ROOT_SBIN_DIR="/usr/bin" install

as with the latest xfsprogs, I end up with the symlinks /usr/bin/xfsdump and /usr/bin/xfsrestore pointing to themselves in /usr/bin, both are 0 bytes. Something about the build of xfsdump is obviously different from xfsprogs, so I may need some hack to simply mv from /sbin to /usr/bin, like you suggested in an earlier comment, not sure yet.

Jristz commented on 2013-06-01 08:44

and adding --bindir=/usr/bin --sbindir=/usr/bin to configure
and adding sbindir=/usr/bin or sbindir=$pkgdir/usr/bin to make install work for migrate xfdump files for the bin merge now in testing??

dkaylor commented on 2013-06-01 06:01

FYI to all using xfsdump, I'm currently working on redoing the PKGBUILD to move the executables out of /sbin to /usr/bin, bringing it into alignment with recent changes to the xfsprogs PKGBUILD. However, the resultant build is not behaving as expected (i.e. as xfsprogs does, which builds fine). But, I am working on it.

dkaylor commented on 2013-05-17 01:27

The issue with the bad sig at ftp://oss.sgi.com/projects/xfs/cmd_tars/ has been resolved, so I've updated to 3.1.3.

Jristz commented on 2013-05-12 20:44

bin meging now in TODO list and anounced on mailisting

why not simply make a 'mv $pkgdir/usr/sbin/* $pkgdir/usr/bin' and test if work??

dkaylor commented on 2013-05-10 19:53

Ben Myers, who maintains xfsdump, is looking at the bad sig issue and has an approximate cause in mind, so I will update soon.

dkaylor commented on 2013-05-10 19:00

I get a bad signature when checking xfsdump-3.1.3.tar.gz.sig downloaded from ftp://oss.sgi.com/projects/xfs/cmd_tars/. Can anyone else confirm this?

PerfectGentleman commented on 2013-05-10 17:59

3.1.3 came out

dkaylor commented on 2013-04-16 23:03

Releasing a -3 with some more changes and corrections, taking some cues from xfsprogs in core. Jristz, I will look into the directory merger issue you bring up, so another change may be needed.

Jristz commented on 2013-04-16 22:45

Is recommemded install think on /usr/bin rater than other dirs (/usr/sbin,/bin,/sbin) because think on Arch going to merge all those 3 into /usr/bin, maintain all in /usr/bin from the begining prevent laters unneded updates and problems at upgrade time when the merge happen (this year)

dkaylor commented on 2013-04-16 22:33

OK, I actually bothered to read the packaging standards, so I've brought the PKGBUILD up to modern standards and simplified it a bit.

dkaylor commented on 2013-04-16 12:15

I'm not seeing your pastebin; regardless, the package builds fine with 4.1's makepkg.

eworm commented on 2013-04-16 10:59

I've modified the PKGBUILD a bit, please update:
http://pastebin.com/fePYPdcA

This introduces a package() function to make makepkg from pacman-4.1 happy and installs all binaries to /usr/sbin/.

Jristz commented on 2013-02-12 04:16

any debug option is used only for debug prupossed and as far I know none package on Arch use it (and as FAR I read pacman 4.1+ can have separate debug simbols finally)

and as side note glibc upstream reccomend -o1 but Arch use -02, this mean that arch unles the compiller flags changes fix a bug (*cof* WINE *cof*), they no need to changed from the Arch defaults

dkaylor commented on 2012-12-15 12:06

Updated to 3.1.2. Still looking for comments regarding using:

OPTIMIZER=-O1
DEBUG=-DNDEBUG

Any opinions from anyone using xfsdump?

dkaylor commented on 2012-12-15 11:55

The current PKGBUILD worked for 3.1.1, but there actually is a 3.1.2, so I've updated again and the current PKGBUILD works for me. Anyone actually using xfsdump, let me know of any problems.

noplomplom commented on 2012-12-15 09:38

Please update PKGBUILD with correct MD5 sum ('84c0fa8a405db0ca21ede128761ef197'), SHA1 sum ('98f2b8d8f6e866e321bb81f08eb402bf3c048bba'), SHA256 sum ('1a765e2989925f6ad2ed17048b47d57783b7096cef04b2052ce6544f273f78a0') and SHA512 sum ('d022ecc3b8298027c5d870e77ecbe3467066ddb6ed809a9848c9d22212ba92e3e47a62fecafbc5d437ac41be2ca1d89ea5a248a66675d0b57996f4517905bc73').
Then I have a compilation error: "make: *** No targets specified and no makefile found".

dkaylor commented on 2012-12-13 06:28

Updated to 3.1.1. Anyone have any opinion on whether I should export these in the PKGBUILD:

OPTIMIZER=-O1
DEBUG=-DNDEBUG

Right now, it just uses the defaults as set in xfsdump's own install-sh script.
But the install documentation says those are available. I don't actually use xfsdump myself, so I don't know how much it matters. If no one cares, I'm going to leave it at the defaults.

dkaylor commented on 2012-12-13 06:28

Updated to 3.1.1. Anyone have any opinion on whether I should export these in the PKGBUILD:

OPTIMIZER=-O1
DEBUG=-DNDEBUG

Right now, it just uses the defaults as set in xfsdump's own install-sh script.
But the install documentation says those are available. I don't actually use xfsdump myself, so I don't know how much it matters. If no one cares, I'm going to leave it at the defaults.

dkaylor commented on 2012-04-14 16:51

Adopted.

Anonymous comment on 2012-04-02 12:33

I am updating this to 3.1.0. Two things to watch out for:

It may be best to use this with xfsprogs-3.1.8, which is still in testing. But I left the depends xfsprogs>=3.1.0 in the PKGBUILD.

Also I could not download the package with the default makepkg.conf DLAGENT for ftp, 'ftp::/usr/bin/curl -fC - --ftp-pasv --retry 3 --retry-delay 3 -o %o %u'
Changing it to 'ftp::/usr/bin/wget -c %u' worked normally. I don't have time to look into issues with curl vs. wget, so if someone has any idea let me know.

Anonymous comment on 2011-12-16 13:44

Yep, this was long out-of-date, sorry for that, should be current now. Thanks for letting me know!

Anonymous comment on 2011-06-23 11:02

Updated to 3.0.5.

Anonymous comment on 2011-06-23 04:51

submitter is non-responsive, so I'm adopting, updated PKGBUILD coming soon

Anonymous comment on 2011-06-22 10:40

willing to take over maintainership for now (as long as I'm using an XFS /home) if current wants to orphan

Jristz commented on 2011-06-08 01:34

http://xfs.org/index.php/Getting_the_latest_source_code <-- Webpage

http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs.git;a=summary <-- Xfs
http://oss.http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfstests.git;a=summary <-- XfsDump
http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfstests.git;a=summary <--XfsTest
http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/dmapi.git;a=summary <-- Dmapi

Jristz commented on 2011-06-08 01:27

current source migrate to http://xfs.org/index.php/Getting_the_latest_source_code
search and update

Jristz commented on 2011-06-08 01:23

@MrBlaster
==> SYST ... hecho. ==> PWD ... hecho.
==> TYPE I ... hecho. ==> CWD (1) /projects/xfs/cmd_tars ... hecho.
==> SIZE xfsdump-3.0.5.tar.gz ... hecho.
==> PASV ... hecho. ==> RETR xfsdump-3.0.5.tar.gz ...
No such file `xfsdump-3.0.5.tar.gz'.

Jristz commented on 2011-06-08 01:19

==> SYST ... hecho. ==> PWD ... hecho.
==> TYPE I ... hecho. ==> CWD (1) /projects/xfs/cmd_tars ... hecho.
==> SIZE xfsdump-3.0.4.tar.gz ... hecho.
==> PASV ... hecho. ==> RETR xfsdump-3.0.4.tar.gz ...
No such file `xfsdump-3.0.4.tar.gz'.

MrBlister commented on 2011-06-02 23:57

Change the pkgver to 3.0.5, and the MD5SUM to '878795f3cf8bcd10eaa3da9e0a612fa7'. Then it works.

MrBlister commented on 2011-06-02 23:55

Change the pkgver to 3.0.5, and the md5sum to '878795f3cf8bcd10eaa3da9e0a612fa7'. The it works.

Anonymous comment on 2011-04-04 15:23

It's not working as the makepkg software can't connect to the source I guess. Output:
[wloczymysl@wiwarium xfsdump]$ ls
xfsdump xfsdump.tar.gz
[wloczymysl@wiwarium xfsdump]$ cd xfsdump
[wloczymysl@wiwarium xfsdump]$ ls
PKGBUILD
[wloczymysl@wiwarium xfsdump]$ makepkg -s
==> Making package: xfsdump 3.0.4-1 (Mon Apr 4 17:18:02 CEST 2011)
==> Checking runtime dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for inter-conflicts...

Targets (1): dmapi-2.2.10-2

Total Download Size: 0.04 MB
Total Installed Size: 0.16 MB

Proceed with installation? [Y/n] y
:: Retrieving packages from extra...
dmapi-2.2.10-2-x86_64 40.6K 114.1K/s 00:00:00 [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(1/1) installing dmapi [######################] 100%
==> Checking buildtime dependencies...
==> Retrieving Sources...
-> Downloading xfsdump-3.0.4.tar.gz...
--2011-04-04 17:18:06-- ftp://oss.sgi.com/projects/xfs/cmd_tars/xfsdump-3.0.4.tar.gz
=> “xfsdump-3.0.4.tar.gz.part”
Resolving oss.sgi.com... 192.48.182.195
Connecting to oss.sgi.com|192.48.182.195|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD (1) /projects/xfs/cmd_tars ... done.
==> SIZE xfsdump-3.0.4.tar.gz ... done.
==> PASV ... done. ==> RETR xfsdump-3.0.4.tar.gz ...
No such file “xfsdump-3.0.4.tar.gz”.

==> ERROR: Failure while downloading xfsdump-3.0.4.tar.gz
Aborting... :(

ilpianista commented on 2010-11-13 15:36

* moved from [extra]