It looks like the headers shipped by btrfs-progs have changed recently.
The git version ships them as a submodule, and the PyPI archive includes them as well; that should work better.
Search Criteria
Package Details: bedup 0.10.1-1
| Git Clone URL: | https://aur.archlinux.org/bedup.git (read-only) |
|---|---|
| Package Base: | bedup |
| Description: | Offline deduplication utility for the BTRFS filesystem |
| Upstream URL: | https://github.com/g2p/bedup |
| Licenses: | |
| Conflicts: | |
| Submitter: | omgold |
| Maintainer: | TheNiceGuy |
| Last Packager: | TheNiceGuy |
| Votes: | 39 |
| Popularity: | 0.730616 |
| First Submitted: | 2013-04-27 09:47 |
| Last Updated: | 2016-06-27 01:16 |
Dependencies (9)
- python
- python-alembic
- python-cffi
- python-distribute (python-setuptools)
- python-mako
- python-sqlalchemy (python-sqlalchemy-0.7.9, python-sqlalchemy-git)
- python-xdg
- btrfs-progs (btrfs-progs-git) (make)
- gcc (gcc-git, gcc-multilib-git, gcc-multilib-x32, gcc-multilib) (make)
Required by (0)
Sources (1)
Latest Comments
G2P commented on 2016-10-26 16:26
Enverex commented on 2016-10-26 15:08
Build fails pretty badly here - http://www.hastebin.com/ecofoguyux.rb
Crazyachmed commented on 2016-06-04 21:13
please add aarch64 to supported list. seems to work for me ;)
darkbasic commented on 2016-05-18 09:27
Sorry I wanted to comment on python-editor, not bedup.
Anyway I confirm that 0.10.1 fixed the build issue.
G2P commented on 2016-05-18 07:34
The error fryfrog reports is fixed in https://github.com/g2p/bedup/commit/579c05a9df15fc9f32c2e9482459f7bb7f51a7eb.
I just pushed a point release with the fix.
darkbasic commented on 2016-05-18 07:16
==> Removing existing $pkgdir/ directory...
==> Starting build()...
Traceback (most recent call last):
File "setup.py", line 1, in <module>
from setuptools import setup
ImportError: No module named 'setuptools'
==> ERROR: A failure occurred in build().
fryfrog commented on 2016-05-11 05:56
Should one still use this? I tried to build it, but it fails.
https://ptpb.pw/_NOL
Maybe gcc has had some big changes since this was last released by the source? :/
justin8 commented on 2013-12-30 07:25
FYI, for pkgbuilds, anything in 'base-devel' is assumed to be installed. that includes gcc. See: https://wiki.archlinux.org/index.php/PKGBUILD#makedepends
see
As for conflicts with th. e git version, the git version should have a conflicts and a provides for bedup (which is already there). see: https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines#Guidelines
WonderWoofy commented on 2013-06-03 02:47
Yeah, bedup git totally builds and installs... I wonder where I went wrong, as looking over the PKGBUILD, mine looked pretty much the same. Now to see if it works... Thanks for that.
I guess I can agree that having gcc in the makedepends certainly doens't hurt anything, and I think the ability to run makepkg w/o gcc is as it should be probably.
I think the only thing with the git package is that it should have "conflicts=('bedup')" so that in the event that bedup is installed bedup-git will not error out with "file exists in filesystem".
Now I wish I handn't deleted the PKGBUILD I made off of yours so that I could compare the two. I woundn't be surprised if I just had some kind of typo in there. I guess when I think about it I really didn't put much time into debugging it.
omgold commented on 2013-06-02 15:55
> FYI, python-distribute is in the makedepends array, but it is actually required for bedup to run.
Right. Thanks. Fixed it.
> Also, I think that the 'gcc' makedepend is assumed in the case of AUR programs. I mean I know that not everything needs a C compiler, but I haven't noticed other AUR entries including 'gcc' as a makedep.
Ehm, I tried it, and actually makepkg can be run without having gcc installed. So I guess, any package containing C code should have a makedepends on gcc, no?
> Out of curiousity, is there any reason why you chose to use the pypi version 0.90 rather than makeing a bedup-git package?
I used it, because in the instructions at the github repo it was mentioned as one of the 'official' ways to build it. As the git repo does not seem to have a tag for a newer stable version and I wanted to have a stable one, I went for pypi.
> Are you familiar enough it its deps to make such a package? If so I would really appreciate it if you did that, as simply trying to convert this PKGBUILD to be a git type did not seem to work. Thoughts?
Okay, I now also created a bedup-git package. Didn't stumble over anything out of the ordinary. For me it seems to work. Maybe you can give it a try.