fosskers / aura

A multilingual package manager for Arch Linux and the AUR.
https://fosskers.github.io/aura/
GNU General Public License v3.0
1.76k stars 114 forks source link

List of AUR packages that don't build #14

Closed fosskers closed 6 years ago

fosskers commented 12 years ago

When you find a package that didn't build, please explain how the building failed. Thank you! Here they are:

UNSOLVED (as of 2018 June)

Currently there are no reported unbuildable packages with the aura-1.5 branch.

taylor1791 commented 12 years ago

lib32-nvidia-utils-bumblebee lib32-virtualgl

dkasak commented 12 years ago

jbrout

It has perl-exiftool listed as its dependency which is provided by perl-image-exiftool in the repos. However Aura fails with:

aura >>= Dependency checking failed for these reasons:
`perl-exiftool` exists in NO WAY as a package or as one provided by another!
fosskers commented 12 years ago

jbrout builds now. Please confirm.

dkasak commented 12 years ago

Confirming that jbrout builds.

fosskers commented 12 years ago

Thanks.

dhitchcock commented 12 years ago

I can't install torchlight-hib. It's case where you have to download the file manually and put it in the build dir, so usually in yaourt I have to copy it to something like /tmp/yaourt/aur-torchlight before giving the final confirmation to build. A pain that I'm used to.

Aura doesn't pause for me to copy it anywhere, but I did notice that it looked for files in a var, $LOCAL_PACKAGE_SOURCES, so I set that to a dir, put the file in that dir, and then it did find it! but still failed

- in $LOCAL_PACKAGE_SOURCES ['/home/packages'] ... FOUND

==> Starting setup... install: cannot stat ‘/var/cache/pacman/pkg/torchlight-hib-12290/torchlight-hib/pkg/opt/Torchlight/Torchlight.png’: No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

aura >>= Building failed.

So not sure how to deal with packages like this where I have to download manually, which seems like something I do pretty often. Mostly games, or ttf-win7-fonts.

fosskers commented 12 years ago

Is this one of those packages where it will ask you where to look for the files? If so, try running aura with -Ax and you should see the prompt. Otherwise, aura builds packages within temp folders in the package cache. It would be pretty hard to put a file there preemptively ;)

dhitchcock commented 12 years ago

It does not prompt where to look for the files, though -Ax did make it go much farther than it did previously. It got to the very end, but then spit out an error at the end and the package didn't get upgraded.

==> Finished making: torchlight-hib 1.15_20120926-0 (Tue Oct 2 17:52:23 CDT 2012) aura: : getSymbolicLinkStatus: does not exist (No such file or directory)

fosskers commented 12 years ago

...This has happened before. Unfortunately, that's a haskell error. Could be coming from somewhere within the attempt to copy the built .pkg file to the package cache.

AbigailBuccaneer commented 12 years ago

android-sdk: Conditional dependencies depending on architecture.

$ sudo aura -A android-sdk
aura >>= Determining dependencies...
aura >>= Main AUR packages:
android-sdk

aura >>= Continue? [Y/n] y
aura >>= Building `android-sdk`...
aura >>= Well, building `android-sdk` failed.
aura >>= Dumping makepkg output in 3.. 2.. 1..
==> Making package: android-sdk r20.0.3-2 (Thu 11 Oct 12:07:21 BST 2012)
==> Checking runtime dependencies...
==> Missing Dependencies:
  -> lib32-alsa-lib
  -> lib32-openal
  -> lib32-libstdc++5
  -> lib32-libxv
  -> lib32-ncurses
  -> lib32-sdl
  -> lib32-zlib
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.

aura >>= Building failed.
fosskers commented 12 years ago

@Jetbeard thank you. I should get on improving that Bash parser.

fosskers commented 12 years ago

The following should now build:

lib32-turbojpeg
lib32-virtualgl
lib32-nvidia-utils-bumblebee
spotify
openssl098

Please confirm! @raisdead, etc

ejstacey commented 12 years ago

$ aura -A package-query aura >>= Determining dependencies... aura >>= Dependency checking failed for these reasons: 'yajl exists in NO WAY as a package or as one provided by another! $ pacman -Q | grep yajl yajl 2.0.4-1 $

fosskers commented 12 years ago

That's a bug in the Bash parser. Checking aura -Ap package-query shows that the maintainer thought it hilarious to mix quotes and no quotes in the depends field.

ejstacey commented 12 years ago

Ah, thanks. I should have investigated further.. just noticed my old tool handled it. It must be used to ridiculousness in PKGBUILDs ;)

fosskers commented 12 years ago

I'll see what I can do to alter the parser.

ejstacey commented 12 years ago

As a side note, I've noticed that lots of large packages fail to build, and I have to re-do them. (jre|jdk)-compat, lib32-nvidia-utils-bumblebee, nvidia-utils-bumblebee are all ones I have to attempt multiple times. It's not my network connection dropping or anything like that; Aura just seems to not like it. Eventually, it will build. I'm not sure what triggers it being successful. Are there timers or anything like that?

aura >>= Building jre6-compat... aura >>= Well, building jre6-compat failed. aura >>= Dumping makepkg output in 3.. 2.. 1.. ==> Making package: jre6-compat 6u37-b06 (Thu Oct 25 13:21:28 EST 2012) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving Sources... -> Downloading jdk-6u37-linux-x64.bin... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 285 0 0 295 0 --:--:-- --:--:-- --:--:-- 0 100 68.7M 100 68.7M 0 0 78376 0 0:15:19 0:15:19 --:--:-- 45965 ==> ERROR: Failure while downloading jdk-6u37-linux-x64.bin

Should I open another ticket for this? Any other details I can get/give you?

Thanks!

fosskers commented 12 years ago

That output you're seeing there is makepkg output, which in turn is actually verbose curl output. Those downloads failing are the fault of either a bad (no longer existent?) source location or an incorrect PKGBUILD.

By the way, what version of aura are you using?

ejstacey commented 12 years ago

Weird. I thought that'd be the case, but I don't know why curl would randomly fail downloads.. haven't seen that before. Even though curl shows 100% download, still fails. Don't think it's a md5/sha diff either, but I'll investigate more tomorrow. Just thought of it, but if Aura downloads to somewhere on /var, maybe that's filling up... anyways. Tomorrow I'll dig through it more.

Using the latest Aura from AUR.

fosskers commented 12 years ago

Packages are built in temporary directories within the pacman package cache, actually, which is in /var.

fosskers commented 12 years ago

@ejstacey I fixed the parsing bug. package-query should build now.

ejstacey commented 12 years ago

Excellent, thanks!

fosskers commented 12 years ago

No prob.

EdShaw commented 12 years ago
# aura -A primus-git lib32-primus-git 
aura >>= Determining dependencies...
aura >>= Dependency checking failed for these reasons:
`primus` exists in NO WAY as a package or as one provided by another!

primus-git provides primus.

lib32-primus-git depends on primus

Edit: Should note that installing primus-git and then lib32-primus-git works fine.

Ta

fosskers commented 12 years ago

Thanks. This is a big-ish problem, in that aura can only check for virtual package dependencies for packages that are in official repos or already installed. This is why installing one after the other works, but things explode when you try to install them at the same time.

I do think I know how I could fix this, though.

flying-sheep commented 11 years ago
pymclevel
mcedit

both can’t be upgraded because the latter depends on a specific version of the former.

  1. if one tries to upgrade pymclevel first, it fails because the old version of mcedit depends on the previous version of pymcedit
  2. if one tries to upgrade mcedit first, it fails because it depends on the newer version of pymclevel

possible solution: handle like a circular dependency.

fosskers commented 11 years ago

Thank you @flying-sheep . I had hoped this would never come up. I'll add 'em to the list. Would this not occur even when building manually with makepkg?

fosskers commented 11 years ago

@dhitchcock I finally figured out what was causing torchlight not to build. The fix will be pushed momentarily, and will be included in this coming Sunday's release.

nyux commented 11 years ago

storybook has failed to install multiple times using aura.

$ sudo aura -A storybook
<snip>
aura >>= Building `storybook`...
aura >>= Well, building `storybook` failed.
aura >>= Dumping makepkg output in 3.. 2.. 1..
==> Making package: storybook 4.0.9-1 (Sun Dec 23 15:55:43 MST 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
  -> Downloading storybook-4.0.9-linux.bin...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 63.0M  100 63.0M    0     0   270k      0  0:03:58  0:03:58 --:--:--  207k
==> Validating source files with md5sums...
    storybook-4.0.9-linux.bin ... Passed
==> Extracting Sources...
==> Entering fakeroot environment...
==> Starting build()...

./storybook-4.0.9-linux.bin: line 310: exec: -t: invalid option
exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...]
==> ERROR: A failure occurred in build().
    Aborting...

aura >>= Building failed.
[03:38:29][nyux@noxya][~]$ sudo aura -Ax storybook
<snip>
==> Making package: storybook 4.0.9-1 (Sun Dec 23 15:39:30 MST 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
  -> Downloading storybook-4.0.9-linux.bin...

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:05 --:--:--     0
 82 63.0M   82 52.2M    0     0   165k      0  0:06:29  0:05:22  0:01:07 57086
curl: (18) transfer closed with 11352487 bytes remaining to read
==> ERROR: Failure while downloading storybook-4.0.9-linux.bin
    Aborting...

All dependencies were installed, and yaourt has no problem installing the package.

fosskers commented 11 years ago

@nyux Thanks for reporting this. Sorry for a late response; I was away from home for a few days without a computer.

I've never seen build failures like this. I'll get on testing on my end first thing in the morning. As for an initial diagnosis:

./storybook-4.0.9-linux.bin: line 310: exec: -t: invalid option
exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...]
==> ERROR: A failure occurred in build().
    Aborting...

I find this unlikely to be an aura error directly. Could you tell me what shell you're using?

curl: (18) transfer closed with 11352487 bytes remaining to read
==> ERROR: Failure while downloading storybook-4.0.9-linux.bin
    Aborting...

This is very likely directly an aura error, as it uses curl internally for downloading package sources. Again, give me a day or so and I'll have more details for you.

nyux commented 11 years ago

I'm using a vanilla bash shell.

Version 4.2.039-1, straight from base

fosskers commented 11 years ago

@nyux Thanks.

fosskers commented 11 years ago

@nyux I succeeded in building storybook with aura. I did it twice in fish shell and once in bash, no problems. If you provide me with the output of aura --auradebug and sudo aura --auradebug, I might be able to figure out what your problem is.

nyux commented 11 years ago

I'm sorry for taking so long to respond. Christmas-y things got in the way.

 aura --auradebug
User              => nyux
True User         => nyux
Using Sudo?       => No.
Language          => English
Pacman Command    => pacman-color
Ignored Pkgs      => menu-cache
Pkg Cache Path    => /var/cache/pacman/pkg/
Log File Path     => /var/log/pacman.log
Silent Building?  => Yes!
Must Confirm?     => Yes!
PKGBUILD editing? => No.
Diff PKGBUILDs?   => No.
usage:  aura <operation> [...]
 sudo aura --auradebug
User              => root
True User         => nyux
Using Sudo?       => Yes!
Language          => English
Pacman Command    => pacman-color
Ignored Pkgs      => menu-cache
Pkg Cache Path    => /var/cache/pacman/pkg/
Log File Path     => /var/log/pacman.log
Silent Building?  => Yes!
Must Confirm?     => Yes!
PKGBUILD editing? => No.
Diff PKGBUILDs?   => No.
usage:  aura <operation> [...]
fosskers commented 11 years ago

@nyux And it's still failing to build?

nyux commented 11 years ago

I did sudo aura -Au and aura updated itself to the latest version (1.0.8.1-1) I was hoping that would help fix the problem, so I ran sudo aura -A storybook again

[05:03:30][nyux@noxya][~]$ sudo aura -A storybook
aura >>= Determining dependencies...
aura >>= Main AUR packages:
storybook

aura >>= Continue? [Y/n] 
aura >>= Building `storybook`...
aura >>= Well, building `storybook` failed.
aura >>= Dumping makepkg output in 3.. 2.. 1..
==> Making package: storybook 4.0.9-1 (Tue Jan  1 17:03:43 MST 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
  -> Downloading storybook-4.0.9-linux.bin...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 63.0M  100 63.0M    0     0   334k      0  0:03:13  0:03:13 --:--:--  323k
==> Validating source files with md5sums...
    storybook-4.0.9-linux.bin ... Passed
==> Extracting Sources...
==> Entering fakeroot environment...
==> Starting build()...

./storybook-4.0.9-linux.bin: line 310: exec: -t: invalid option
exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...]
==> ERROR: A failure occurred in build().
    Aborting...

aura >>= Building failed.

So... yeah, this is a bit confusing. I don't know what's going on.

fosskers commented 11 years ago

Try this then. aura -Aw storybook. Then untar (tar -zxvf) what that gives you, and run makepkg yourself in its new subdirectory. If that fails, then it's definitely not an aura problem.

nyux commented 11 years ago
[08:09:33][nyux@noxya][~/downloads/builds]$ sudo aura -Aw storybook
[sudo] password for nyux:
aura >>= Downloading `storybook` source tarball...
[08:09:50][nyux@noxya][~/downloads/builds]$ tar -zxvf storybook.tar.gz 
storybook/
storybook/PKGBUILD
[08:10:05][nyux@noxya][~/downloads/builds]$ cd storybook
[08:10:08][nyux@noxya][~/downloads/builds/storybook]$ makepkg
==> Making package: storybook 4.0.9-1 (Thu Jan 10 20:10:12 MST 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
  -> Downloading storybook-4.0.9-linux.bin...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 63.0M  100 63.0M    0     0   180k      0  0:05:57  0:05:57 --:--:--  262k
==> Validating source files with md5sums...
    storybook-4.0.9-linux.bin ... Passed
==> Extracting Sources...
==> Entering fakeroot environment...
==> Starting build()...
Creating directory /home/nyux/downloads/builds/storybook/pkg/usr/share/storybook
Verifying archive integrity... All good.
Uncompressing Storybook.......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
==> Tidying install...
  -> Purging unwanted files...
  -> Compressing man and info pages...
==> Creating package...
  -> Generating .PKGINFO file...
  -> Compressing package...
==> Leaving fakeroot environment.

Since yaourt builds the package all right, I thought that building it manually had to work. And it did.


[EDIT]: And... this is weird. Just upgraded aura and ran aura -A storybook. It failed, still, but it also output a new error message.

./storybook-4.0.9-linux.bin: line 310: exec: -t: invalid option
exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...]
==> ERROR: A failure occurred in build().
    Aborting...

error: no targets specified (use -h for help)
Raw shell command call failed.

Then, for the sake of comparison, I ran aura -Ax storybook and:

aura >>= Determining dependencies...
aura >>= Main AUR packages:
storybook

aura >>= Continue? [Y/n] 
aura >>= Building `storybook`...
==> Making package: storybook 4.0.9-1 (Thu Jan 10 20:31:26 MST 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
  -> Downloading storybook-4.0.9-linux.bin...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 63.0M  100 63.0M    0     0   283k      0  0:03:48  0:03:48 --:--:--  378k
==> Validating source files with md5sums...
    storybook-4.0.9-linux.bin ... Passed
==> Extracting Sources...
==> Entering fakeroot environment...
==> Starting build()...
Creating directory /var/cache/pacman/pkg/storybook-12437/storybook/pkg/usr/share/storybook
Verifying archive integrity... All good.
Uncompressing Storybook.......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
==> Tidying install...
  -> Purging unwanted files...
  -> Compressing man and info pages...
==> Creating package...
  -> Generating .PKGINFO file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: storybook 4.0.9-1 (Thu Jan 10 20:36:42 MST 2013)
loading packages...
resolving dependencies...
looking for inter-conflicts...

Targets (1): storybook-4.0.9-1

Total Installed Size:   102.91 MiB

Proceed with installation? [Y/n] 
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
(1/1) installing storybook                         [######################] 100%

It launches correctly and seems to work just fine. How peculiar.

julianwachholz commented 11 years ago

The package php53 does not fail to build, but Aura fails to install it correctly. This is because makepkg creates multiple pkg.tar.xz files, but only the main php53.pkg.tar.xz is installed.

The PKGBUILD has the following inside:

# AUR split packages no likey.
# This will shove 'em down its throat.
pkgname=php53

true && pkgbase=php53
true && pkgname=('php53'
         'php53-cgi'
         'php53-apache'
         ...
         'php53-sqlite'
         'php53-tidy'
         'php53-xsl')
pkgver=5.3.20
fosskers commented 11 years ago

@nyux I'm scratching my head on that one...

@julianwachholz Ha! So this finally decided to happen, did it. I was wondering if I'd ever see this in the wild. I know exactly why this is happening and can fix it easily.

fosskers commented 11 years ago

@julianwachholz Fixed. Just built php53 myself. The fix is already pushed to the repo, and will be included in tomorrow's official release.

julianwachholz commented 11 years ago

Now that's issue handling how I like it. Great job, thank you! :)

fosskers commented 11 years ago

My pleasure.

jon-incomm commented 11 years ago

powerpill

$ sudo aura -Ax powerpill aura >>= Determining dependencies... aura: fd:6: hGetContents: invalid argument (invalid byte sequence)

fosskers commented 11 years ago

@jon-incomm Powerpill is building for me. Also, that's a Haskell error rather than an Aura one. Apparently that error comes up when there is an issue with character encoding. What terminal do you use?

flying-sheep commented 11 years ago

perl-module-refresh does not install its builddep perl-path-class, and consequently fails to build.

jon-incomm commented 11 years ago

@fosskers: I'm connected over ssh in iTerm2 (a mac terminal). powerpill installed fine for me from packer.

fosskers commented 11 years ago

@jon-incomm Could you tell me if you're getting similar errors when you do:

aura -Ad powerpill and aura -Ap powerpill

fosskers commented 11 years ago

@flying-sheep Thank you for reporting that. It's the checkdepends field that's breaking things. Aura doesn't support that, it seems. I'm actually rewriting the Bash parser from the ground up, so this will be fixed naturally when that is done.

For now, if you comment out the checkdepends field and the check() function, it should build.

fosskers commented 11 years ago

@flying-sheep perl-module-refresh builds now. The Bash parser has been completely rewritten.