summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2012-10-03archbuild: abort if update or creation of the chroot failsPierre Schmitz1-2/+2
2012-09-14Fix ownership when copying files from chroot to systemFlorian Pritz1-0/+4
Previously files were always owned by nobody which means trying to write to them directly would fail because only the owner has +w. Signed-off-by: Florian Pritz <bluewind@xinu.at> Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2012-07-20prepare release20120720Pierre Schmitz1-1/+1
2012-06-25Fix bash completionsEric Bélanger1-0/+5
With bash-completion 2.0, the completion must have the same name as the binary. Signed-off-by: Eric Bélanger <snowmaniscool@gmail.com> Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2012-06-16prepare release20120616Pierre Schmitz1-1/+1
2012-06-16commitpkg: check if there are any packages to process before doing soPierre Schmitz1-9/+11
2012-06-16mkarchroot: reset trap so it wont be called twicePierre Schmitz2-1/+2
2012-06-16archbuild: do not cross filesystems when removing the chroot copiesPierre Schmitz1-2/+2
2012-06-16archbuild: use flock -n as we do elsewherePierre Schmitz1-3/+6
2012-06-15Fix /run permissions in chrootAllan McRae1-1/+1
Signed-off-by: Allan McRae <allan@archlinux.org> Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2012-06-12prepare release20120612Pierre Schmitz1-1/+1
2012-06-12Support multiple package cache directoriesPierre Schmitz1-18/+24
* We use the host package cache configuration * As only the first cache will be written to, we mount the others readonly
2012-06-12archbuild: Store chroots in /var/lib instead of /var/tmpPierre Schmitz1-1/+1
/var/tmp is cleaned up by tmpfiels by default which we cannot handle gracefully.
2012-06-11Remove no longer used optionPierre Schmitz1-3/+1
2012-06-11Add a version number to each chroot so we can tell the user when a rebuild ↵Pierre Schmitz1-3/+5
is needed
2012-06-11Enable signature checking within build environmentPierre Schmitz10-61/+96
* bind /sys and /dev/pts from host * drop support for devtmpfs as it is no longer needed * add /run and /dev/rtc0 * clone own ipc, uts and mount namespaces for chroot * set localtime, timezone and locale within chroot environment * copy /etc/pacman.d/gnupg from host
2012-06-11prepare release20120611Pierre Schmitz1-1/+1
2012-06-11update makepkg.conf and pacman.confPierre Schmitz10-82/+66
2012-06-10mkarchroot: use bind mount instead of symlink for /dev/ptmxGerardo Exequiel Pozzi1-1/+3
We need /dev/ptmx -> /dev/pts/ptmx (for devpts -o newinstance) Other way to do this thing is via bind mount (as said kernel doc[devpts.txt]). This should be done in this way at least for /dev as devtmpfs in the chroot. Since we can not touch /dev (devtmpfs), because devtmpfs is "singleton", just use bind method and avoid interference. Do it the same for both modes of /dev (tmpfs) and (devtmpfs) to keep it simple. Currently devpts in chroot is not working without this when using /dev as devtmpfs, this fixes this issue (opening /dev/ptmx, creates devices nodes on outside /dev/pts) Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2012-06-10Gracefully handle files containing an "@"Lukas Fleischer2-1/+4
The "@" sign in file names in SVN marks the beginning of a pegged version number -- from the Subversion book: Peg revisions are specified to the Subversion command-line client using at syntax, so called because the syntax involves appending an “at sign” (@) and the peg revision to the end of the path with which the revision is associated. The trivial workaround is to always append an at sign to the end of the path in the version control checks. Before: $ community-stagingpkg 'Add systemd units.' ==> ERROR: exim-submission@.service is not under version control $ svn status -v | grep 'exim-submission@.service' A - ? ? exim-submission@.service After: $ community-stagingpkg 'Add systemd units.' ==> Committing changes to trunk...done ==> Signing package exim-4.80-2-x86_64.pkg.tar.xz... [...] Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de> Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2012-06-10Prevent packages being uploaded with "Unknown Packager"Allan McRae1-0/+17
Signed-off-by: Allan McRae <allan@archlinux.org> Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2012-03-21Move bash_completion to /usr/share/bash-completion/completions/Pierre Schmitz1-2/+2
2012-03-05Prepare release20120305Pierre Schmitz1-1/+1
2012-03-05commitpkg: Pass through the -f parameter to archrelease so unofficial repos ↵Pierre Schmitz1-7/+9
can be used
2012-03-05makechrootpkg: Install the built packages before running namcap to reduce ↵Pierre Schmitz1-1/+1
false positives and check inter split package dependencies.
2012-03-05Add -d param to optionally support devtmpfsGerardo Exequiel Pozzi1-15/+22
The main intention of this patch is to take advantage of /dev/loop-control and loop devices. Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2012-03-05Add script to move packages between [extra] and [community]Pierre Schmitz3-1/+95
2012-03-04commitpkg: Add ability to override the serverPierre Schmitz1-14/+16
This might be useful for unofficial repos
2012-03-04find-libdeps: fix extraction of sonameFlorian Pritz1-1/+2
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>
2012-02-15prepare release20120215Pierre Schmitz1-1/+1
2012-02-15Always sign unsigned packagesAllan McRae1-8/+4
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>
2012-02-12archrelease: Validate tags before releasingLukas Fleischer3-19/+43
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>
2012-02-08zsh_completion: Remove multilib*-{i686, any}Lukas Fleischer1-3/+3
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>
2012-02-06prepare release20120206Pierre Schmitz1-1/+1
2012-02-06commitpkg: use absolute paths when uploading filesFlorian Pritz1-0/+10
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>
2012-01-19Fix typo: It's PKGDEST and not DESTDIRHEADmasterPierre Schmitz1-1/+1
2012-01-18Set correct pacman.conf20120119Pierre Schmitz2-2/+2
Commit ee4edefa2f12372adb4793c0dd6420fc76911ae4 reverted too much and left pacman.conf unset
2012-01-18Remove any pacman 4 related workarounds20120118Pierre Schmitz10-27/+12
2012-01-18makechrootpkg: fix error messageAllan McRae1-3/+4
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>
2012-01-18Fix up usage help, the Default line belongs to -lJan Alexander Steffens (heftig)1-1/+1
Signed-off-by: Jan Alexander Steffens (heftig) <jan.steffens@gmail.com> Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2012-01-18find-libdeps: fix syntax errorFlorian Pritz1-1/+1
The problem has been introduced in commit 56d4dec19fbcec23f677114e4104bb9df902ed9f Signed-off-by: Florian Pritz <bluewind@xinu.at> Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2012-01-18commitpkg: behavior more sanely in searching for built pkgsDave Reisner1-14/+15
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>
2012-01-14prepare release20120114Pierre Schmitz1-1/+1
2012-01-14Add support for multilib-stagingPierre Schmitz3-2/+119
2011-12-20prepare release20111220Pierre Schmitz1-1/+1
2011-12-20mkarchroot: do not create /etc/mtabTom Gundersen1-1/+0
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>
2011-12-20Use #!/bin/bash instead of #!/bin/shTimothy Redaelli1-1/+1
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
2011-12-04archbuild: exec makechrootpkg to preserve exit valueDave Reisner1-1/+1
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>
2011-12-04makearchroot: source /etc/profile before buildingAllan McRae1-0/+1
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>
2011-12-04Makefile: Remove output files before replacing themLukas Fleischer1-0/+1
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>
generated by cgit v1.2.3-24-g4f1b (git 2.32.0) at 2024-12-18 20:52:24 +0100