Package Details: bup-git 1:0.33.r72.g50f57708-1

Git Clone URL: (read-only, click to copy)
Package Base: bup-git
Description: Efficient file backup system based on the git packfile format
Upstream URL:
Keywords: backup dev git packfile system
Licenses: GPL
Conflicts: bup
Provides: bup
Submitter: mfwitten
Maintainer: edh
Last Packager: edh
Votes: 22
Popularity: 0.000000
First Submitted: 2011-04-20 17:55 (UTC)
Last Updated: 2023-12-31 16:06 (UTC)

Dependencies (14)

Required by (2)

Sources (1)

Latest Comments

1 2 3 4 5 6 Next › Last »

edh commented on 2021-08-17 13:57 (UTC)

@chowbok done.

chowbok commented on 2021-08-17 13:30 (UTC)

Hi! Would you mind adding "aarch64" to the list of supported architectures? It works fine on there.

edh commented on 2021-03-02 22:10 (UTC)

@mederel An additional commit would be completely sufficient but yes. IMHO this change does not merit introducing an epoch.

If you are annoyed by your package manager reminding you to update, just forcefully rebuild the package and you should be fine.

mederel commented on 2021-03-02 22:01 (UTC)

Hi @edh, I take it then that we await the next upstream release, and things should go back to normal, aren't they? Regards.

edh commented on 2021-02-16 12:45 (UTC)

@mederel and @IslandC0der Apparently the problem really was at my end. I nuked the repository and cloned again. Now I get a checksum that is one character shorter.

IslandC0der commented on 2021-02-16 12:35 (UTC)

Hmmm, I think @menderel is right; I'm getting the same issue just by running makepkg -do, no AUR helpers. The pkgver gets updated to 1:0.32.r0.g3b052c6-1

If you visit the github page, the latest commit is indeed 3b052c6 (note the missing '3' at the end), but if you click on it, you can see the full id, which is 3b052c63c93a95193447945296e7ec5db97f6b6e (there is a '3' right after). So now the question is: why is your pkgver() extracting one extra character, @edh?

mederel commented on 2021-02-15 20:36 (UTC)

@IslandC0der and @edh, thank you for your answers!!! And my apologies for a (2-week-long awaited!! :-( ) late answer.

Looking at pkgver I see the following command which I ran on a copy of the repository:

$ git describe --long 2>/dev/null

So here the 3 is missing. Just need to find why.

IslandC0der commented on 2021-01-31 22:14 (UTC)

@mederel, I think @edh is right

Are you using yay? If so, have you tried doing a clean build?

edh commented on 2021-01-31 18:01 (UTC)


The pkgver is computed correctly and is equal to the one here at the AUR. I can further compile the package just fine and thereby reproduce the exact same pkgver. This just might be a bug in your AUR helper and not in the PKGBUILD.

mederel commented on 2021-01-31 17:35 (UTC)

Every system update I do I see this AUR update proposed:

2  aur/bup-git    1:0.32.r0.g3b052c6-1 -> 1:0.32.r0.g3b052c63-1

It has to do with the version that is computed in the PKGBUILD I believe. Tried to change it accordingly in the file but it did nothing the update continue to come. Any idea where this could be comming from?