markzz/aurweb.git/git-interface/git-update.py, branch v4.0.0

git-update: Error out if PKGBUILD is missing

2015-07-16T12:09:55Z

Fixes FS#45646. Signed-off-by: Lukas Fleischer

git-update: Fix error when printing SRCINFO errors

2015-07-04T13:02:04Z

This commit fixes a bug introduced by ae2907a (git: Use .format everywhere instead of %, 2015-06-27) where passing the error tuple to .format wasn't prefixed with an asterisk. Fixes FS#45545. Reported-by: Marty Signed-off-by: Johannes Löthberg Signed-off-by: Lukas Fleischer

git-update: Improve error message on invalid pkgbase

2015-06-27T11:04:03Z

When the package base does not match the repository name, we currently show an error message that only mentions the package base name: error: invalid pkgbase: yate-qt4 To the end user this sounds like the package base name is malformed itself (and we show exactly the same error message when it contains invalid characters, indeed). Clarify that there is a name mismatch by also printing the expected value: error: invalid pkgbase: yate-qt4, expected: yate4-qt Inspired by FS#45483. Signed-off-by: Lukas Fleischer

git-update: Allow privileged users to bypass blacklist

2015-06-27T11:04:03Z

Fixes FS#45410. Signed-off-by: Johannes Löthberg Signed-off-by: Lukas Fleischer

git: Use .format everywhere instead of %

2015-06-27T11:04:03Z

% formatting is deprecated, and .format should be used instead. Signed-off-by: Johannes Löthberg Signed-off-by: Lukas Fleischer

Make url and pkgdesc fields optional

2015-06-20T12:29:43Z

The url and pkgdesc PKGBUILD variables are optional, so they should be in the AUR as well. Signed-off-by: Johannes Löthberg Signed-off-by: Lukas Fleischer

git-update: Remove regex matching of URL

2015-06-20T12:28:23Z

The regex check that a URL is either http or ftp doesn't really have any use, and it forces you to leave proper URLs for eg projects hosted on gopher empty. Signed-off-by: Johannes Löthberg Signed-off-by: Lukas Fleischer

git-update: Fix parsing of versioned optdepends

2015-06-14T15:58:56Z

Fixes FS#43649. Signed-off-by: Lukas Fleischer

git-update: Allow non-fast-forwards for TUs

2015-06-11T15:56:51Z

Although we theoretically never want to lose history, there may be rare occasions when a forced push is required (e.g. if illegal data is pushed). Allow Trusted Users and Developers to perform non-fast-forward pushes. Signed-off-by: Lukas Fleischer

git-update: Deny non-fast-forwards

2015-06-11T15:56:26Z

To make sure we never lose any history, non-fast-forwards are forbidden. Instead of relying on receive.denyNonFastForwards, add a simple check to the update hook. This has the added benefit of more flexibility. Signed-off-by: Lukas Fleischer