- Mar 05, 2012
-
-
Pierre Schmitz authored
-
- Mar 04, 2012
-
-
Pierre Schmitz authored
This might be useful for unofficial repos
-
Florian Pritz authored
libperl.so results in soname="libperl.so.so" which is wrong. This returns the correct string: "libperl.so" Fix-by:
Dave Reisner <dreisner@archlinux.org> Signed-off-by:
Florian Pritz <bluewind@xinu.at> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
- Feb 15, 2012
-
-
Pierre Schmitz authored
-
Allan McRae authored
We do not allow packages to be uploaded without signatures so force all unsigned packages to be signed. This has the bonus of not breaking makepkg signing support by requiring you use an internal makepkg variable. Signed-off-by:
Allan McRae <allan@archlinux.org> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
- Feb 12, 2012
-
-
Lukas Fleischer authored
Compare every single tag with a list of valid tags. This prevents broken releases which occurred whenever someone made a typo on the command line: $ ./archrelease community i686 ==> ERROR: archrelease: Invalid tag: "community" (use -f to force release) Since the list is used in the ZSH completion as well, break it out to a separate file and move it to "lib/". Also, add a command line parameter to allow for releasing to an unknown repository when necessary. Signed-off-by:
Lukas Fleischer <archlinux@cryptocrack.de> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
- Feb 08, 2012
-
-
Lukas Fleischer authored
These tags make no sense. Remove them from our valid tag array that is used for tab completion. Signed-off-by:
Lukas Fleischer <archlinux@cryptocrack.de> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
- Feb 06, 2012
-
-
Pierre Schmitz authored
-
Florian Pritz authored
This fixes a problem where rsync won't work if the pkgver contains a colon (epoch). In this case rsync assumes that the colon is a remote:path separator and having src and dest both being remote arguments is not supported. Signed-off-by:
Florian Pritz <bluewind@xinu.at> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
- Jan 19, 2012
-
-
Pierre Schmitz authored
-
- Jan 18, 2012
-
-
Pierre Schmitz authored
Commit ee4edefa reverted too much and left pacman.conf unset
-
Pierre Schmitz authored
-
Allan McRae authored
Passing a directory that does not exist to makechrootpkg results in an error message: ==> ERROR: No chroot dir defined, or invalid path '' The path is not being printed as the readlink command blanks it if the directory does not exist. Fix this. Signed-off-by:
Allan McRae <allan@archlinux.org> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
Jan Alexander Steffens (heftig) authored
Signed-off-by:
Jan Alexander Steffens (heftig) <jan.steffens@gmail.com> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
Florian Pritz authored
The problem has been introduced in commit 56d4dec1 Signed-off-by:
Florian Pritz <bluewind@xinu.at> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
Dave Reisner authored
In the case of a .pkg.tar.xz and a .pkg.tar.gz existing in the same directory, all commitpkg would say is: ==> WARNING: Could not find . Skipping x86_64 Upon digging into the logic, we did a few things poorly, mostly in getpkgfile: - getpkgfile tried to die in a subshell (within the command substituion assignment to 'pkgfile'). This will never work. - We assumed that proper glob expansion happened when we received exactly 1 arg. This isn't necessarily true without nullglob in effect. - We dumped the real error (spewed by getpkgfile) to /dev/null. - We checked for the package twice in both $PWD and $DESTDIR/. - We checked for file existance multiple times. Address this by: - not hiding errors. revamp the wording a little bit to make it more obvious why we failed, particularly in the case of a glob expanding to more than 1 file. Logic here is simplified to pointing out the failure cases of 0 and >1. - setting nullglob so the number of arguments passed into getpkgfile is meaningful from a 'did it decisively resolve' point of view. - not trying to exit the entire script from a subshell. Just return a value (and use it). - avoiding the package file existance check afterwards. this is a freebie from getpkgfile when the glob passed fails to expand. Signed-off-by:
Dave Reisner <dreisner@archlinux.org> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
- Jan 14, 2012
-
-
Pierre Schmitz authored
-
Pierre Schmitz authored
-
- Dec 20, 2011
-
-
Pierre Schmitz authored
-
Tom Gundersen authored
As of filesystem-2011.12 this is not needed anylonger, and indeed blocks the chroot from being upgraded. As a workaround, recreating the chroot fixes the problem. Fixes FS#27640. Reported-by:
Andrea Scarpino <andrea@archlinux.org> Signed-off-by:
Tom Gundersen <teg@jklm.no> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
Timothy Redaelli authored
Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
- Dec 04, 2011
-
-
Dave Reisner authored
This fixes a compound command such as the one below from continuing even if the first fails. extra-x86_64-build && extra-i686-build The problem is that 'cleanup 0' is triggered in archbuild even after an unsucessful call to makechrootpkg. Since both archbuild and makechrootpkg share the exact same cleanup function (from lib/common), we simply force the shell to exit with the true return value by exec'ing the call to makechrootpkg. Signed-off-by:
Dave Reisner <dreisner@archlinux.org> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
Allan McRae authored
This ensures the PATH used when building is the default path and not the value set by the user calling makechrootpkg. Signed-off-by:
Allan McRae <allan@archlinux.org> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
Lukas Fleischer authored
This one fixes all the "Permission denied" errors we got when invoking make(1) after modifying a source file and removes the need to delete the generated scripts manually. Signed-off-by:
Lukas Fleischer <archlinux@cryptocrack.de> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
Lukas Fleischer authored
We already fixed a couple of these in previous patches - this one should replace all remaining uses of single brackets ("[") by double brackets. Also, use arithmetic evaluation instead of conditional expressions where appropriate and make use of "-z" and "-n" instead of comparing variables to empty strings. Signed-off-by:
Lukas Fleischer <archlinux@cryptocrack.de>
-
Pierre Schmitz authored
-
- Nov 21, 2011
-
-
Pierre Schmitz authored
-
- Nov 11, 2011
-
-
Pierre Schmitz authored
-
- Nov 09, 2011
-
-
Ionut Biru authored
repack is defined as a boolean. set it true when -R is passed /usr/sbin/makechrootpkg: line 295: 1: command not found Signed-off-by:
Ionut Biru <ibiru@archlinux.org> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
- Nov 06, 2011
-
-
Pierre Schmitz authored
-
Pierre Schmitz authored
-
Pierre Schmitz authored
-
Pierre Schmitz authored
-
- Nov 04, 2011
-
-
Lukas Fleischer authored
Move the message template before the if block. We moved this to the else branch in commit aaa68e49 which lead to "msgtemplate" being unset if one specifies a commit message on the command line, thus stripping the "upgpkg:" part. Signed-off-by:
Lukas Fleischer <archlinux@cryptocrack.de> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
Eric Bélanger authored
Signed-off-by:
Eric Bélanger <snowmaniscool@gmail.com> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
Lukas Fleischer authored
Add "lib/common.sh" to the build dependencies of our scripts to ensure everything gets rebuilt when we modify a common function. Also, add "Makefile" itself to enforce a rebuild if the edit command changes. Signed-off-by:
Lukas Fleischer <archlinux@cryptocrack.de> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
Lukas Fleischer authored
* Honor TMPDIR variable (just like we did in commit a0c6bf45). * Quote path properly. * Avoid unnecessary use of basename(1). Signed-off-by:
Lukas Fleischer <archlinux@cryptocrack.de> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
Lukas Fleischer authored
Signed-off-by:
Lukas Fleischer <archlinux@cryptocrack.de> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
Eric Bélanger authored
Some of the output/error messages were capitalized, some were not. This patch capitalize everything for consistency sake. Other minor changes were done to the messages like removing the superfluous "error:" from die messages and adding a final period to messages that were complete sentences as appropriate. Signed-off-by:
Eric Bélanger <snowmaniscool@gmail.com> Signed-off-by:
Pierre Schmitz <pierre@archlinux.de>
-
- Nov 01, 2011
-
-
Pierre Schmitz authored
-