You are not logged in.
If I try to create a package from the AUR
makepkg -sfi package-name
seems to freeze after installing the dependencies. It just stops after installing the last dependency and freezes with 65% CPU-Usage.
If I quit makepkg after freeze and run it again, building the package works so the dependencies get correctly installed.
Note to AUR-Helpers:
Yaourt -> works
Packer -> works
pacaur -> doesn't work
Any Idea what could cause this Problem and how to fix it?
Last edited by mak42 (2014-09-05 20:45:42)
simplicity is the ultimate form of sophistication
Offline
Note: Yaourt seems to use "makepkg -sf", while packer uses "makepkg -f". Pacaur indeed uses "-sfi", so it is the -i flag that doesn't work here.
Offline
Unfortunately no, "makepkg -sf" and "makepkg -s" also freezes, "makepkg -f" doesn't work due missing dependencies.
I installed dwarf-fortress a while ago, and had to enable multilib, maybe something in that direction is causing the issue?
EDIT: removing dwarf-fortress and its multi-lib deps doesn't seem to make any difference...
Last edited by mak42 (2014-09-05 07:13:35)
simplicity is the ultimate form of sophistication
Offline
mak42, you'll have to give more info if you want help.
Does this occur with a specific package or with all ?
If a specific pacakge, which one ?
incase you install needed dependencies manually , then run makepkg package-name without any flags, does the package build ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Online
Hi Lone_Wolf,
yeah sorry about that I'll try to clarify.
It occurs with all AUR-Packages having dependencies, if I use the -s flag.
Installing dependencies manually and build the package afterwards without any flags works fine.
So currently I really don't have a clue what could cause this behavior...
simplicity is the ultimate form of sophistication
Offline
mak42> Could you test with yaourt again? From what I see, yaourt actually uses makepkg -sf to build packages. It would be even weirder that yaourt succeeds where makepkg fails...
Offline
I just double-checked it, yaourt installs the dependencies and starts building the package.
Downloading tarball and running "makepkg -sf package-name" doesn't get further than installing the last dependency. It doesn't start building the package.
Can I provide any debug output or log-files that could help clarify this behavior?
simplicity is the ultimate form of sophistication
Offline
mak42> This doesn't make sense to me. Either I'm looking at the wrong part of yaourt code, or the additional "-p PKGBUILD" makes it work (yaourt actually uses "makepkg -sfp ./PKGBUILD", but that last part is totally redundant).
Last edited by Spyhawk (2014-09-05 13:26:36)
Offline
"makepkg -sfp ./PKGBUILD" also fails. It doesn't make sense for me either, but something must be causing this issue. I just could use yaourt and live with it, but it really bugs me.
Unfortunately I don't have the expertise to track it down myself
Last edited by mak42 (2014-09-05 14:05:25)
simplicity is the ultimate form of sophistication
Offline
mak42> Could you test with yaourt again? From what I see, yaourt actually uses makepkg -sf to build packages. It would be even weirder that yaourt succeeds where makepkg fails...
I just looked at the source myself and for me it looks like yaourt is installing the dependencies before building the package.
So I think this is the reason why it works with yaourt.
simplicity is the ultimate form of sophistication
Offline
Hmm, this looks like a function to build packages from the ABS (yaourt -Sb...). But well, I gave up understanding yaourt code logic a long time ago...
If you want to know more, you still can have a look at a bash debug output (bash -x yaourt -S package). Not sure exactly how that would help with your issue, but understanding why yaourt doesn't fail here might be a beginning.
Last edited by Spyhawk (2014-09-05 20:05:40)
Offline
Soooo I've found the guilty after digging through the source of "makepkg"
source /etc/profile &>/dev/null
causes the problem, if I run this command it freezes, Ctrl+C will kill the whole terminal.
So now I know the source of the Problem, still trying to figure out why this happens...
EDIT: Found it I'm using tdm as login-manager, to start it I've put a script into /etc/profile.d/ and this Script gave back an Error "Invalid TTY".
If you source /etc/profile it can't complete due to this Error.
So it was completely my fault
Thank's for your help, now I have to find another way of starting TDM
EDIT2:
just put /usr/bin/tdm into ~/.bash_profile and tdm works fine.
Actually this is already in the wiki, don't know why I didn't do that in the first place
Last edited by mak42 (2014-09-05 21:00:19)
simplicity is the ultimate form of sophistication
Offline
What have you got in /etc/profile.d/?
Offline
What have you got in /etc/profile.d/?
just a bash script tdm-login.sh
#!/bin/bash
source /usr/bin/tdm
running tdm in a terminal-emulator leads to the error Invalid TTY
Last edited by mak42 (2014-09-05 21:11:32)
simplicity is the ultimate form of sophistication
Offline
Yes, I posted while you were updating your previous post with the tdm info...
Offline