@sashaman I've just recently updated this package and used it for a while without a problem. From the log lines you've provided I see that the makepkg is launched from the root account. That's probably the reason.
Search Criteria
Package Details: docker-compose-bin 1.21.0-1
| Git Clone URL: | https://aur.archlinux.org/docker-compose-bin.git (read-only) |
|---|---|
| Package Base: | docker-compose-bin |
| Description: | Pythonless package of a a tool for defining and running multi-container applications |
| Upstream URL: | https://github.com/docker/compose |
| Keywords: | docker |
| Licenses: | |
| Conflicts: | |
| Submitter: | alkersan |
| Maintainer: | alkersan |
| Last Packager: | alkersan |
| Votes: | 8 |
| Popularity: | 0.328153 |
| First Submitted: | 2015-06-25 07:34 |
| Last Updated: | 2018-04-11 06:36 |
Dependencies (1)
Required by (0)
Sources (2)
Latest Comments
stiefel40k commented on 2017-12-06 21:40
alkersan commented on 2017-09-17 10:24
sashaman commented on 2017-09-15 15:28
==> Lade PKGBUILD von docker-compose-bin aus dem AUR herunter...
x .SRCINFO
x .gitignore
x PKGBUILD
docker-compose-bin 1.16.1-1 (2017-09-04 06:22)
(Nicht unterstütztes Paket: Potenziell gefährlich!)
==> PKGBUILD bearbeiten? [J/n] („A“ zum Abbrechen)
==> ----------------------------------------------
==> FEHLER: makepkg als root auszuführen ist nicht erlaubt, da es Ihrem System bleibenden, katastrophalen Schaden zufügen kann.
==> FEHLER: An unknown error has occurred. Exiting...
Konnte PKGBUILD nicht lesen
mwz commented on 2016-12-16 20:56
==> Validating source files with sha256sums...
docker-compose-Linux-x86_64 ... FAILED
1.9.0.tar.gz ... Passed
==> ERROR: One or more files did not pass the validity check!
:: failed to verify docker-compose-bin integrity
warmwaffles commented on 2016-05-16 14:13
Resolved the issue by nuking the pacaur directory
`rm -rf ~/.cache/pacaur/docker-compose-bin`
Solved the issue.
warmwaffles commented on 2016-05-16 14:04
Anyone else getting this issue?
:: Package(s) docker-compose-bin not found in repositories, trying AUR...
:: resolving dependencies...
:: looking for inter-conflicts...
AUR Packages (1): docker-compose-bin-1.7.1-1
:: Proceed with installation? [Y/n] y
:: Retrieving package(s)...
:: docker-compose-bin build files are up-to-date -- skipping
:: Checking docker-compose-bin integrity...
==> Making package: docker-compose-bin 1.7.1-1 (Mon May 16 08:58:54 CDT 2016)
==> Retrieving sources...
-> Found docker-compose-Linux-x86_64
-> Found 1.7.1.tar.gz
==> Validating source files with sha256sums...
docker-compose-Linux-x86_64 ... FAILED
1.7.1.tar.gz ... Passed
==> ERROR: One or more files did not pass the validity check!
:: failed to verify docker-compose-bin integrity
I downloaded the individual sources and sha256'd them and they match what is in the PKGBUILD file.
alkersan commented on 2015-10-19 18:29
@kjozsa, could you provide more context about your setup? I haven't faced with such error ever before.
kjozsa commented on 2015-10-19 13:39
$ docker-compose -f fig-master.yml pull eir_oracle
Couldn't find env file: /tmp/env
This looks like a new bug to me with docker-compose on your package. Care to have a quick look? Thanks!
ainola commented on 2015-08-12 04:15
Hey, cheers, and thanks for maintaining this.
ainola commented on 2015-08-11 21:27
@Alkersan, this line, for instance:
cd $srcdir/compose-$pkgver
needs double quotes in case someone is building this in a directory with a space in the name. If I were to download and run MAKEPKG in a directory called "My Directory", $srcdir would 'word-split' and only get "My". Changing it to this would fix it:
cd "$srcdir/compose-$pkgver"
Please fix the Sha256sums as they are currently wrong (validation fails) Thanks!
EDIT: Sorry it was a glitch on my side! I thought my .cache/pacaur was empty, that is why I posted the request, but somehow it was not, and it caused a glitch. Sorry again, everything looks fine!